Cannot Start Remote Desktop Service After Windows Updates?

If Remote Desktop Service (TermService) fails to start after a Windows update, the fix usually involves repairing the service registry entry, adjusting its startup type, or installing the latest update rollup. This article explains why updates break the service and provides step-by-step fixes that work on Windows 10 and 11.

Why Windows Updates Affect Remote Desktop

Windows updates occasionally modify system files, registry keys, or security policies that the Remote Desktop service depends on. The most common triggers are:

• Security patches that tighten network or authentication settings, which can disable Remote Desktop if the new defaults conflict with your configuration.
• Service startup type resets – some updates reset TermService to “Manual” or “Disabled” to reduce attack surface, even if you had it set to “Automatic.”
• Corrupted or partially installed updates – a failed update can leave the service’s files or registry entries in an inconsistent state.
• Group Policy changes – updates may refresh policy settings that override local service configuration.

If the service fails to start, you’ll likely see error 1058 (service disabled), 1068 (dependency failure), or a generic “The service did not respond to the start or control request in a timely fashion.”

Quick Checks Before You Fix

Before diving into registry edits, verify these basics:

1. Press Win + R, type services.msc, and find Remote Desktop Services. Check its startup type – it should be Automatic.
2. Make sure the following dependencies are running: Remote Desktop Configuration, Remote Desktop Services UserMode Port Redirector, and Remote Procedure Call (RPC).
3. Open Settings → System → Remote Desktop and confirm the toggle is On. If it’s off, turn it on – this often resets the service startup type.
4. Check if the service is set to Disabled in Group Policy (gpedit.msc) under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections.

If any dependency is stopped, start it manually. If the service still won’t start, proceed to the registry fix below.

Fix 1: Repair the Service Registry Entry

Windows updates can corrupt the ImagePath or Start value in the TermService registry key. To repair it:

1. Press Win + R, type regedit, and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService
2. Double-click Start (a DWORD) and set its value to 2 (Automatic). If it’s set to 4 (Disabled), change it to 2.
3. Double-click ImagePath and verify it reads:
   %SystemRoot%\System32\svchost.exe -k NetworkService – if it’s missing or wrong, set it to that exact string.
4. Close regedit and restart the service via services.msc or the command: net start TermService (run as administrator).

If the service starts, you’re done. If not, continue to the next fix.

Fix 2: Reinstall the Remote Desktop Listener

The Remote Desktop listener (RDP-Tcp) can become corrupted after an update. To recreate it:

1. Open Command Prompt as Administrator.
2. Run wmic /namespace:\\root\cimv2\TerminalServices PATH Win32_TSGeneralSetting Set TerminalServerMode=1 – this forces the service to recreate its listener.
3. Alternatively, use regedit to delete the RDP-Tcp subkey under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations. The service will recreate it on restart.
4. Restart the Remote Desktop Services service.

Be careful – deleting the wrong key can break other terminal server settings. Only delete RDP-Tcp if you’re comfortable with registry editing.

Fix 3: Run System File Checker and DISM

Corrupted system files are a frequent cause. Run these tools in an elevated Command Prompt:

1. sfc /scannow – this scans and repairs protected system files. It may take 10-15 minutes.
2. If SFC finds errors, run DISM /Online /Cleanup-Image /RestoreHealth – this fixes the component store that SFC relies on.
3. Restart your PC and try starting the Remote Desktop service again.

These tools are built into Windows and safe to run; they won’t remove personal files.

Fix 4: Install the Latest Cumulative Update

If the problem appeared after a specific update, Microsoft may have released a subsequent patch that resolves the issue. Check Settings → Windows Update and install all pending updates, including optional ones. If you suspect a particular update caused the break, you can uninstall it temporarily:

1. Go to Settings → Windows Update → Update history → Uninstall updates.
2. Select the most recent update and uninstall it, then restart.
3. If Remote Desktop works again, reinstall the update after a few days – a newer version may fix the regression.

Only uninstall updates as a last resort, and always create a restore point first (System Properties → System Protection).

When to Use a System Restore or Reset

If none of the above fixes work, you have two stronger options:

• System Restore – roll back to a restore point from before the update. This doesn’t affect personal files, but it may remove recently installed apps. Go to Control Panel → Recovery → Open System Restore.
• In-place Upgrade Repair – download the Windows 11/10 ISO from Microsoft’s website, mount it, and run setup.exe. Choose “Keep personal files and apps.” This reinstalls Windows while preserving your data and programs, and it often fixes stubborn service issues.

Both methods are safe if you back up important files first.

Frequently Asked Questions

Why does Remote Desktop get disabled after every Windows update?

Some security-focused updates intentionally disable Remote Desktop to reduce exposure, especially if the feature is not actively used. If you rely on it, you may need to re-enable it after each major update. You can automate this by setting the service to Automatic and enabling the feature via Group Policy, but updates may still override it.

Can I prevent Windows from touching Remote Desktop settings?

Not fully, but you can reduce the risk by deferring feature updates (Settings → Windows Update → Advanced options) and by keeping your system on the latest stable build. Also, ensure you have a restore point before installing updates.

Is it safe to edit the registry to fix Remote Desktop?

Yes, if you follow the steps carefully and back up the registry first (File → Export). Only modify the specific keys mentioned. Incorrect changes to other keys can cause system instability.

What if I see error 0x80004005 when starting the service?

This generic error often indicates permission issues. Run the service as an administrator or check the event log (Event Viewer → Windows Logs → System) for more details. The fixes above (especially SFC and DISM) usually resolve it.

Does this affect Windows 10 and 11 the same way?

Yes, the service and registry structure are essentially identical in both versions. The steps in this guide apply to Windows 10 and 11, and also to Windows Server 2016/2019/2022 with minor differences in menu names.

Related

• Network Resource Unavailable Error on Windows 10? Fix It
• Transfer WhatsApp From iPhone to Xiaomi: Full Guide
• Migrate GPU Workloads from CoreWeave to AWS, Azure, or GCP