The Update BureauWindows Server 2022 · Release Health
Known issues in Windows Server 2022
Problems Microsoft has confirmed for this version, from its official release health notes. 11 still open or mitigated.
Active known issues
Open & Mitigated-
Warnings related to Remote Desktop might not display correctly
After installing KB5082063, Remote Desktop file security warnings might show overlapping text or partly hidden buttons when monitors use different scaling settings.
How to apply the workaround WorkaroundKB5087545 addresses this warning display issue.
-
Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
A limited set of managed devices might ask for the BitLocker recovery key on the first restart after installation. This can happen when BitLocker is on the OS drive, PCR7 is included in the configured profile or equivalent registry setting, System Information reports PCR7 binding as “Not Possible,” the Windows UEFI CA 2023 certificate is in the Secure Boot DB, and the device does not yet use the 2023-signed Windows Boot Manager.
How to apply the workaround Group PolicyRemoving the explicit PCR7 setting lets Windows use its selected default PCR profile. Suspending and resuming BitLocker updates its bindings.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps cmd.exe · Administrator Instructions (.txt)Step-by-step procedure- Before installing the update, open Group Policy Editor or the Group Policy Management Console.
- Go to
Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drivesand setConfigure TPM platform validation profile for native UEFI firmware configurationstoNot Configured. - Run
gpupdate /forceon affected devices. - Where BitLocker is enabled on the C: drive, run the suspend command, then the resume command.
> gpupdate /force> manage-bde -protectors -disable C:> manage-bde -protectors -enable C:
-
Apps might become unresponsive when saving files to cloud-based storage
Some apps may freeze or show errors when opening or saving cloud files. With Outlook data files on OneDrive, Outlook may hang or fail to reopen; sent items may disappear or old emails may download again.
How to apply the workaround WorkaroundContact the app developer about other ways to access the files. For Outlook, move PST files out of OneDrive; webmail is another option if your provider supports it.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Contact the app developer about other ways to access the files.
- For Outlook, move its PST files out of OneDrive or use webmail if your email provider supports it.
-
Windows Server Update Services (WSUS) does not display error details
Windows Server Update Services (WSUS) does not show synchronization error details in its reports after KB5070881 or later updates.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5070881 on affected systems until a fix is released.
-
PSDirect connections failing in hotpatched devices
Microsoft lists an open issue where PowerShell Direct connections might fail on hotpatched devices. It can occur when the host and guest virtual machines are not both fully updated.
How to apply the workaround WorkaroundIf connections fail, update both the host and guest virtual machines with the recommended updates.
-
SMBv1 protocol connectivity
Microsoft lists an open issue where shared files and folders might be unreachable over SMBv1 on NetBIOS over TCP/IP. It can occur if either the SMB client or server has the September 2025 security update.
How to apply the workaround WorkaroundThe page names KB5066782 as an update that addresses this issue.
-
Open Secure Shell service
Microsoft lists an OpenSSH service issue reported after the October 2024 security update. On some enterprise, IoT, and education devices, the service might fail to start and block SSH connections.
How to apply the workaround WorkaroundInstall KB5053596, which addresses this issue.
-
System Guard Runtime Monitor Broker service
Event Viewer might show a System Guard Runtime Monitor Broker service error on devices with updates from January 14, 2025, or later. The error is otherwise silent and should not affect performance, features, or device security.
How to apply the workaround WorkaroundKB5055526 addresses this issue; do not manually start, configure, uninstall, or remove the service or its components.
-
Citrix
Some devices with Citrix Session Recording Agent version 2411 might fail to install the January 2025 security update and undo the changes. Home users are not expected to be affected.
How to apply the workaround WorkaroundUpdate Citrix Session Recording Agent to version 2503 or newer.
-
After installing this security update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device
Some Windows and Linux dual-boot devices might fail to boot Linux and show an SBAT security-policy error.
How to apply the workaround WorkaroundSeptember 2024 and later updates omit the settings that caused the issue; additional improvements to resolve it are included in May 2025 and later updates. Dual-boot systems need no additional steps after installing September 2024 or later updates.
-
After installing KB5036909, you might be unable to [change your user account profile picture](https://support.microsoft.com/en-us/windows/change-your-account-picture-3645cdc7-acab-49d2-76a9-4ce7e5e…
After installing the update, changing a user account profile picture might fail with error 0x80070520. Microsoft says this issue has very limited or no impact for this Windows version.
How to apply the workaround WorkaroundContact Windows support for help if you encounter the issue.
Recently resolved
Fixed in latest updates-
USB Audio Class 1.0 devices with error Code 10 or no output
Some USB Audio Class 1.0 devices might fail to start, produce no audio, or have unresponsive volume or sound settings. KB5129235 addressed symptoms with 8-channel or 3D audio; KB5131080 addressed the remaining symptoms.
How to apply the workaround WorkaroundSome customers reported restoring audio for multichannel modes by switching to 2-channel mode.
-
Users might be unable to sign in to OWA or send emails on Exchange Server
Some on-premises Exchange servers might have OWA sign-in, email sending, or mailbox replication problems after the October 2026 update. The issue is resolved by KB5131080 and later updates.
How to apply the workaround Registry / GPOFor updates released before November 10, 2026, a registry change can temporarily raise the Endpoint Mapper limit. The mitigation is not needed with KB5131080 or later.
-
Remote Desktop Services might stop responding after September 2026 security update
Some organizations might have Remote Desktop Services connection or sign-in failures, or servers stuck at “Please wait for the Remote Desktop Configuration” after the September update. Updates released on or after September 14, 2026, such as KB5129239, resolve this issue; Windows 365 and Azure Virtual Desktop are not affected.
Resolution Fixed in KB5129239Install KB5129239 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
OneDrive shortcut in file explorer might not work in administrator mode
The OneDrive shortcut in File Explorer might not work when File Explorer runs with administrative privileges. This affects the built-in Administrator account and apps run as administrator. KB5099538 resolves this issue.
Resolution Fixed in KB5099535Install KB5099535 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Deleting from recycle bin displays an internal file name
When you permanently delete one item, the confirmation dialog might show its internal Recycle Bin name instead of its original name. KB5099538 resolves this issue.
Resolution Fixed in KB5099535Install KB5099535 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Microsoft Office applications might fail to open from certain third-party apps
Some third-party apps that use OLE automation might fail to open Office apps or documents. KB5099538 resolves this issue.
Resolution Fixed in KB5099535Install KB5099535 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Domain controllers might restart repeatedly after installing KB5082063
In forests with multiple domains that use PAM, domain controllers might crash during startup and restart repeatedly. KB5091575 resolves this; hotpatch devices should use KB5091576.
Resolution Fixed in KB5091572Install KB5091572 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Some devices with Virtual Secure Mode enabled might fail to shut down or hibernate
Some Secure Launch-capable PCs with Virtual Secure Mode enabled might restart instead of shutting down or entering hibernation. Microsoft lists this as a known issue for this update.
How to apply the workaround WorkaroundMicrosoft says KB5075906 addresses this issue.
-
Connection and authentication failures in Azure Virtual Desktop and Windows 365
Some Windows App sign-ins for Remote Desktop connections fail on Windows client devices, affecting Azure Virtual Desktop and Windows 365.
How to apply the workaround WorkaroundMicrosoft lists KB5077793 as the workaround.
-
Unexpected User Account Control (UAC) prompt when doing MSI repair operations
After KB5063871, standard users might see unexpected UAC prompts during MSI repair and related operations. Silent MSI repairs can fail with an error.
How to apply the workaround WorkaroundThe page identifies KB5065432 as the update that addresses this issue.
-
Microsoft Changjie Input Method Editor
After installing KB5062553, some users might have trouble forming or selecting words with the Microsoft Changjie input method for Traditional Chinese. The spacebar might not respond, words might appear incorrectly, or the candidate window might not display properly.
How to apply the workaround WorkaroundInstall KB5063880; Microsoft says it addresses this issue.
-
DHCP Server service
The DHCP Server service might stop responding after KB5060531, affecting IP renewal for clients. KB5062553 resolves this issue.
Resolution Fixed in KB5062572Install KB5062572 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Active Directory Group Policy: Events in local policy
Local policy might show logon auditing as off even when logon events are being recorded. KB5058920 resolved this reporting issue; home users are unlikely to be affected.
Resolution Fixed in KB5058921Install KB5058921 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025, or later
Event Viewer might show a System Guard Runtime Monitor Broker error, Event 7023, after Windows updates released January 14, 2025, or later. It has no expected effect on performance, functionality, or device security; KB5055526 addresses it.
Resolution Fixed in KB5055526Install KB5055526 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections
The OpenSSH service might fail to start after the October 2024 security update, preventing SSH connections. KB5053596 addresses the issue.
Resolution Fixed in KB5053603Install KB5053603 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing this security update, you might experience issues with USB audio devices
USB audio devices might stop working, especially when the audio setup uses a USB 1.0 audio-driver-based DAC. KB5052000 addresses the issue.
Resolution Fixed in KB5051979Install KB5051979 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update
Devices with Citrix Session Recording Agent version 2411 might fail to complete the January 2025 update installation and revert changes on restart. Citrix Session Recording Agent version 2503 and newer resolve the issue.
Resolution ResolvedMicrosoft has resolved this issue in a subsequent update. No manual workaround is required after updating.
-
After installing KB5040437, container networking on Kubernetes might not operate as expected, preventing containers from reaching external networks or communicating between pods
Kubernetes container networking might fail on Server 2022 when using Calico, blocking containers from reaching external networks or communicating between pods. KB5044281 resolves this issue.
Resolution Fixed in KB5044281Install KB5044281 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing the Windows update released on or after July 9, 2024, Windows Servers might affect Remote Desktop Connectivity across an organization
Remote Desktop connections across an organization might be interrupted after a Windows update released on or after July 9, 2024. This issue can occur intermittently when Remote Desktop Gateway uses the legacy Remote Procedure Call over HTTP protocol; sessions might be lost about every 30 minutes. KB5044277 addresses the issue.
Resolution Fixed in KB5044281Install KB5044281 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing the July 9, 2024, Windows security update, you might see a [BitLocker recovery](https://learn.microsoft.com/windows/security/operating-system-security/data-protection/bitlocker/recov…
A BitLocker recovery screen might appear when the device starts after KB5040430, especially when Device Encryption is enabled. KB5041773 resolves this issue.
Resolution Fixed in KB5041160Install KB5041160 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Devices might experience problems with Microsoft 365 Defender
The Microsoft 365 Defender Network Detection and Response service might interrupt network data reporting. KB5041160 resolves this issue.
Resolution Fixed in KB5041160Install KB5041160 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5039227, you might see an issue on cloud-based SQL servers where Azure Synapse SQL Se…
On cloud-based SQL servers, Azure Synapse SQL Serverless Pool databases might enter “Recovery pending,” especially in environments using Customer-Managed Key or Azure Synapse dedicated SQL pool. KB5041054 resolves this issue.
Resolution Fixed in KB5041054Install KB5041054 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing the April 9, 2024 security update on domain controllers (DCs), you might notice a significant increase in [NTLM](https://learn.microsoft.com/windows-server/security/kerberos/ntlm-ove…
Organizations with a very small percentage of primary domain controllers and high NTLM traffic might see a significant increase in NTLM authentication traffic after installing the April 9, 2024 security update. KB5037765 resolves this issue.
Resolution Fixed in KB5037782Install KB5037782 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Windows devices might face VPN connection failures after installing the update dated April 9, 2024, or later
Windows devices might have VPN connection failures after installing the update dated April 9, 2024, or later. KB5037765 resolves this issue.
Resolution Fixed in KB5037782Install KB5037782 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Following installation of KB5035849, Local Security Authority Subsystem Service (LSASS) may experience a memory leak on domain controllers (DCs)
After installing KB5035849, LSASS might leak memory on domain controllers handling Kerberos authentication requests from on-premises and cloud-based Active Directory. Extreme leaks might crash LSASS and trigger an unscheduled domain controller reboot. KB5037425 addresses this issue.
Resolution Fixed in KB5037422Install KB5037422 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After you install KB5034129, chromium-based internet browsers, such as Microsoft Edge, might not open correctly
After installing KB5034129, Chromium-based browsers, including Microsoft Edge, might open to a white screen and become unresponsive. Devices with browser-specific Image File Execution Options registry entries might be affected. KB5034770 resolves the issue.
How to apply the workaround WorkaroundBefore KB5034770, remove the browser's Image File Execution Options registry key and restart the device. If the key has values beyond “(Default),” removing it might also remove browser startup configurations.
Step-by-step workaround instructionsShow steps Hide steps5 stepsStep-by-step procedure- Open Registry Editor by searching for
regeditin the Start menu. - Go to
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\. - Find the key for the affected browser, such as
msedge.exeorchrome.exe, and inspect its values. - If the only value is “(Default),” delete the browser key. If there are additional values, deleting the key might remove browser startup configurations.
- Restart the device.
- Open Registry Editor by searching for
No known issue matches these filters.