How To Repair Windows 10 Version 1607
Skip to main content
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Resolved issues in Windows 10, version 1607 and Windows Server 2016
- Article
- 15 minutes to read
-
Thank you.
See a list of known issues that have been resolved for Windows 10, version 1607 and Windows Server 2016 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Microsoft Installer might have issues updating or repairing apps Affected apps might fail to open after an update or repair has been attempted. | OS Build 14393.4770 KB5007192 2021-11-09 | Resolved KB5008207 | 2021-12-14 10:00 PT |
| Connections to printers shared via print server might encounter errors This issue is observed when print clients try to connect to a remote printer shared on a print server | OS Build 14393.4704 KB5006669 2021-10-12 | Resolved KB5008207 | 2021-12-14 10:00 PT |
| Authentication might fail on DCs with certain Kerberos delegation scenarios Clients and servers using Single Sign On via Kerberos Tickets acquired via S4u2self might be unable to authenticate. | OS Build 14393.4770 KB5007192 2021-11-09 | Resolved KB5008601 | 2021-11-14 10:00 PT |
| Installation of printers might fail when attempted over some network connections This issue has been observed in devices which access printers via a print server using HTTP connections | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved KB5006669 | 2021-10-12 10:00 PT |
| UI elements and drawing within some apps may not work as expected Some apps using GDI+ might have issues with scaling within the app or when used on high DPI or resolution displays. | OS Build 14393.4704 KB5006669 2021-10-12 | Resolved KB5007192 | 2021-11-09 10:00 PT |
| Receiving a prompt for administrative credentials every time you attempt to print This issue affects devices in environments in which the print server and print client are in different times zones. | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved KB5006669 | 2021-10-12 10:00 PT |
| Custom printing properties might not be correctly provided to print server clients This issue will not cause printing operations to fail, but clients might print with default settings only | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved KB5006669 | 2021-10-12 10:00 PT |
| Administrator credentials required every time apps attempt to print Certain printers in some environments using Point and Print might prompt for credentials every time when printing. | OS Build 14393.4583 KB5005043 2021-08-10 | Resolved External | 2021-09-16 18:23 PT |
| Printing and scanning might fail when these devices use smart-card authentication Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication. | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
Issue details
November 2021
Microsoft Installer might have issues updating or repairing apps | ||
| Status | Originating update | History |
| Resolved KB5008207 | OS Build 14393.4770 KB5007192 2021-11-09 | Resolved: 2021-12-14, 10:00 PT Opened: 2021-11-18, 10:34 PT |
| After installing KB5007192 or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted. Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app. Resolution: This issue was resolved in KB5008207. This update should prevent the issue from occurring again, but you might need to reinstall affected apps, if they will not open. Affected platforms:
Back to top | ||
Authentication might fail on DCs with certain Kerberos delegation scenarios | ||
| Status | Originating update | History |
| Resolved KB5008601 | OS Build 14393.4770 KB5007192 2021-11-09 | Resolved: 2021-11-14, 10:00 PT Opened: 2021-11-10, 19:09 PT |
| After installing the November security updates, released November 9, 2021 on your Domain Controllers (DC) running a Windows Server versions listed below in affected platforms, you might have authentication failures on servers relating to Kerberos Tickets acquired via S4u2self. The authentication failures are a result of Kerberos Tickets acquired via S4u2self and used as evidence tickets for protocol transition to delegate to backend services which fail signature validation. Kerberos authentication will fail on Kerberos delegation scenarios that rely on the front-end service to retrieve a Kerberos ticket on behalf of a user to access a backend service. Important Kerberos delegation scenarios where a Kerberos client provides the front-end service with an evidence ticket are not impacted. Pure Azure Active Directory environments are not impacted by this issue. End users in your environment might be unable to sign into services or applications using Single Sign On (SSO) using Active Directory on-premises or in a hybrid Azure Active Directory environment. Updates installed on the client Windows devices will not cause or affect this issue. Affected environments might be using the following:
You might receive one or more of the following errors when encountering this issue:
Resolution: This issue was resolved in the out-of-band update KB5008601 released November 14, 2021. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5008601, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5008601 is not available from Windows Update and will not install automatically. Affected platforms:
Back to top | ||
UI elements and drawing within some apps may not work as expected | ||
| Status | Originating update | History |
| Resolved KB5007192 | OS Build 14393.4704 KB5006669 2021-10-12 | Resolved: 2021-11-09, 10:00 PT Opened: 2021-11-05, 17:58 PT |
| After installing KB5006669 or a later update, certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling. Resolution: This issue was resolved in KB5007192. Affected platforms:
Back to top | ||
October 2021
Connections to printers shared via print server might encounter errors | ||
| Status | Originating update | History |
| Resolved KB5008207 | OS Build 14393.4704 KB5006669 2021-10-12 | Resolved: 2021-12-14, 10:00 PT Opened: 2021-10-29, 11:15 PT |
| After installation of KB5006669, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
Please refer to these articles for further guidance:
You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect. Resolution: This issue was resolved in KB5008207. Affected platforms:
Back to top | ||
Installation of printers might fail when attempted over some network connections | ||
| Status | Originating update | History |
| Resolved KB5006669 | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-10-13, 12:34 PT |
| After installing KB5005573, devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. Devices which had connected to and installed the printer prior to the installation of KB5005573 are unaffected and operations to that printer will succeed as usual. This issue has been observed in devices which access printers via a print server using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download. Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations. Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Only the automatic download and installation processes are impacted by this issue. Resolution: This issue was resolved in KB5006669. Affected platforms:
Back to top | ||
Receiving a prompt for administrative credentials every time you attempt to print | ||
| Status | Originating update | History |
| Resolved KB5006669 | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-10-15, 17:21 PT |
| After installing KB5005573 or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones. Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations. Affected platforms:
Resolution: This issue was resolved in KB5006669. If after installing KB5006669 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481). Back to top | ||
Custom printing properties might not be correctly provided to print server clients | ||
| Status | Originating update | History |
| Resolved KB5006669 | OS Build 14393.4651 KB5005573 2021-09-14 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-10-13, 12:28 PT |
| After installing KB5005573 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005573 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected. Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings. Resolution: This issue was resolved in KB5006669. Affected platforms:
Back to top | ||
September 2021
Administrator credentials required every time apps attempt to print | ||
| Status | Originating update | History |
| Resolved External | OS Build 14393.4583 KB5005043 2021-08-10 | Last updated: 2021-09-16, 18:23 PT Opened: 2021-09-16, 18:11 PT |
| After installing KB5005043 or a later update, certain printers in some environments using Point and Print might receive a prompt saying, "Do you trust this printer" and requiring administrator credentials to install every time an app attempts to print to a print server or a print client connects to a print server. This is caused by a print driver on the print client and the print server using the same filename, but the server has a newer version of the file. When the print client connects to the print server, it finds a newer driver file and is prompted to update the drivers on the print client, but the file in the package it is offered for installation does not include the later file version. Workaround: Verify that you are using the latest drivers for all your printing devices and where possible, use the same version of the print driver on the print client and print server. Affected platforms:
Resolution: This issue is resolved externally by adjusting the print drivers in your environment. If updating drivers in your environment does not resolve the issue, please contact support for your printer manufacturer (OEM). For more information, see the Q1/A1 in the "Frequently asked questions" section of KB5005652. Back to top | ||
July 2021
Printing and scanning might fail when these devices use smart-card authentication | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved: 2021-08-03, 10:36 PT Opened: 2021-07-23, 14:36 PT |
| After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. Affected platforms:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. Back to top | ||
How To Repair Windows 10 Version 1607
Source: https://docs.microsoft.com/en-us/windows/release-health/resolved-issues-windows-10-1607
Posted by: wrighthaventrus.blogspot.com
0 Response to "How To Repair Windows 10 Version 1607"
Post a Comment