Windows 10, version 1607 and Windows Server 2016

  • Article
  • 12 minutes to read

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.

    Known issues

    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    Copying files/shortcuts using Group Policy Preferences might not work as expected
    Files or shortcuts might not copy or copy as zero-byte files when using Group Policy Preferences on client devices.
    		OS Build 14393.5356
    KB5017305
    2022-09-13    		Confirmed
    		2022-09-22
    16:49 PT
    Update might fail to install and you might receive a 0x800f0922 error
    Security update for Secure Boot DBX might fail to install.
    		OS Build 14393.5285
    KB5012170
    2022-08-09    		Investigating
    		2022-09-20
    10:06 PT
    Possible issues caused by new Daylight Savings Time in Chile
    Chilean government announced a Daylight Saving Time (DST) change for 2022.
    		N/A

    		Mitigated
    		2022-09-06
    14:02 PT
    Certain apps or devices might be unable to create Netlogon secure channel connections
    Scenarios which rely on synthetic RODC machine accounts might fail if they do not have a linked KRBTGT account.
    		OS Build 14393.4886
    KB5009546
    2022-01-11    		Investigating
    		2022-02-24
    17:41 PT
    Apps that acquire or set Active Directory Forest Trust Information might have issues
    Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, or you might receive an error.
    		OS Build 14393.4886
    KB5009546
    2022-01-11    		Mitigated
    		2022-02-07
    15:36 PT
    Windows 10 Enterprise might not activate via KMS
    Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might have issues activating using new CSVLK.
    		OS Build 14393.4402
    KB5003197
    2021-05-11    		Confirmed
    		2021-12-01
    18:10 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

    September 2022

    Copying files/shortcuts using Group Policy Preferences might not work as expected

    StatusOriginating updateHistory
    ConfirmedOS Build 14393.5356
    KB5017305
    2022-09-13    		Last updated: 2022-09-22, 16:49 PT
    Opened: 2022-09-22, 15:23 PT

    After installing KB5017305, file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings in Group Policy Editor.

    Workaround: To mitigate this issue, you can do ONE of the following:

    • ​Uncheck the "Run in logged-on user's security context (user policy option)". Note: This might not mitigate the issue for items using a wildcard (*).
    • ​Within the affected Group Policy, change "Action" from "Replace" to "Update".
    • ​If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotes) from the destination might allow the copy to be successful.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Possible issues caused by new Daylight Savings Time in Chile

    StatusOriginating updateHistory
    MitigatedN/A

    		Last updated: 2022-09-06, 14:02 PT
    Opened: 2022-09-02, 13:17 PT

    Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

    Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

    • ​Time shown in Windows and apps will not be correct.
    • ​Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.
    • ​Automation using date and time, such as Scheduled tasks, might not run at the expected time.
    • ​Timestamp on transactions, files, and logs will be 60 minutes off.
    • ​Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.
    • ​Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

    Workaround: You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

    • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off.
    • ​Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.

    To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:

    • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to On.
    • ​Go to Control Panel > Clock and Region > Date and Time > Change time zone and check the option for “Automatically adjust clock for Daylight Saving Time”.

    Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly.

    Next steps: We are working on a resolution and will provide an update in an upcoming release. Note: Microsoft plans to release an update to support this change; however, there might be insufficient time to properly build, test, and release such an update before the change goes into effect. Please use the workaround above.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    August 2022

    Update might fail to install and you might receive a 0x800f0922 error

    StatusOriginating updateHistory
    InvestigatingOS Build 14393.5285
    KB5012170
    2022-08-09    		Last updated: 2022-09-20, 10:06 PT
    Opened: 2022-08-12, 17:08 PT

    When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.

    Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

    Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

    Next steps: We are presently investigating and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    February 2022

    Certain apps or devices might be unable to create Netlogon secure channel connections

    StatusOriginating updateHistory
    InvestigatingOS Build 14393.4886
    KB5009546
    2022-01-11    		Last updated: 2022-02-24, 17:41 PT
    Opened: 2022-02-24, 17:25 PT

    After installing KB5009546 or any updates released January 11, 2022 and later on your domain controllers, scenarios which rely on Read-only domain controllers (RODCs) or synthetic RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must have a linked and compliant KRBTGT account to successfully establish a secure channel. Affected applications or network appliances, such as Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations after joining a domain.

    Next Steps: Affected apps and network appliances will need an update from their developer or manufacturer to resolve this issue. Microsoft and Riverbed are presently investigating and will provide an update when more information is available.

    Affected platforms:

    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Apps that acquire or set Active Directory Forest Trust Information might have issues

    StatusOriginating updateHistory
    MitigatedOS Build 14393.4886
    KB5009546
    2022-01-11    		Last updated: 2022-02-07, 15:36 PT
    Opened: 2022-02-04, 16:57 PT

    After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API.

    Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.

    For instructions on how to install this update for your operating system, see the KB articles listed below:

    • ​Windows Server 2022: 
    • ​Windows Server 2019: 
    • ​Windows Server 2016: 
    • ​Windows Server 2012 R2: 
    • ​Windows Server 2012:

    Affected platforms:

    • ​Client: None
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    December 2021

    Windows 10 Enterprise might not activate via KMS

    StatusOriginating updateHistory
    ConfirmedOS Build 14393.4402
    KB5003197
    2021-05-11    		Last updated: 2021-12-01, 18:10 PT
    Opened: 2021-12-01, 17:44 PT

    After installing updates released April 22, 2021 or later on an affected version of Windows Server when used as Key Management Services (KMS) host, client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note: This does not affect activation of any other version or edition of Windows.

    Client devices attempting to activate that are affected by this issue might receive the error, "Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information." Event Log entries related to activation is another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs, then Application. If you see only event ID 12288 (without a corresponding event ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did not respond, or the client did not receive the response. For more information on these event ID, see Useful KMS client events - Event ID 12288 and Event ID 12289.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016

    February 2021

    Windows Presentation Foundation (WPF) apps might close, or you may receive an error

    StatusOriginating updateHistory
    MitigatedOS 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:

    • ​Client: Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
    • ​Server: Windows Server, version 1803; Windows Server 2016

    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

    StatusOriginating updateHistory
    MitigatedOS 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:

    • ​Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2016

    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.