Oh, cool. Microsoft melts bug that froze Server 2025 Remote Desktop sessions – Source: go.theregister.com

More than one month after complaints starting flying, Microsoft has fixed a Windows bug that caused some Remote Desktop sessions to freeze.

The issue was introduced in a botched February update to Windows 11 24H2, and Server 2025. Three weeks ago, Microsoft warned Remote Desktop sessions would become unresponsive to keyboard and mouse input, and users had to disconnect and reconnect to restore access.

On Tuesday, Microsoft pushed out a patch for this Server 2025 gremlin, saying: “We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.”

The fix you need is in the KB5055523 release, which Microsoft recommends folks install as soon as possible. The Windows 11 freezing issue was fixed in an earlier update.

• Windows Server 2025 locking up after February patch, no word of when a fix will land
• Free Blue Screens of Death for Windows 11 24H2 users
• Microsoft blames ‘latent code issue’ after Windows 11 upgrades sneak past admin blockades
• Microsoft rated this bug as low exploitability. Miscreants weaponized it in just 8 days

This update is different from the fix Microsoft released last week to correct yet another botched patch. That one was causing Blue Screens of Death for Windows 11 users and was delivered using the OS-slinger’s Known Issue Rollback (KIR) mechanism that allows it to undo buggy patches.

The constant patch-break-patch cycle is, to put it mildly, not a good look for Redmond. Microsoft has had a lot of patching problems so far this year alone, including sending out dodgy error messages, last month’s fix for a software issue that caused USB-connected printers to spew out reams of gibberish, and a situation – Microsoft plans a targeted code fix to solve this – where an update offered some users the chance to install Windows 11 in defiance of corporate policy that prevented them from doing so. The Windows maker said at the time that “a recent service change uncovered a latent code issue, causing impact” – causing users to question what the root cause of such “a latent code issue” might be.

“Microsoft needs to apportion resources better. The largest budget needs to be the Department of Internal Failure, fixing things that all the other departments broke,” one Register reader put it to us. “How long before someone screencaps Clippy AI advising someone to move to Linux or Apple to avoid this sort of thing?”

Maybe Redmond should focus less on trying to shove Copilot into everything and concentrate on fixing the important stuff. ®