Windows Update Service Stuck in Stopping State – Fix

1. The Real Fix: Kill the Hung Background Intelligent Transfer Service (BITS)

Had a client last month whose entire print queue died because of this exact problem. Windows Update got stuck in 'stopping' after a failed update. The real culprit? BITS (Background Intelligent Transfer Service) sometimes doesn't release its handle. Here's the fix that works 9 times out of 10.

1. Open Command Prompt as Administrator. Search for 'cmd', right-click, 'Run as administrator'.
2. Type net stop wuauserv and press Enter. If it says 'service is stopping' and hangs, move on.
3. Type net stop bits and press Enter. Usually BITS is the one holding everything up.
4. If BITS won't stop either, type taskkill /f /im svchost.exe — but be careful. This kills all background tasks. Only do this if you're stuck for more than 5 minutes.
5. After both services stop, restart them: net start wuauserv and net start bits.

This fixes the stuck service about 70% of the time. If it doesn't, read on.

2. The Second Most Common Cause: Corrupted Windows Update Files

Sometimes the update files themselves get corrupted. This happens a lot after a power outage or forced shutdown during updates. Windows Update then hangs forever because it can't process the broken files.

What to do:

1. Open Command Prompt as Administrator.
2. Run net stop wuauserv and net stop bits first — even if they're stuck, try.
3. Rename the SoftwareDistribution folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
4. Rename the Catroot2 folder: ren C:\Windows\System32\catroot2 catroot2.old
5. Restart the services: net start wuauserv and net start bits
6. Open Windows Update and check for updates again. It'll rebuild the folders fresh.

I've seen this fix a system that had been stuck for 3 days. The client thought they needed to reinstall Windows. Nope. Just rename the folders.

3. The Third Cause: Third-Party Security Software Interference

Here's a weird one. Some antivirus programs — looking at you, McAfee and older Norton versions — hold onto Windows Update processes to scan them. This causes the service to never fully release. Had a client whose small business server had this for weeks. Disabled the antivirus and the update finished in 10 minutes.

How to check:

1. Temporarily disable your antivirus (not just turn off real-time scanning, fully disable it).
2. Try restarting the Windows Update service again.
3. If it works, add an exception in your antivirus for C:\Windows\SoftwareDistribution and C:\Windows\System32\wuaueng.dll.

Don't keep your antivirus off for long. Just long enough to see if it's the cause. I've seen cases where even Windows Defender conflicts after a bad update. You can also check Windows Defender's exclusion list just in case.

Quick-Reference Fix Table

One last thing: if you're still stuck after all this, check the Windows Update log at C:\Windows\WindowsUpdate.log. Look for error codes like 0x80070643 or 0x80240034. That usually means a missing system file. Run sfc /scannow from Command Prompt to fix those. But 90% of the time, the BITS fix above is all you need.