Windows 10, version 22H2

Find information on known issues and the status of the rollout for Windows 10, version 22H2. 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.

The Windows release health hub is always evolving. Take our short survey and let us know how we can improve.

Current status as of November 18, 2022

The Windows 10, version 22H2 feature update is entering its final rollout phase and is now designated for broad deployment. As part of the broad deployment phase, Microsoft is offering this update to an expanded set of eligible devices running Windows 10, version 20H2 and later versions.

If you have an eligible device, you can install this feature update by opening Windows Update Settings and selecting Check for updates. Once the update is ready for your device, you will see the option to Download and install

Devices currently on Windows 10, version 20H2 or newer will have a fast installation experience because this feature update will install like a monthly update. For more information on how to install Windows 10, version 22H2, read this blog post. If you want to explore moving to Windows 11, see How to get the Windows 11 2022 Update.

To learn about Windows 10 servicing timelines and lifecycle, see Windows 10 release information and Lifecycle FAQ - Windows.

    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 19045.2251
    KB5019959
    2022-11-08
    Confirmed
    2022-12-05
    15:45 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 19045.2251
    KB5019959
    2022-11-08
    Resolved
    2022-11-18
    16:22 PT
    Your desktop or taskbar might momentarily disappear or might become unresponsive
    You might experience an error in which the desktop or taskbar disappearing then reappearing.
    N/A

    Resolved
    2022-11-16
    19:50 PT
    Direct Access might be unable to reconnect after your device has connectivity issues
    This issue might happen after losing network connectivity or transitioning between Wi-Fi networks or access points.
    OS Build 19045.2193
    KB5018482
    2022-10-25
    Resolved
    2022-11-13
    15:34 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
    N/A

    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.
    N/A

    Investigating
    2022-10-18
    10:04 PT

    Issue details

    December 2022

    Database connections using Microsoft ODBC SQL Server driver might fail.

    StatusOriginating updateHistory
    ConfirmedOS Build 19045.2251
    KB5019959
    2022-11-08
    Last updated: 2022-12-05, 15:45 PT
    Opened: 2022-12-05, 15:45 PT

    After installing KB5019959, 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

    Sign in failures and other issues related to Kerberos authentication

    StatusOriginating updateHistory
    ResolvedOS Build 19045.2251
    KB5019959
    2022-11-08
    Resolved: 2022-11-18, 16:22 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

    Your desktop or taskbar might momentarily disappear or might become unresponsive

    StatusOriginating updateHistory
    ResolvedN/A

    Resolved: 2022-11-16, 19:50 PT
    Opened: 2022-11-16, 19:36 PT

    You might experience an error in which the desktop or taskbar might momentarily disappear, or your device might become unresponsive.

    Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.

    Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.

    For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

    Group Policy downloads with Group Policy name:

    Affected platforms:

    • ​Client: Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • ​Server: None

    Direct Access might be unable to reconnect after your device has connectivity issues

    StatusOriginating updateHistory
    ResolvedOS Build 19045.2193
    KB5018482
    2022-10-25
    Resolved: 2022-11-13, 15:34 PT
    Opened: 2022-11-13, 14:49 PT

    After installing KB5018482 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).

    Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected.

    Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.

    Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.

    For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

    Group Policy downloads with Group Policy name:

    Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

    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
    • ​Server: Windows Server 2022; Windows Server 2019

    October 2022

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

    StatusOriginating updateHistory
    ConfirmedN/A

    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 () 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
    InvestigatingN/A

    Last updated: 2022-10-18, 10:04 PT
    Opened: 2022-08-12, 17:08 PT

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

    Note: This issue only affects the Security update for Secure Boot DBX () 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 .

    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