Learn about new features and innovations.
Windows Server 2022
Find information on known issues and the servicing status for Windows Server 2022. For immediate help with Windows update issues, use the Get Help app in Windows or go to support.microsoft.com. Follow?@WindowsUpdate?on Twitter for Windows release health updates.
- What's new in Windows Server 2022
- Windows Server 2022 is now available
See how this release can modernize your server environment.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Database connections using Microsoft ODBC SQL Server driver might fail. Apps using ODBC connections might fail to connect to databases. | OS Build 20348.1249 KB5019081 2022-11-08 | Resolved KB5022291 | 2023-01-10 10:00 PT |
| Software Defined Networking (SDN) managed by SCVMM might have issues with new VMs SCVMM might have issues creating new VMs or creating new NICs for existing VMs. | OS Build 20348.30000 KB5021249 2022-12-13 | Resolved KB5022553 | 2022-12-20 14:00 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. | OS Build 20348.1194 KB5018485 2022-10-25 | Resolved KB5021249 | 2022-12-13 10:00 PT |
| KB5012170 might fail to install and you might receive a 0x800f0922 error Security update for Secure Boot DBX might fail to install. | OS Build 20348.880 KB5012170 2022-08-09 | Confirmed | 2022-12-14 16:12 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 20348.1129 KB5018421 2022-10-11 | Confirmed | 2022-10-27 16:57 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 20348.469 KB5009555 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 20348.469 KB5009555 2022-01-11 | Mitigated | 2022-02-07 15:36 PT |
Issue details
December 2022
Database connections using Microsoft ODBC SQL Server driver might fail.
| Status | Originating update | History | Resolved KB5022291 | OS Build 20348.1249 KB5019081 2022-11-08 | Resolved: 2023-01-10, 10:00 PT Opened: 2022-12-05, 15:45 PT |
|---|
After installing KB5019081, 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". Note for developers: Apps affected by this issue might fail to fetch data, for example when using the SQLFetch function. This issue might occur when calling SQLBindCol function before SQLFetch or calling SQLGetData function after SQLFetch and when a value of 0 (zero) is given for the ‘BufferLength’ argument for fixed datatypes larger than 4 bytes (such as SQL_C_FLOAT).
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
Workaround: To mitigate this issue, you can do one of the following:
- If your app is already using or able to use Data Source Name (DSN) to select ODBC connections, install Microsoft ODBC Driver 17 for SQL Server and select it for use with your app using DSN. Note: We recommend the latest version of Microsoft ODBC Driver 17 for SQL Server, as it is more compatible with apps currently using the legacy Microsoft ODBC SQL Server Driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.
- If your app is unable to use DSN, the app will need to be modified to allow for DSN or to use a newer ODBC driver than Microsoft ODBC SQL Server Driver (sqlsrv32.dll).
Resolution: This issue was resolved in KB5022291. If you have implemented the above workaround, it is recommended to continue using the configuration in the workaround.
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
Software Defined Networking (SDN) managed by SCVMM might have issues with new VMs
| Status | Originating update | History | Resolved KB5022553 | OS Build 20348.30000 KB5021249 2022-12-13 | Resolved: 2022-12-20, 14:00 PT Opened: 2022-12-13, 09:48 PT |
|---|
After installing KB5021249 on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021249, only new Network Adapters created after installation of KB5021249 are affected.
When experiencing this issue, you might receive one of the following errors:
- When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection"
- Software defined networking (SDN) software load balancer service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error"
- SDN RAS Gateway service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error"
Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands:
$lang = (Get-WinSystemLocale).Name
C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\$lang\VfpExt.mfl
C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof
A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this KB article.
Resolution: This issue was resolved in out-of-band (OOB) updates released December 20, 2022 for installation on all Hyper-V hosts in your environment which are using Software Defined Networking (SDN) and managed by System Center Virtual Machine Manager (SCVMM). 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.
To get the standalone package for these out-of-band (OOB) 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 December 13, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019
November 2022
Direct Access might be unable to reconnect after your device has connectivity issues
| Status | Originating update | History | Resolved KB5021249 | OS Build 20348.1194 KB5018485 2022-10-25 | Resolved: 2022-12-13, 10:00 PT Opened: 2022-11-13, 14:49 PT |
|---|
After installing KB5018485 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: You can mitigate this issue by restarting your Windows device.
Resolution: This issue was resolved in updates released December 13, 2022 ( KB5021249) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released December 13, 2022 ( KB5021249) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before December 13, 2022, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. 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:
- Download for Windows 11, version 22H2 - KB5018427 221029_091533 Known Issue Rollback
- Download for Windows 11, version 21H2 - KB5018483 220927_043051 Known Issue Rollback
- Download for Windows Server 2022 - KB5018485 220927_043049 Known Issue Rollback
- Download for Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 - KB5018482 220927_043047 Known Issue Rollback
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)"
| Status | Originating update | History | Confirmed | OS Build 20348.1129 KB5018421 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 ( KB5018421) 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
KB5012170 might fail to install and you might receive a 0x800f0922 error
| Status | Originating update | History | Confirmed | OS Build 20348.880 KB5012170 2022-08-09 | Last updated: 2022-12-14, 16:12 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.
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
| Status | Originating update | History | Investigating | OS Build 20348.469 KB5009555 2022-01-11 | Last updated: 2022-02-24, 17:41 PT Opened: 2022-02-24, 17:25 PT |
|---|
After installing KB5009555 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
| Status | Originating update | History | Mitigated | OS Build 20348.469 KB5009555 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:
- .NET Framework 4.8 KB5011258
- Windows Server 2019:
- Windows Server 2016:
- Windows Server 2012 R2:
- .NET Framework 4.8 KB5011266
- .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011263
- .NET Framework 4.5.2 KB5011261
- Windows Server 2012:
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.