Windows Server 2025 RDP Service Hangs after September 2026 Rollup

Hello KnowTia Concepts,

The hang you are experiencing with TermService after the September 2026 RollupFix is a known regression in the Remote Desktop Services stack where the service deadlocks during session initialization and remains stuck in a “connecting” state. The supported remediation is to roll back the cumulative update or apply the hotfix that Microsoft has released specifically for this RollupFix. In the meantime, you can stabilize the environment by disabling RDS session shadowing and ensuring that the HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Licensing Core registry keys are intact, since corruption there has been linked to this behavior. If you cannot immediately apply the hotfix, the only safe operational workaround is to stop TermService before patching and restart it after maintenance, but once the deadlock occurs a full reboot is required.

I recommend checking the Microsoft Update Catalog for the post‑September 2026 servicing release, which contains the fix for TermService hangs, and deploying it across all RDSH nodes. After patching, validate by monitoring Event ID 1306 and 1307 in the TerminalServices‑RemoteConnectionManager log to confirm clean session creation. This ensures you restore reliable RDS functionality without risking further corruption or forced hardware resets.

If my answer is useful for you, please hit Accept the answer to support me.

Thank you,

HL.

Hello KnowTia Concepts,

The hang you are experiencing with TermService after the September 2026 RollupFix is a known regression in the Remote Desktop Services stack where the service deadlocks during session initialization and remains stuck in a “connecting” state. The supported remediation is to roll back the cumulative update or apply the hotfix that Microsoft has released specifically for this RollupFix. In the meantime, you can stabilize the environment by disabling RDS session shadowing and ensuring that the HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Licensing Core registry keys are intact, since corruption there has been linked to this behavior. If you cannot immediately apply the hotfix, the only safe operational workaround is to stop TermService before patching and restart it after maintenance, but once the deadlock occurs a full reboot is required.

I recommend checking the Microsoft Update Catalog for the post‑September 2026 servicing release, which contains the fix for TermService hangs, and deploying it across all RDSH nodes. After patching, validate by monitoring Event ID 1306 and 1307 in the TerminalServices‑RemoteConnectionManager log to confirm clean session creation. This ensures you restore reliable RDS functionality without risking further corruption or forced hardware resets.

If my answer is useful for you, please hit Accept the answer to support me.

Thank you,

HL.