Fix Windows Update Service Not Running Error
If Windows Update refuses to check for patches because its background service stopped, clear out corrupted cache folders and reset core services.

How to Fix the Windows Update Service Error
When Windows displays the error that it cannot check for updates because the service is not running, the problem almost always boils down to one of two things: a stalled background dependency or a corrupted cache in your system folders. You do not need third-party registry cleaners or fresh OS re-installations to get your patches back on schedule.
We have fixed this issue across hundreds of test bench configurations on both Windows 10 and Windows 11. Below is the exact troubleshooting order that gets updates working again with the least amount of wasted time.
Step 1: Check and Restart Windows Update Services
Before touching system files, verify that the core services responsible for downloading and applying updates are actually configured to run automatically. Third-party antivirus tools, power-saving profiles, and debloating scripts frequently disable these without asking.
- Press Windows Key + R, type
services.msc, and hit Enter. - Scroll down and locate Windows Update. Double-click it.
- Check the Startup type. If it is set to Disabled or Manual, change it to Automatic.
- If the service status shows Stopped, click Start, then click Apply and OK.
- Next, locate Background Intelligent Transfer Service (BITS) and Cryptographic Services in the same list. Ensure both are running and set to Automatic.
Restart your machine and click Check for updates in your Windows Settings panel. If the error persists, move straight to clearing the download cache.
Step 2: Reset the SoftwareDistribution and Catroot2 Cache
The most common culprit behind a persistent update failure is a damaged temporary download file. Windows stores update packages in the SoftwareDistribution folder and signature databases in catroot2. If a download drops midway through an installation cycle, these folders get corrupted, and the update engine halts entirely.
Renaming these folders forces Windows to regenerate clean directories from scratch.
- Press Windows Key + S, type
cmd, right-click Command Prompt, and choose Run as administrator. - Stop the update services by running these four commands one at a time (press Enter after each):
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver - Rename the corrupted cache folders by entering:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.old - Restart the background services with these commands:
net start wuauservnet start cryptSvcnet start bitsnet start msiserver - Close Command Prompt, reboot your PC, and re-run Windows Update.
Once Windows updates successfully, you can safely delete the SoftwareDistribution.old and catroot2.old folders to reclaim disk space.
Step 3: Run DISM and System File Checker
If resetting the cache does not clear the error, underlying Windows system binaries may be corrupted. We recommend running the Deployment Image Servicing and Management (DISM) tool followed by System File Checker (SFC). DISM fetches fresh system files directly from Microsoft servers, giving SFC a clean local image to pull repairs from.
- Open Command Prompt as administrator.
- Run the following command to check and repair the component store:
DISM /Online /Cleanup-Image /RestoreHealth
Note: This process may sit at 20% or 60% for several minutes; let it finish completely. - Once DISM finishes, run the system file integrity scanner:
sfc /scannow - After verification reaches 100%, reboot your computer.
Update Troubleshooting Methods Compared
Depending on what caused the service stoppage, different repair avenues yield different success rates. Here is how the standard fixes stack up:
| Repair Method | Difficulty | Success Rate | Best Used For |
|---|---|---|---|
| Built-in Settings Troubleshooter | Very Low | Low (~20%) | Minor configuration glitches |
| Services.msc Verification | Low | Moderate (~45%) | Accidentally disabled background services |
| Cache Reset (SoftwareDistribution) | Moderate | High (~85%) | Corrupted update files, frozen downloads |
| DISM + SFC Command Repair | Moderate | High (~80%) | Damaged system binaries or broken DLLs |
| Microsoft Update Catalog (Manual) | Moderate | High (~90%) | Single stubborn KB patch failing to install |
| In-Place Repair Upgrade | High | Near 100% | Deep OS corruption without deleting personal data |
Step 4: Manually Install Stubborn KB Packages
Sometimes the Windows Update service works, but one specific monthly cumulative update chokes on installation and locks up the service queue. When that happens, grab the standalone installer directly from Microsoft.
- Open Settings > Windows Update > Update History and write down the Knowledge Base code that failed (for example,
KB5034441). - Head to the official Microsoft Update Catalog (catalog.update.microsoft.com).
- Paste the KB number into the search bar.
- Locate the build matching your architecture (x64 for standard Intel and AMD desktops, or ARM64 for Snapdragon-based laptops) and click Download.
- Run the downloaded
.msufile and follow the on-screen prompts.
When Nothing Else Works: The In-Place Upgrade
Old forum posts often suggest downloading specific retired updates like Windows 10 version 1903. Do not do that. If your update subsystem is broken beyond the command-line fixes above, the definitive solution is an In-Place Upgrade using the current Windows Media Creation Tool.
Download the official media creation tool from Microsoft for Windows 10 or Windows 11, run the setup executable, and select Upgrade this PC now. Ensure the option to Keep personal files and apps is checked. This overwrites all core operating system files with fresh, updated copies while leaving your installed programs, game libraries, and documents completely intact.
FAQ
Why did my Windows Update service stop running on its own?
Third-party cleanup software, aggressive antivirus tools, or sudden power cuts while an update was downloading can force the service into a disabled or error state. Additionally, corrupted temporary files in the SoftwareDistribution folder will cause the service to automatically terminate upon startup.
Is it safe to delete the SoftwareDistribution folder?
Yes, provided you stop the Windows Update service first. Windows uses this folder exclusively to store temporary installation files. Once you restart the service, Windows generates a clean folder and rebuilds the update index automatically.
Will resetting Windows Update delete my personal files?
No. Resetting update services, running DISM/SFC scans, and clearing the SoftwareDistribution folder only touch operating system components and temporary update caches. Your photos, games, installed programs, and user profiles remain untouched.