The Update BureauWindows Server 2016 · Release Health
Known issues in Windows Server 2016
Problems Microsoft has confirmed for this version, from its official release health notes. 2 still open or mitigated.
Active known issues
Open & Mitigated-
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.
-
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.
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.
-
CompatTelRunner.exe might close unexpectedly
Some Windows Server 2016 devices might log recurring CompatTelRunner.exe errors. These errors do not affect device functions, and KB5123099 resolves the issue.
How to apply the workaround WorkaroundDismiss the related event log warnings temporarily until the resolving update is installed.
-
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 Controller lookup might fail for 15-character hostnames
On Windows Server 2016 systems with a 15-character hostname, domain controller discovery might fail after KB5087537. KB5094122 resolves the issue.
Resolution Fixed in KB5094122Install KB5094122 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Remote Desktop security warnings might not display correctly
The security warning shown when opening Remote Desktop files might display incorrectly, with overlapping text or partly hidden buttons, when multiple monitors use different display scaling settings. Updates released on and after May 12, 2026, such as KB5087537, resolve this issue.
Resolution Fixed in KB5087537Install KB5087537 (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.
-
Message Queuing (MSMQ)
In enterprise or managed environments, including clustered MSMQ under load, queues might become inactive, IIS sites might show resource errors, and applications might fail to write messages. KB5074974 resolved this issue.
Resolution Fixed in KB5074975Install KB5074975 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
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.
-
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.
-
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.
-
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.
No known issue matches these filters.