You open Windows Update and get an error instead of updates. Or the troubleshooter reports that the Windows Update service is not running. You start it manually — and it stops again, or refuses to start at all. On a Lenovo laptop, this is a servicing problem wearing a services costume: the service is usually fine, but something it depends on is broken.

The Windows Update service (wuauserv) does not work alone. It leans on BITS, the DCOM launcher, the servicing stack, and correct registry permissions. When any of those break, wuauserv is the part that visibly fails. Fix the foundation and the service stays up.

Work through these in order — diagnose first, then act.

Why this happens

  • Startup type set to Disabled. Debloater or optimizer tools commonly disable wuauserv.
  • Broken dependencies. BITS or DCOM launcher failing takes wuauserv down with them.
  • Corrupted servicing stack. Damaged components the service needs at startup.
  • Permission damage on service registry keys. Incorrect ACLs prevent the service from starting.
  • Third-party tools actively stopping it. “Privacy” or “update blocker” utilities fighting Windows.
  • Corrupted SoftwareDistribution folder. A damaged data folder crashing the service on launch.
  • Malware disabling updates. Some malware disables wuauserv to prevent security patches.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Set the correct startup type and start the service

Press Win+R, type services.msc, and press Enter. Find “Windows Update,” double-click it, and check the Startup type — if it says Disabled, change it to “Manual.” Click Apply, then click Start.

If it starts and stays running, check Windows Update immediately — the problem may have been just the disabled state. If it stops within a minute or throws an error on start, note the exact error message; “Error 1053” or dependency errors point to the next fixes. Do not set it to Disabled under any circumstances.

Fix 2: Check and repair the dependency services

In the Windows Update service properties, go to the Dependencies tab. The key ones: Background Intelligent Transfer Service (BITS) and DCOM Server Process Launcher. Start each dependency manually in services.msc — set BITS to Manual if disabled, and start it.

If a dependency itself will not start, that is your real problem: fix BITS first (same technique — check its startup type, clear its queue if needed), then return to wuauserv. Services fail in chains, and the visible failure is always at the end of the chain. Fix from the bottom up.

Fix 3: Hunt down the tool that keeps disabling it

If wuauserv runs fine after Fix 1 but is disabled again after a reboot, something is actively changing it. Check for installed “Windows update blocker,” “privacy,” “debloater,” or “optimizer” utilities in Settings, Apps — uninstall any you find.

Also check Task Scheduler (Win+R, taskschd.msc) for suspicious tasks that run at startup and modify services. And check Lenovo Vantage’s settings for any aggressive “optimization” features — while Vantage itself does not disable wuauserv, bundled third-party tools sometimes do. The service should survive reboots untouched once the interfering tool is gone.

Fix 4: Reset the SoftwareDistribution folder

A corrupted data folder can crash wuauserv at startup:

  1. Open Command Prompt as administrator.
  2. Run: net stop wuauserv, then net stop bits
  3. Rename the folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  4. Run: net start bits, then net start wuauserv
  5. Check Windows Update — it rebuilds the folder automatically.

Renaming (rather than deleting) preserves the old data as a fallback. If the service starts cleanly afterward, the old cache was the crasher. This is also the moment to run the Windows Update troubleshooter (Settings, System, Troubleshoot) to catch any remaining configuration issues. Once the service is running, if downloads stall rather than fail, the stuck downloading guide for 24H2 picks up from there.

Fix 5: Repair servicing permissions and components

If the service still will not stay up, the servicing infrastructure needs repair:

  1. Open Command Prompt as administrator.
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. Run: sfc /scannow
  4. Restart.

These restore damaged system files and servicing components that wuauserv depends on. For permission-specific damage, the troubleshooter in Fix 4 usually handles service ACLs; persistent permission errors may need the in-place repair in Fix 7. Microsoft documents servicing repair in their Windows support resources .

Fix 6: Scan for malware and check system integrity

Malware that disables Windows Update to avoid removal is a real threat model. Run a full scan with Windows Security (Virus & threat protection, Scan options, Full scan). Also check Task Manager’s Startup tab and the Run registry keys for unfamiliar entries.

If the scan finds and removes threats, restart and verify wuauserv stays running — then immediately check for updates, because a machine whose updates were suppressed may be months behind on security patches. Install everything offered before doing anything else. If your Lenovo has broader update problems, the cumulative update failure guide covers the install side.

Fix 7: In-place repair upgrade for persistent failures

When the service will not run despite correct settings, healthy dependencies, a clean cache, and repaired components, rebuild the servicing stack with an in-place upgrade: mount the Windows 11 ISO from the official Microsoft download page , run setup.exe, choose “Keep personal files and apps.”

This reinstalls Windows over itself, reconstructing every service registration, permission, and servicing component from clean sources. After completion, wuauserv works as designed. Before starting, update Lenovo drivers and BIOS via Lenovo support so the fresh system meets current firmware.

Closing

A Windows Update service that will not run is a symptom, not the disease — the disease is a disabled startup type, a broken dependency, an interfering tool, or damaged servicing components. Work the chain from the service outward: correct the startup type, fix dependencies, remove the interfering tool, reset the cache, repair the stack. The service wants to run; you just have to stop whatever is holding it down.

Frequently asked questions

What is the Windows Update service (wuauserv) actually responsible for?
Wuauserv is the core service behind Windows Update — it scans for updates, downloads them, and coordinates installation with the servicing stack. When it’s stopped or disabled, Settings shows errors like ‘something went wrong’ and no updates are found. It’s designed to run on a manual trigger startup type, launching whenever Windows Update needs it.
Why does the service keep stopping after I start it?
Usually because a dependency is broken or something is actively stopping it. Check its dependencies (Background Intelligent Transfer Service and DCOM Server Process Launcher) in the service properties. Third-party ‘optimizer’ or ‘debloater’ tools are the most common culprits for repeatedly disabling it — check their settings if the service won’t stay running.
Is it safe to set the Windows Update service to Automatic?
Yes, though Manual (Trigger Start) is the Windows default and works fine. Setting it to Automatic just means it starts at boot rather than on demand — harmless. What you should never do is leave it Disabled, which blocks all updates including security patches. If a tool set it to Disabled, change it back to Manual at minimum.
Could Lenovo software be stopping the Update service?
Lenovo Vantage itself doesn’t stop wuauserv, but aggressive third-party utilities sometimes bundled or installed alongside can. More commonly on Lenovo laptops, the issue is corrupted servicing components or permission problems rather than Lenovo software. Check Vantage’s settings only if the service stops immediately after you start it while Vantage is running tasks.