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. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.

Resolved issues

Issue details

August 2024

Printing jobs using LPD protocol might fail with the July 2024 security update

After installing the July 2024 Windows security update, released July 9, 2024 (KB5040437), and later updates, you might encounter issues when trying to print documents using the Line Printer Daemon (LPD) protocol, which is a deprecated protocol.

People using Home or Pro editions of Windows for personal use are unlikely to face this issue as the LDP is a protocol used more often by IT departments to receive a print job on a printer or a server.

Note: The Line Printer Daemon protocol (LPR/LPD) is deprecated. When this feature is eventually removed, clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the Windows Standard Port Monitor.

Resolution: This issue is resolved by the Windows August 2024 security updates released August 13, 2024 (KB5041160), and later updates. We recommend you install the latest update for your device. It contains important improvements and issue resolutions, including this one.

Affected platforms:

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

July 2024

Devices might boot into BitLocker recovery with the July 2024 security update

After installing the July 2024 Windows security update, released July 9, 2024 (KB5040437), you might see a BitLocker recovery screen upon booting your device. This screen does not commonly appear after a Windows update. You are more likely to face this issue if you have the Device Encryption option enabled in Settings under Privacy & Security -> Device encryption. Resulting from this issue, you might be prompted to enter the recovery key from your Microsoft account to unlock your drive.

Resolution: This issue was resolved by Windows updates released August 13, 2024 (KB5041160), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.

If you install an update released August 13, 2024 (KB5041160) or later, you do not need to use a workaround for this issue. If you are using an update released before August 13, 2024, and have this issue, your device should proceed to start up normally from the BitLocker recovery screen once the recovery key has been entered. You can retrieve the recovery key by logging into the BitLocker recovery screen portal with your Microsoft account. Detailed steps for finding the recovery key are listed here: Finding your BitLocker recovery key in 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 Enterprise 2015 LTSB
• ​Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008

Network data reporting from Microsoft 365 Defender may be interrupted

Devices which have installed Windows Server updates released June 11, 2024 (KB5039227) might experience problems with Microsoft 365 Defender. The Network Detection and Response (NDR) service might encounter issues, resulting in an interruption of network data reporting.

IT administrators may confirm they’re affected by this issue with a notification that appears in the service health page, located in the Microsoft 365 admin center. The status of NDR can also be seen in the service health page.

Please note that although this interruption can hinder certain Defender features such as Device Inventory and Incident Response, other functionality – such as Vulnerability Management and Cloud Apps – should continue to operate as expected. 

Resolution: This issue was resolved by Windows updates released August 13, 2024 (KB5041160), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.

Affected platforms:

• ​Client: None
• ​Server: Windows Server 2022

CrowdStrike issue impacting Windows endpoints causing an error message

Microsoft has identified an issue impacting Windows endpoints which are running the CrowdStrike Falcon agent, developed by CrowdStrike Holdings. Following updates released and delivered by CrowdStrike on July 18, 2024, devices running the Falcon agent may encounter an error message on a blue screen and experience a continual restarting state.

Affected systems might restart repeatedly and require recovery operations in order to restore normal use.

Updated July 25, 2024: Microsoft released further guidance on Windows resiliency: Best practices and the path forward. Read more about how we are working in close cooperation to improve resiliency across the Windows ecosystem and explore best practices you can use to support resiliency in your organization.

Updated July 22, 2024: Microsoft has released a third mitigation option for this issue impacting Windows clients and servers. If devices are unable to recover with the two previous options mentioned below, IT admins can use PXE to remediate. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on prerequisites and configurations to use PXE Recovery.

Updated July 21, 2024: As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. Based on customer feedback, this new release includes a new option for recovery using safe boot, the option to generate ISO or USB, a fix for ADK detection when the Windows Driver Kit is installed, and a fix for the USB disk size check. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on using the signed Microsoft Recovery Tool.

Updated July 20, 2024: Microsoft has released KB5042426, which contains step-by-step guidance for Windows Servers hosted on-premises that are running the CrowdStrike Falcon agent and encountering a 0x50 or 0x7E error message on a blue screen. We will continue to work with CrowdStrike to provide the most up-to-date information available on this issue. 

A new USB Recovery Tool is available to help IT admins expedite the repair process. The new tool can be found in the Microsoft Download Center. Read more about the new recovery tool and usage instructions at New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints.

Updated July 19, 2024: A new Knowledge Base article, KB5042421, with additional step-by-step guidance for Windows 11 and Windows 10 clients is now available. We will continue to work with CrowdStrike to provide up-to-date mitigation information as it becomes available.

To mitigate this issue ahead of additional resolution options, you can follow these steps:

1. ​Start Windows into Safe Mode or the Windows Recovery Environment.
2. ​Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
3. ​Locate the file matching “C-00000291*.sys” and delete it.
4. ​Restart the device.
5. ​Recovery of systems requires a Bitlocker key in some cases.

For Windows Virtual Machines running on Azure follow the mitigation steps in Azure status.

Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - CrowdStrike Blog.

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 Enterprise LTSC 2019
• ​Server: Windows Server 2022; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

June 2024

Synapse SQL Serverless Pool databases go on "Recovery pending" state

Following the installation of the Windows security update released June 11, 2024 (KB5039227), you might see an issue on cloud-based SQL servers where Azure Synapse SQL Serverless Pool databases go on "Recovery pending" state. This issue is more likely to affect environments utilizing Customer-Managed Key (CMK) and Azure Synapse dedicated SQL pool.

Resolution: This issue was resolved in the out-of-band (OOB) update KB5041054, which is only available via the Microsoft Update Catalog. Since this is a cumulative update, you do not need to apply any previous update before installing KB5041054, as it supersedes all previous updates for affected versions. Installation of this OOB will require a device restart. If your organization uses the affected platforms and hasn’t yet deployed the June 2024 Windows security update yet, we recommend you apply this OOB update instead.

In addition, a resolution was rolled out on the service-side to enterprises using Azure SQL. If your organization is still observing this issue, please reach out to Support for business.

Affected platforms:

• ​Server: Windows Server 2022; Azure Stack HCI, version 22H2
• ​Client: None

April 2024

Edge updates might cause Microsoft Copilot app to show up in Installed apps

Updates to Edge browser version 123.0.2420.65, released on March 28, 2024, and later, might incorrectly install a new package (MSIX) called ‘Microsoft chat provider for Copilot in Windows’ on Windows devices. Resulting from this, the Microsoft Copilot app might appear in the Installed apps in Settings menu.

It is important to note that the Microsoft chat provider for Copilot in Windows does not execute any code or process, and does not acquire, analyze, or transmit device or environment data in any capacity.

This package was intended to prepare some Windows devices for future Windows Copilot enablement and was not intended for all devices. Although the component installed as part of this issue can cause the Microsoft Copilot app to be shown as part of the Installed apps, this component does not fully install or enable Microsoft Copilot.

Note: Edge browser version 124.0.2478.51, released on April 18, 2024, contains a change by which the chat provider for Copilot in Windows will not continue to be installed on every device.

Resolution: This issue is now resolved with Edge browser updates released on April 26, 2024, and June 13, 2024. Edge version 124.0.2478.67 was released on April 26 and removed the package ‘Microsoft chat provider for Copilot in Windows’ from all servers affected by this issue. Edge version 126.0.2592.56 was released on June 13, 2024, and removed the same package from all Windows client versions affected by this issue. The ‘Microsoft Copilot’ entry will not show in the Installed apps list in the Settings menu once the Edge browser is updated.

Affected platforms:

Client: Windows 11, version 23H2, Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2

Server: Windows Server 2022

VPN connections might fail after installing the April 2024 security update

Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036909) or the April 2024 non-security preview update.

Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037782), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.

Affected platforms:

Client: Windows 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2. 

Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.

NTLM traffic issue after installing the April 2024 security update

After installing the April 2024 security update (KB5036909) on domain controllers (DCs), you might notice a significant increase in NTLM authentication traffic. This issue is more likely to affect Active Directory (AD) deployments already servicing a large number of NTLM authentication requests where a small number of Primary Domain Controllers (PDCs) are supporting a large number of read-write Backup Domain Controllers (DCs) and Read Only Domain Controllers (RODCs).

Note: In rare instances, Windows Servers running the Domain Controller (DC) role might experience Local Security Authority Subsystem Service (LSASS) crashes resulting in a reboot. 

Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037782), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.

Affected platforms:

Client: none

Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008

March 2024

Issue with Kerberos requests on domain controllers may cause LSASS memory leaks

Following installation of the March 2024 security update, released March 12, 2024 (KB5035857), Local Security Authority Subsystem Service (LSASS) may experience a memory leak on domain controllers (DCs). This is observed when on-premises and cloud-based Active Directory Domain Controllers service Kerberos authentication requests.

Extreme memory leaks may cause LSASS to crash, which triggers an unscheduled reboot of underlying domain controllers (DCs).

Note: This issue does not occur on Home devices. It affects only environments in organizations using some Windows Server platforms.

Resolution: This issue was resolved in the out-of-band (OOB) update KB5037422, which is only available via the Microsoft Update Catalog. We strongly recommend you do not apply the March 2024 security update on DCs and install KB5037422 instead. As this is a cumulative update, you do not need to apply any previous update before installing KB5037422. To install this update, search for KB5037422 in the Microsoft Update Catalog. The OOB update can then be manually imported to Windows Server Update Services (WSUS) and Configuration Manager. For guidance, see WSUS and the Microsoft Update Catalog.

If you manage update catalogs in Configuration Manager, please check the section Import updates. If you with you work with software update synchronization in Configuration Manager, review the steps on Import updates from the Microsoft Update Catalog. For more information about the Microsoft Update Catalog, visit Microsoft Update Catalog - FAQs. 

Important: This update (KB5037422) is not available from Windows Update and will not install automatically.

Affected platforms:

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

January 2024

The January 2024 Windows RE update might fail to install

Devices attempting to install the January 2024 Windows Recovery Environment update (KB5034439) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.

Resulting from this error, the following message might be displayed.

• ​"0x80070643 - ERROR_INSTALL_FAILURE"

Important: If your Windows device does not have a recovery environment configured, you do not need this update (KB5034439). In this case, the error can be ignored.

To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:

1. ​Open a Command Prompt window (cmd) as admin.
2. ​To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".

Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.

The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action. For guidance on making this change, review the following resources:

• ​A code script can be used to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE. See Extend the Windows RE Partition.
• ​Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.

Completion of these manual steps will allow the installation of this update to succeed.

Affected platforms:

• ​Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
• ​Server: Windows Server 2022

December 2023

Printer names and icons might be changed and HP Smart app automatically installs

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:

1. ​​Some Windows devices are installing the HP Smart app.
2. ​​Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
3. ​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. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device. To learn more about critical and recommended troubleshooters, see Keep your device running smoothly with recommended troubleshooting.

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

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

February 2023

Devices with locale set to Croatia might not utilize the expected currency

The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device's currency for purchases or other transactions. 

Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.

Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.

1. ​Open the "Windows Region" settings. This can be done in one of the following ways:
   1. ​Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
   2. ​On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
2. ​In the Region settings, choose one of the 2 locales for Croatia:
   1. ​Croatian (Bosnia & Herzegovina)
   2. ​Croatian (Croatia)
3. ​In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
4. ​Change the currency symbol from "KN" to Euro, "€"

Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.

Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.

Resolution: This issue was resolved in updates released March 12, 2024 (KB5035857) and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.

Affected platforms:

• ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; 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
• ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

February 2022

Apps or devices might be unable to create Netlogon secure channel connections

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 has provided the following documentation regarding devices from Riverbed Technology that are configured as RODCs: Information about devices from Riverbed Technology that are configured as RODCs. For further details or resolution guidance applicable to other network devices, contact the developer or manufacturer of the device.

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

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.