Windows Fixes

How to Fix Windows Update Error 1053

Issue type: Windows Update service failure — Error 1053. Applies to Windows 10 and Windows 11.

Short answer: To fix error 1053 Windows Update, restart the Windows Update service, then check its dependency services. Error 1053 means the service did not respond to a start or control request in time. If restarting wuauserv works only temporarily, the update service state is probably corrupted and you should reset Windows Update components.

Fix Error 1053 Windows Update: What It Means

Error 1053 is a Service Control Manager timeout. In plain English, Windows tried to start, stop, or control a service, but the service did not respond quickly enough. For Windows Update, the usual targets are wuauserv, BITS, Cryptographic Services, or a dependency service that Windows Update needs before it can run.

You may see it in three places:

  • A Services.msc popup when starting Windows Update manually.
  • Event Viewer as Event ID 7000 or 7009.
  • Windows Update failing to check for updates because the service never starts properly.

What to Do First: Restart Windows Update Service

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Windows Update.
  3. Right-click it and choose Stop.
  4. Wait 20 seconds.
  5. Right-click it again and choose Start.
  6. Open Settings > Windows Update and click Check for updates.

If the service starts cleanly and Windows Update works, the timeout was temporary. If error 1053 returns, continue below.

Fix 2: Restart Services with CMD

Use this if Services.msc is frozen, the Start/Stop buttons are grayed out, or the service is stuck at Starting.

net stop wuauserv
net stop bits
net stop cryptSvc
net start cryptSvc
net start bits
net start wuauserv

If any command says the service is not started, continue with the next command. The goal is to force the service stack into a clean state.

Fix 3: Check Required Dependency Services

Windows Update cannot respond correctly if required services are stopped or disabled. In services.msc, check these:

  • DCOM Server Process Launcher: Running, Automatic
  • RPC Endpoint Mapper: Running, Automatic
  • Windows Management Instrumentation: Running, Automatic
  • Cryptographic Services: Running, Automatic
  • Background Intelligent Transfer Service: Manual or Manual (Trigger Start), not Disabled

If any dependency is disabled, change it back to Automatic or Manual as appropriate, then restart Windows Update.

Fix 4: Confirm Windows Update Is Not Disabled

Some optimizer tools, debloat scripts, and group policies disable Windows Update. That can create repeated service timeout errors.

  1. Open services.msc.
  2. Double-click Windows Update.
  3. Set Startup type to Manual.
  4. Click Apply.
  5. Start the service.
  6. Restart the PC and test Windows Update again.

Windows Update does not need to be Automatic on every home PC. Manual trigger start is normal. Disabled is the problem.

Fix 5: Reset Windows Update Components

If error 1053 returns after every restart, reset the update infrastructure instead of restarting one service repeatedly. The reset process stops update services, renames SoftwareDistribution and catroot2, then restarts the services cleanly. Use the full reset Windows Update components guide for the complete command sequence.

Common Mistake

The common mistake is running SFC and DISM first. Those tools are useful for system file corruption, but error 1053 is usually a service startup timeout. Restart the service, check dependencies, and reset update components before doing larger Windows image repairs.

Best Next Step

If error 1053 continues, open Event Viewer and filter Windows Logs > System for Service Control Manager. Look for Event ID 7000 and 7009 at the exact time the error appeared. That entry shows which service timed out and gives you the correct next target. Microsoft lists Service Control Manager codes in Service Control Manager error codes — Microsoft Learn.

If error 1053 keeps returning after a simple service restart, use reset Windows Update components after checking the Windows Update cache.

Frequently Asked Questions

What does Windows Update error 1053 mean?

It means a Windows service did not respond to the Service Control Manager in time. For Windows Update, that usually means wuauserv or a dependency is stuck, disabled, or waiting on a corrupted update state.

Is error 1053 a Windows Update error code?

It is a service control error that can affect Windows Update. You usually see it when the Windows Update service fails to start or respond.

Can I disable Windows Update to stop error 1053?

No. Disabling Windows Update hides the symptom but leaves the PC without security updates. Pause updates temporarily if needed, but fix the service state instead of disabling it.

Why does error 1053 come back after reboot?

Recurring error 1053 means the service starts into a broken state every time. Check dependencies first, then reset Windows Update components.

Do I need DISM for error 1053?

Not first. Use DISM only if the service-level fixes fail and Event Viewer or Windows Update logs suggest deeper component corruption.