Click Check for updates on your HP laptop and instead of a scan you get an error: the Windows Update service is not running. Open services.msc and there it is — wuauserv, stopped, and every attempt to start it either fails silently or throws an error. The update pipeline is not misbehaving; its engine will not turn over.

This is a service-layer problem, and it has a service-layer fix order. You will verify the service and its dependencies, repair its registration, clear the corruption that usually broke it, and check for the policies and third-party tools that commonly disable it on HP machines. Work the list in order — most cases resolve by Fix 4.

Services do not run in a vacuum. Windows Update (wuauserv) executes inside a shared svchost process alongside BITS, and it depends on Remote Procedure Call and DCOM infrastructure being healthy. That is why sfc /scannow matters for a service problem: the service binary itself is rarely damaged, but the libraries and registrations around it are. When you see wuauserv fail with Error 1053 (timeout) versus Error 2 (file not found), you are looking at two different diseases — timeouts suggest dependency or corruption trouble, missing-file errors suggest registration damage.

Why this happens

  • Corrupted service registration. The wuauserv registration in the service control manager is damaged, so start commands fail.
  • Broken dependencies. wuauserv depends on RPC and DCOM components; if those are damaged, the service cannot start.
  • Third-party antivirus disabled it. Some security suites stop the update service as part of their own update management.
  • HP or third-party optimizer tools turned it off. Debloat and optimizer utilities love disabling wuauserv to ‘stop unwanted updates.’
  • Group policy set it to disabled. On managed or formerly managed machines, policy can force the service off.
  • Corrupted update cache crashing the service. A damaged SoftwareDistribution store can crash wuauserv during startup.
  • System file corruption. Missing or damaged system files break the service binary or its libraries.

How to fix it

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

Fix 1: Start the service and check its dependencies

Confirm the exact failure mode before repairing.

  1. Open services.msc, find Windows Update, and try Start.
  2. Note any error message or code — ‘Error 1053’ and ‘Error 2’ point at different causes.
  3. Open the Dependencies tab and confirm Remote Procedure Call (RPC) is running.
  4. Also verify Background Intelligent Transfer Service and Cryptographic Services can start.

Fix 2: Re-register the update DLLs

Rebuilds the service’s COM registration, fixing the most common start failures.

  1. Open an elevated Command Prompt.
  2. Run regsvr32 wuapi.dll, regsvr32 wuaueng.dll, regsvr32 wups.dll, and regsvr32 wuwebv.dll, confirming each.
  3. Also run regsvr32 atl.dll and regsvr32 msxml3.dll.
  4. Try starting the Windows Update service again.

Fix 3: Reset the service configuration

Repairs a damaged service definition directly.

  1. In an elevated Command Prompt, run sc config wuauserv start= demand.
  2. Run sc config bits start= demand and sc config cryptsvc start= auto.
  3. Try net start wuauserv.
  4. If it starts now, the service definition was the problem — proceed to Fix 4 to clear whatever damaged it.

Fix 4: Clear the update cache

A corrupted cache is the classic reason the service dies on startup.

  1. Stop wuauserv, cryptSvc, bits, and msiserver (stop whichever are running).
  2. Rename C:\Windows\SoftwareDistribution to C:\Windows\SoftwareDistribution.old.
  3. Start the services again with net start.
  4. Open Settings > Windows Update and check for updates. For the download-side variant of update trouble, see update stuck downloading on Dell .

Fix 5: Check for policy blocks

On machines where something keeps forcing the service off.

  1. Run gpresult /h C:\gpreport.html and inspect Windows Update policies.
  2. Check HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU for NoAutoUpdate or service-related values.
  3. Remove optimizer or debloat tools that manage services — they are a top cause on HP consumer laptops.
  4. If the machine is organization-managed, the admin’s policy wins; do not fight it locally.

Fix 6: Run DISM and SFC

Repairs the system files the service depends on.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth elevated.
  2. Follow with sfc /scannow and restart.
  3. Try starting the service once more.
  4. Service binaries live in the protected store, so this repair covers damage the earlier fixes cannot. Related service-layer reading: update troubleshooter not working .

Fix 7: In-place upgrade repair

Rebuilds the entire service infrastructure when nothing else restores wuauserv.

  1. Download the Media Creation Tool from Microsoft’s official Windows 11 download site.
  2. Run setup.exe, keep files and apps, and complete the repair.
  3. Verify wuauserv starts and Windows Update scans normally.
  4. This is the definitive fix for service corruption — a fresh, correctly registered service stack. For HP-specific driver concerns afterward, HP support has your model’s driver set.

Fix 8: Scan for malware that disables updates

Some malware kills wuauserv deliberately to block security patches.

  1. Run a Microsoft Defender Offline scan from Windows Security > Virus & threat protection.
  2. Check Task Scheduler for unrecognized tasks that stop services on boot.
  3. Review services.msc for other disabled security services — a pattern suggests infection, not accident.
  4. If malware is found and removed, re-run the service repairs above; infections often damage what they disable.

Closing

A Windows Update service that will not run is a registration, dependency, or corruption problem — not a reason to reinstall Windows from scratch. Re-register the components, reset the service definition, clear the cache, and evict whatever third-party tool keeps disabling it. Once wuauserv starts cleanly and stays running, the update pipeline it powers comes back to life with it. After the service is healthy again, leave its startup type at Manual — that is the Windows default, and forcing Automatic papers over problems instead of fixing them. If a third-party optimizer was the culprit, replace it rather than re-tuning it; utilities that disable security infrastructure to win benchmarks are not optimizing anything. A service that starts on demand and stays running is the quiet foundation every other repair assumes.

Frequently asked questions

What does 'Windows Update service not running' mean?
It means the wuauserv service — the engine behind Settings > Windows Update — is stopped, disabled, or crashing on start. Without it, checking for updates fails immediately, usually with an error telling you the service is not running. The service is named wuauserv in services.msc, where you can inspect its status directly.
Why would the update service stop on an HP laptop?
Common causes: corrupted service registration after a failed update, third-party antivirus disabling it, aggressive HP or third-party ‘optimizer’ utilities turning it off, group policy on managed machines, or system file corruption breaking its dependencies. HP consumer laptops are frequent targets of third-party optimizer tools, which makes that cause worth checking early.
Can I just set the service to Automatic?
You can try, but if the underlying cause is corruption or a policy, it will stop again or refuse to start. Setting it to Manual (the Windows default) and fixing the root cause is more reliable than forcing Automatic on a broken service.
Is it safe to delete the SoftwareDistribution folder for this?
Yes — with the services stopped first. Deleting or renaming SoftwareDistribution only removes cached update data, which Windows rebuilds. It is one of the safest repairs in the Windows Update toolkit and often unsticks the service. Renaming instead of deleting keeps a fallback copy, which costs nothing and occasionally saves a diagnosis.