-->
Find information on known issues for Windows 10, version 1607 and Windows Server 2016. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.
| Windows 10, version 21H1 is now available Find out how to get the update > | IT tools for Windows 10, version 21H1 Explore the latest tools and resources to support your rollout > |
The 'Blue Light' reduction feature was first introduced in Windows 10 build 15002. It was renamed to 'Night Light' in build 15019. Night Light - Turn On or Off in Windows 10. It sounds like you don't have the latest Windows 10 Insider build installed to have this feature available yet. Windows 10 Build Number - Find. Windows 10 1607 language pack (in domain at home) Archived Forums Windows 10 Installation, Setup, and Deployment. Windows 10 Installation, Setup, and Deployment.
Windows 10 1607 Fix
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| 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 |
| Windows Presentation Foundation (WPF) apps might close, or you may receive an error Microsoft and third-party applications which use the .Net UI framework called WPF might have issues. | OS Build 14393.4225 KB4601318 2021-02-09 | Mitigated | 2021-02-11 20:41 PT |
| Cluster service may fail if the minimum password length is set to greater than 14 The cluster service may fail to start if “Minimum Password Length” is configured with greater than 14 characters. | OS Build 14393.2639 KB4467684 2018-11-27 | Mitigated | 2019-04-25 14:00 PT |
Issue details
July 2021
Windows 10 1607 Problems
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. | ||
February 2021
Windows Presentation Foundation (WPF) apps might close, or you may receive an error | ||
| Status | Originating update | History |
| Mitigated | OS Build 14393.4225 KB4601318 2021-02-09 | Last updated: 2021-02-11, 20:41 PT Opened: 2021-02-11, 17:49 PT |
After installing KB4601318, Windows Presentation Foundation (WPF) apps might close, or you may receive an error similar to: Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef) at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr) at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean) at System.Windows.Interop.HwndMouseInputProvider.Dispose() This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps. Affected platforms:
Workaround: To mitigate this issue when using Microsoft Visual Studio, update to the latest version. This issue is resolved starting with the following releases: Developers can mitigate this issue in their own apps by setting two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”. The switches are named Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix; both should be set to “true”. The first switch avoids the crash, but re-introduces the issue addressed in this update. The second switch is currently ignored, but will be recognized in a future .NET update that addresses the issue for the null-reference crash; it restores the behavior originally intended to be addressed in this update. For example, using the app.config file method to apply the workaround at application scope: <AppContextSwitchOverrides value='Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true ' /> Next steps: We are working on a resolution and will provide an update in an upcoming release. | ||
November 2018
Cluster service may fail if the minimum password length is set to greater than 14 | ||
| Status | Originating update | History |
| Mitigated | OS Build 14393.2639 KB4467684 2018-11-27 | Last updated: 2019-04-25, 14:00 PT Opened: 2018-11-27, 10:00 PT |
After installing KB4467684, the cluster service may fail to start with the error '2245 (NERR_PasswordTooShort)' if the Group Policy 'Minimum Password Length' is configured with greater than 14 characters. Affected platforms:
Workaround: Set the domain default 'Minimum Password Length' policy to less than or equal to 14 characters. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. | ||