RDP Session Freeze — Keyboard and Mouse Unresponsive After February 2025 Updates (Windows Server 2025 / Windows 11 24H2)

Indicators

• RDP session appears connected and remote desktop is visible, but keyboard input is not registered by the remote host
• Mouse cursor moves on screen but clicks produce no response within the RDP session
• Session freeze occurs after applying Windows updates released February 2025 or later — no network disconnection involved
• Affected hosts are running Windows Server 2025 or Windows 11 24H2
• TermService (Remote Desktop Services) shows as running but session remains non-interactive

Likely causes

• Regression introduced in Windows cumulative or security updates released from February 2025 onwards, affecting RDP input handling on Windows Server 2025 and Windows 11 24H2
• Input processing within established RDP sessions is broken at the OS level — the connection layer itself remains functional, making this distinct from RDP disconnect issues

Diagnostic steps

1. Confirm OS version and build using alternative access method (console/IPMI): run 'winver' or 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber' in PowerShell
   Verify the system is running an affected OS version (Windows Server 2025 or Windows 11 24H2) before proceeding with targeted remediation
2. Review installed Windows updates: 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20' or check Settings > Windows Update > Update History
   Identify updates applied from February 2025 onwards and correlate freeze onset with a specific KB number
3. Attempt RDP connection and confirm freeze symptom: establish session, open Notepad and type, test mouse clicks — note whether session remains visually connected while input is unresponsive
   Distinguish this freeze from RDP disconnects — confirms session is connected but input non-functional, matching known bug signature
4. Check System and Application Event Logs via console access: 'Get-WinEvent -LogName System -MaxEvents 100 | Where-Object {$_.LevelDisplayName -eq "Error" -or $_.LevelDisplayName -eq "Warning"} | Select-Object TimeCreated, Id, Message | Format-List' — filter for events from TermService and RdpCoreTS sources
   Identify RDP service, TermService, or RdpCoreTS input-related error events that may confirm freeze timing or provide additional diagnostic context
5. Check RDP-related service status: 'Get-Service -Name TermService, UmRdpService | Select-Object Name, Status, StartType'
   Confirm Remote Desktop Services and UserMode Port Redirector services are running and have not crashed or hung
6. After rolling back the suspect update, establish an RDP session and confirm keyboard and mouse remain responsive during sustained use; verify removal with 'Get-HotFix | Sort-Object InstalledOn -Descending' to confirm the KB is no longer listed
   Validate that rollback was successful and the freeze regression is resolved

Resolution path

• 1. Check Microsoft Update Catalog and Windows Release Health dashboard (https://learn.microsoft.com/en-us/windows/release-health/) for an out-of-band (OOB) or superseding cumulative update that addresses this RDP freeze regression — apply if available
• 2. If no fix update is available, uninstall the problematic February 2025 or later cumulative update via console/IPMI access: 'wusa /uninstall /kb:<KBNumber> /quiet /norestart' (replace <KBNumber> with identified update), then reboot
• 3. After uninstalling problematic update, pause Windows Update to prevent automatic re-installation: Settings > Windows Update > Advanced Options > Pause updates, or via Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > 'Select when Quality Updates are received')
• 4. Monitor Microsoft's official Windows release health page and tech news sources for announcement of a patch resolving the Server 2025 RDP freeze, then apply promptly through a controlled change window
• 5. If update rollback is not operationally feasible, implement a session monitoring or auto-reconnect solution to detect frozen sessions and alert affected users while awaiting Microsoft's official fix

Prevention

• Implement staged update deployment using WSUS, Microsoft Endpoint Configuration Manager, or Windows Update for Business deferral rings — test cumulative updates on non-production pilot group for at least 7 days before deploying to RDP-dependent servers
• Maintain VM snapshots or bare-metal backup images of critical RDP hosts immediately before each monthly Patch Tuesday update cycle, enabling rapid rollback if regression is introduced
• Subscribe to Microsoft Windows Release Health RSS feed and monitor BleepingComputer or Patch Tuesday reporting channels to receive early warning of known regressions before they reach production

Tools

• Windows Update Catalog (identify and download specific KB updates or replacements)
• wusa.exe (uninstall specific Windows update KBs from command line)
• Event Viewer / Get-WinEvent (review System and Application logs for RDP-related errors including TermService and RdpCoreTS)
• Get-HotFix / Get-ComputerInfo (confirm installed updates and OS build)
• Get-Service (verify RDP service health)
• Windows Recovery Environment / WinRE (rollback if needed)
• IPMI/iDRAC/Hyper-V VMConnect (alternative console access)
• Microsoft Windows Release Health Dashboard (track fix availability)

References

• BleepingComputer — RDP sessions freeze after February 2025 updates (Server 2025 acknowledged)
• Microsoft Windows Release Health Dashboard
• Microsoft Update Catalog