Resolved issues in Windows Server 2022
Find information on recently resolved issues for Windows Server 2022. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Printer names and icons might be changed and HP Smart app automatically installs In most cases, it is possible to use the printer for printing jobs and other features such as copy, scan, or fax. | N/A | Resolved | 2023-12-16 10:29 PT |
| Windows Server 2022 VMs running on VMware ESXi hosts might fail to start Affected VMs will receive an error with a blue screen and Stop code : PNP DETECTED FATAL ERROR. | OS Build 20348.2031 KB5031364 2023-10-10 | Resolved KB5032198 | 2023-11-14 10:00 PT |
| You might receive an error with apphelp.dll from apps using DirectX After installing KB5019980 or later updates, devices with older Intel graphics drivers might encounter issues. | OS Build 20348.1249 KB5019081 2022-11-08 | Resolved KB5029250 | 2023-08-08 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 | Resolved KB5023705 | 2023-03-14 10:00 PT |
| Computing effective access might not show results You might be unable to view effective access and explorer.exe might continue to use CPU after closing the dialog. | OS Build 20348.1726 KB5026370 2023-05-09 | Resolved KB5028171 | 2023-07-11 10:00 PT |
| WSUS might not offer updates to Windows 11, version 22H2 Updates released February 14, 2023 might not be offered via WSUS to some client devices. | N/A | Resolved KB5023705 | 2023-03-14 10:00 PT |
| Microsoft Outlook and some apps might not open 32-bit apps from Microsoft or third-parties might fail to open with certain security software installed. | OS Build 20348.1787 KB5027225 2023-06-13 | Resolved External | 2023-06-28 17:36 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 | Resolved KB5023705 | 2023-03-14 10:00 PT |
| Windows Server 2022 might not start up on VMware Windows Server 2022 VMs running versions of VMware ESXi 7.0.x and below might not start. | OS Build 20348.30000 KB5022842 2023-02-14 | Resolved External | 2023-02-22 16:58 PT |
| 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 |
Issue details
December 2023
Printer names and icons might be changed and HP Smart app automatically installs
| Status | Originating update | History | Resolved | N/A | Resolved: 2023-12-16, 10:29 PT Opened: 2023-12-04, 18:46 PT |
|---|
Some issues related to printer configurations are being observed on Windows devices. Microsoft is investigating this issue and coordinating with partners on a solution.
Symptoms can include the following:
- Some Windows devices are installing the HP Smart app.
- Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
- Double clicking on a printer displays the on-screen error "No tasks are available for this page".
Note: Our investigations indicate that this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.
Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool – December 2023. For devices covered by Recommended Troubleshooting, a user-initiated troubleshooter will be available in the coming weeks.
If you need support to resolve this issue, go to https://support.microsoft.com/contactus, and select Windows.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
November 2023
Windows Server 2022 VMs running on VMware ESXi hosts might fail to start
| Status | Originating update | History | Resolved KB5032198 | OS Build 20348.2031 KB5031364 2023-10-10 | Resolved: 2023-11-14, 10:00 PT Opened: 2023-11-08, 17:53 PT |
|---|
After installing KB5031364 on virtual machines (VMs) running on VMware ESXi hosts, Windows 2022 might fail to start up. Affected VMs will receive an error with a blue screen and Stop code : PNP DETECTED FATAL ERROR. This issue only affects guest VMs with the following configuration on VMware ESXi hosts only:
- AMD Epyc physical processor
- "Expose IOMMU to guest OS" enabled in VMware settings for the VM.
- “Enable Virtualization Based Security” enabled in Windows Server 2022.
- "System Guard Secure Launch" enabled in Windows Server 2022.
Workaround: To mitigate this issue, you can disable "Expose IOMMU to guest OS". Important: This workaround should only be used in environments which do not require "Expose IOMMU to guest OS" to be enabled.
Resolution: This issue was resolved in KB5032198.
Affected platforms:
- Client: None
- Server: Windows Server 2022
June 2023
Computing effective access might not show results
| Status | Originating update | History | Resolved KB5028171 | OS Build 20348.1726 KB5026370 2023-05-09 | Resolved: 2023-07-11, 10:00 PT Opened: 2023-06-21, 16:37 PT |
|---|
After installing updates released on May 9, 2023 or later updates, you might be unable to view Effective Access in the "Advanced Security Settings" dialog for shared files or folders. On affected devices, when the "View effective access" button is selected, you will receive the message "Computing effective access...." but the results of the query might not be displayed and explorer.exe might continue to use CPU after the Advanced Security settings dialog is closed. This issue is unlikely to be experienced by consumers using Windows devices in their home.
Workaround: If you have attempted to view effective access, you can mitigate the CPU usage issue by restarting your device or by signing out for the affected user. Note: Locking Windows will not mitigate this issue, you must sign out.
Resolution: This issue was resolved in KB5028171.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: Windows Server 2022
Microsoft Outlook and some apps might not open
| Status | Originating update | History | Resolved External | OS Build 20348.1787 KB5027225 2023-06-13 | Last updated: 2023-06-28, 17:36 PT Opened: 2023-06-28, 17:14 PT |
|---|
After installing KB5027225 or later updates on Windows devices with certain antivirus, antimalware or security software installed, you might not be able to open Microsoft or third-party apps. Some known affected apps are Microsoft Outlook and other Microsoft Office apps. This issue only occurs with 32-bit apps running on 64-bit Windows with Trellix Endpoint Security version earlier than 35.31.25. When attempting to open an affected app, Event Log indicates an access violation with the error "module is unknown". This issue is not likely to be encountered by consumers using Windows devices in their home.
Resolution: This issue has been resolved by Trellix in Endpoint Security Agent (HX) 35.31.25 and later. If you are experiencing this issue with other security software installed or after installing the latest version of Trellix Endpoint Security Agent, please contact customer support of the security software you are using.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2
- Server: Windows Server 2022
February 2023
You might receive an error with apphelp.dll from apps using DirectX
| Status | Originating update | History | Resolved KB5029250 | OS Build 20348.1249 KB5019081 2022-11-08 | Resolved: 2023-08-08, 10:00 PT Opened: 2023-02-08, 15:49 PT |
|---|
After installing KB5019081 or later updates, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 26.20.100.7463 up to 30.0.101.1190. This issue might happen intermittently and affects a small number of enterprise apps which use DirectX or Direct3D to render part or all of their content. Windows devices using updated Intel graphics drivers with a version later than 30.0.101.1190 are not affected by this issue and already have the Intel resolution for this issue installed.
Home users of Windows are unlikely to experience this issue, as the few affected apps are more commonly used in enterprise environments.
Workaround: To mitigate this issue, you can install an Intel graphics driver with a later version than 30.0.101.1190. It is recommended to check your Windows device manufacturer's support for the latest version of the Intel graphics driver for your device. If they do not offer a driver later than 30.0.101.1190, you can check List of Drivers for Intel Graphics for information on how to download and install the latest Intel graphics driver available from Intel directly.
Resolution: This issue was resolved in KB5029250.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022
WSUS might not offer updates to Windows 11, version 22H2
| Status | Originating update | History | Resolved KB5023705 | N/A | Resolved: 2023-03-14, 10:00 PT Opened: 2023-02-15, 13:49 PT |
|---|
Updates released February 14, 2023 or later might not be offered from some Windows Server Update Services (WSUS) servers to Windows 11, version 22H2. The updates will download to the WSUS server but might not propagate further to client devices. Affected WSUS servers are only those running Windows Server 2022 which have been upgraded from Windows Server 2016 or Windows Server 2019. This issue is caused by the accidental removal of required Unified Update Platform (UUP) MIME types during the upgrade to Windows Server 2022 from a previous version of Windows Server. This issue might affect security updates or feature updates for Windows 11, version 22H2. Microsoft Configuration Manager is not affected by this issue.
Workaround: To mitigate this issue, please see Adding file types for Unified Update Platform on premises.
Resolution: This issue was resolved in KB5023705 for Windows Server 2022.
Affected platforms:
- Client: Windows 11, version 22H2
- Server: Windows Server 2022
Windows Server 2022 might not start up on VMware
| Status | Originating update | History | Resolved External | OS Build 20348.30000 KB5022842 2023-02-14 | Last updated: 2023-02-22, 16:58 PT Opened: 2023-02-15, 14:42 PT |
|---|
After installing KB5022842 on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below.
Workaround: Please see VMware’s documentation to mitigate this issue.
Resolution: This issue is resolved in VMware ESXi 7.0 U3k, released on February 21st 2023. No update from Microsoft is needed for this issue.
Notes from VMware’s documentation:
- Virtual machines running on any version of vSphere ESXi 8.0.x are not impacted by this issue
- vSphere ESXi 6.7 is End of general Support. For more information, see The End of General Support for vSphere 6.5 and vSphere 6.7 is October 15, 2022.
- If you already face the issue, after patching the host to ESXi 7.0 Update 3k, just power on the affected Windows Server 2022 VMs. After you patch a host to ESXi 7.0 Update 3k, you can migrate a running Windows Server 2022 VM from a host of version earlier than ESXi 7.0 Update 3k, install KB5022842, and the VM boots properly without any additional steps required.
Affected platforms:
- Client: None
- Server: Windows Server 2022
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 | Resolved KB5023705 | OS Build 20348.1129 KB5018421 2022-10-11 | Resolved: 2023-03-14, 10:00 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.
Resolution: This issue was resolved in updates released March 14, 2023 ( KB5023705) or later. Please see KB5020276 to understand the newly re-designed behavior. We have added information about a new Allowlist policy for trusted computer account creators to this KB.
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 | Resolved KB5023705 | OS Build 20348.880 KB5012170 2022-08-09 | Resolved: 2023-03-14, 10:00 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.
Resolution: This issue was resolved in KB5023705 or later updates.
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
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.