Microsoft has released an emergency out-of-band update to address a Windows Server bug leading to Remote Desktop connection and performance issues.
“Microsoft is releasing Out-of-band (OOB) updates today, January 4, 2022, to resolve issues in which Windows Server might experience a black screen, slow sign in, or general slowness,” the company explains.
“You might also be unable to use Remote Desktop to reach the server. In some circumstances, the server might stop responding.”
Affected platforms include Windows Server 2022, Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2.
The updates that address this issue are not available from Windows Update and will not install automatically on affected systems.
You can also download the update from the Microsoft Update Catalog. Enterprise admins can import this update into Windows Server Update Services (WSUS) manually using the instructions available in the Microsoft Update Catalog.
KB5010196 is a cumulative update, so you will not have to deploy previous Windows Server updates before installing it.
Fix not yet available for all impacted Windows versions
Microsoft has not yet released the updates for Windows Server 2022, Windows Server 2016, and Windows Server 2012 R2, but it’s working on a fix and will provide a solution in the coming days.
In November, Redmond released out-of-band updates to fix authentication issues linked to Kerberos delegation scenarios impacting Domain Controllers (DC) running supported versions of Windows Server.
As Microsoft explained, on impacted systems, end-users couldn’t sign into services or applications using Single Sign-On (SSO) in Active Directory on-premises or hybrid Azure Active Directory environments.
One week earlier, Microsoft had to issue another set of emergency updates to address Windows 11 issues while opening or using some built-in apps and features due to an expired Microsoft digital certificate.
Before this, last year, the company also pushed a string of out-of-band updates to fix printing issues, WiFi crashes, PDF opening issues, the Windows PrintNightmare zero-day, and another series of printing issues.
To read the original article: