Windows 10, version 1607 and Windows Server 2016

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
    Database connections using Microsoft ODBC SQL Server driver might fail.
    Apps using ODBC connections might fail to connect to databases.
    OS Build 14393.5501
    KB5019964
    2022-11-08
    Confirmed
    2022-12-05
    16:04 PT
    Possible memory leak in Local Security Authority Subsystem Service (LSASS,exe)
    LSASS might use more memory over time and the DC might become unresponsive and restart.
    OS Build 14393.5501
    KB5019964
    2022-11-08
    Mitigated
    2022-11-23
    18:44 PT
    Sign in failures and other issues related to Kerberos authentication
    After installing updates released November 2022, you might have Kerberos authentication issues.
    OS Build 14393.5501
    KB5019964
    2022-11-08
    Resolved
    KB5021654
    2022-11-17
    14:00 PT
    Domain join processes may fail with error "0xaac (2732)"
    This might be encountered when an account was created by a different identity than the one used to join the domain
    OS Build 14393.5427
    KB5018411
    2022-10-11
    Confirmed
    2022-10-27
    16:57 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-10-18
    10:04 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 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

    December 2022

    Database connections using Microsoft ODBC SQL Server driver might fail.

    StatusOriginating updateHistory
    ConfirmedOS Build 14393.5501
    KB5019964
    2022-11-08
    Last updated: 2022-12-05, 16:04 PT
    Opened: 2022-12-05, 15:45 PT

    After installing KB5019964, apps which use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as "The EMS System encountered a problem" with "Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream" or "Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server".

    If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt (select Start then type command prompt and select it) and type the following command:

    tasklist /m sqlsrv32.dll
    

    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 10, 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; 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

    November 2022

    Possible memory leak in Local Security Authority Subsystem Service (LSASS,exe)

    StatusOriginating updateHistory
    MitigatedOS Build 14393.5501
    KB5019964
    2022-11-08
    Last updated: 2022-11-23, 18:44 PT
    Opened: 2022-11-23, 17:54 PT

    After installing KB5019964 or later updates on Domain Controllers (DCs), you might experience a memory leak with Local Security Authority Subsystem Service (LSASS,exe). Depending on the workload of your DCs and the amount of time since the last restart of the server, LSASS might continually increase memory usage with the up time of your server and the server might become unresponsive or automatically restart. Note: The out-of-band updates for DCs released November 17, 2022 and November 18, 2022 might be affected by this issue.

    Workaround: To mitigate this issue, open Command Prompt as Administrator and use the following command to set the registry key KrbtgtFullPacSignature to 0:

    reg add "HKLM\System\CurrentControlSet\services\KDC" -v "KrbtgtFullPacSignature" -d 0 -t REG_DWORD
    

    Note: Once this known issue is resolved, you should set KrbtgtFullPacSignature to a higher setting depending on what your environment will allow. It is recommended to enable Enforcement mode as soon as your environment is ready. For more information on this registry key, please see KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967.

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

    Affected platforms:

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

    Sign in failures and other issues related to Kerberos authentication

    StatusOriginating updateHistory
    Resolved KB5021654OS Build 14393.5501
    KB5019964
    2022-11-08
    Resolved: 2022-11-17, 14:00 PT
    Opened: 2022-11-13, 15:16 PT

    Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1.

    After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:

    When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1":

    While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.
    

    Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.

    Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.

    Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.

    To get the standalone package for these out-of-band updates, search for the KB number 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. Note The below updates are not available from Windows Update and will not install automatically.

    Cumulative updates:

    Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

    Standalone Updates:

    Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

    Affected platforms:

    • ​Client: Windows 11, version 22H2; Windows 10, 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; 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

    October 2022

    Domain join processes may fail with error "0xaac (2732)"

    StatusOriginating updateHistory
    ConfirmedOS Build 14393.5427
    KB5018411
    2022-10-11
    Last updated: 2022-10-27, 16:57 PT
    Opened: 2022-10-27, 15:53 PT

    Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy."

    This issue originates with the October 2022 security updates ( KB5018411) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior.

    Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain.

    Home users of Windows are unlikely to experience this issue.

     

    Next steps: Please see KB5020276 to understand the designed behavior. We have added insights to this KB, and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated once those changes have released.

    Affected platforms:

    • ​Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; 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-10-18, 10:04 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 22H2; Windows 11, version 21H2; Windows 10, version 22H2; 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

    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.