The Windows Update troubleshooter is the most underused repair tool on every laptop. It is free, built into Windows, safe, and it resolves a surprising share of update failures — stuck downloads, services that will not start, and corrupted task registrations — in about two minutes with no technical skill required.

Most people either do not know it exists or run it once, see no dramatic message, and assume it did nothing. Both are mistakes. Used correctly — with a restart afterward and a retest — it is the right first move for nearly every update problem, and it tells you something useful even when it cannot fix the issue itself.

This guide shows the correct way to run it on a laptop, explains what its repairs mean, and lays out exactly what to do when the troubleshooter is not enough. If the troubleshooter itself refuses to run, see our companion article on a non-working update troubleshooter .

Why this happens

  • Update services stopped or misconfigured: wuauserv, bits, and cryptSvc sometimes end up disabled or stuck, and the troubleshooter restores their correct states.

  • Corrupt update task registrations: the scheduled tasks that trigger update scans can break, leaving updates that never start on their own.

  • Damaged registry entries: tweakers, optimizers, and failed updates can mangle the registry values the update engine depends on.

  • Stale network and proxy settings: leftover proxy configurations or broken WinHTTP settings block the update engine from reaching Microsoft’s servers.

  • Pending operations blocking new scans: a half-finished previous operation can jam the queue until the troubleshooter clears it.

  • Missing or unregistered DLLs: the update engine’s component libraries occasionally need re-registering after corruption or bad uninstalls.

  • Laptop-specific power interference: aggressive battery-saver or OEM power tools can suspend the background tasks updates rely on.

How to fix it

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

Fix 1: Run the troubleshooter the right way

There is a correct procedure and it matters: run it with the laptop plugged in, let it finish fully, apply everything, restart, and retest. Skipping the restart is the most common reason people think it failed.

  1. Connect the charger — some repairs are deferred on battery power.
  2. Open Settings (Win + I), go to System, Troubleshoot, Other troubleshooters.
  3. Click Run next to Windows Update and do not touch anything until it finishes.
  4. Apply every fix it offers, even ones that look unrelated.
  5. Restart the laptop, then go to Windows Update and click Check for updates.

Fix 2: Read the troubleshooter’s report properly

The detailed report is diagnostic gold. It names exactly which checks failed and which repairs were applied, which tells you — or a helper — where the real problem lives when updates still fail afterward.

  1. After the run, click View detailed information on the results screen.
  2. Note each issue found and whether it says Fixed or Not fixed.
  3. Screenshot or write down any issue marked Not fixed — that is your next target.
  4. If it mentions service registration or database problems, continue to Fix 3 below.
  5. Keep the report handy if you end up asking for help on a forum.

Fix 3: Follow up with a manual service reset

The troubleshooter repairs services but does not fully rebuild the download cache. When the scan reports fixes applied yet updates still fail, this manual reset finishes the job it started.

  1. Open Terminal (Admin) from the Start right-click menu.
  2. Run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old.
  4. Restart the services with the four matching net start commands.
  5. Restart the laptop and check for updates again.

Fix 4: Check for metered connection blocks

On laptops that move between networks, Windows may treat your Wi-Fi as metered and silently refuse to download updates. The troubleshooter does not always flag this, but it blocks everything downstream.

  1. Go to Settings, then Network and internet, then Wi-Fi, and open your connected network.
  2. Check whether Metered connection is turned on; turn it off for your home network.
  3. In Windows Update, Advanced options, confirm downloads are allowed over metered connections if you need them.
  4. Our detailed guide on metered connections blocking updates covers the edge cases.
  5. Retry the update check on an unmetered connection.

Fix 5: Repair system files behind the failure

When the troubleshooter keeps finding the same problems on every run, the underlying system files are damaged. SFC and DISM repair them so the troubleshooter’s fixes actually stick.

  1. Open Terminal (Admin) and run sfc /scannow to completion.
  2. Restart the laptop.
  3. In a fresh admin terminal, run DISM /Online /Cleanup-Image /RestoreHealth.
  4. Allow 15-30 minutes, restart again, and re-run the troubleshooter.
  5. A clean troubleshooter run now usually means updates will work.

Fix 6: Free disk space the updater needs

Laptops with small SSDs fail updates for the most boring reason of all: no room. The troubleshooter rarely calls this out clearly, so check it yourself before concluding the problem is complex.

  1. Open Settings, System, Storage, and check free space on C:.
  2. Run Disk Cleanup from Start and select Windows Update Cleanup plus Temporary files.
  3. Remove unused apps and move large media to external storage.
  4. Aim for 20 GB free for cumulative updates and 30 GB for feature updates.
  5. Run Check for updates once space is available.

Fix 7: Reset Windows Update via the command line

As a final escalation before manual installs, re-registering the update engine’s DLLs and resetting its policies clears the deep corruption that the graphical troubleshooter cannot reach.

  1. Open Terminal (Admin).
  2. Stop the four update services with net stop as in Fix 3.
  3. Re-register core DLLs, for example regsvr32 wuapi.dll, regsvr32 wuaueng.dll, regsvr32 wups.dll (approve each prompt).
  4. Delete the contents of C:\Windows\SoftwareDistribution\Download (not the folder itself).
  5. Restart the services, reboot, and test Windows Update. For deeper servicing failures, Microsoft’s support documentation covers advanced repair options.

Closing

The troubleshooter deserves its place as step one: it is fast, safe, and genuinely fixes the common cases. But its real value is diagnostic — what it finds and what it cannot fix points you at the right deeper repair. Work the escalation above in order and you will resolve the overwhelming majority of laptop update failures without ever reinstalling Windows.

Frequently asked questions

Where is the Windows Update troubleshooter in Windows 11?
Open Settings with Win + I, go to System, then Troubleshoot, then Other troubleshooters. The Windows Update entry has a Run button beside it. On Windows 10 the path is Settings, then Update and Security, then Troubleshoot, then Additional troubleshooters. On either version, run it with the laptop plugged in and restart afterward for the repairs to take effect.
What does the Windows Update troubleshooter actually fix?
It checks that the update services are running with correct settings, repairs common registry values, clears stuck update tasks, resets some network-related update settings, and re-registers key update DLLs. It handles the frequent, well-understood failure modes automatically.
Is it safe to let the troubleshooter apply all its fixes?
Yes. The troubleshooter only performs Microsoft-approved, non-destructive repairs: restarting services, fixing registry entries, and clearing caches. It never touches personal files, installed programs, or your settings beyond update-related values. You can approve every suggested fix without worrying about data loss.
How often should I run the update troubleshooter?
Only when updates are actually failing. Running it proactively does nothing useful, since there is nothing to repair. If you find yourself running it monthly, something deeper is wrong — work through the advanced fixes below instead of repeating the scan.