Windows Update Not Working? Here's How to Fix It

Evelyn Carter
Jul 3
6 min read

Windows update not working is usually caused by a corrupted update cache, a stuck Windows Update service, insufficient disk space, or a connectivity issue. Running the built-in Windows Update troubleshooter resolves most cases; if it doesn't, clearing the update cache and restarting the Windows Update service usually does.

Windows Update failing, freezing, or refusing to run at all is one of the most common frustrations on any Windows machine — and it's rarely one single cause. Here's a complete, ordered troubleshooting path: start with the basics, work through the most common error codes, and finish with the advanced fixes IT pros reach for when everything else fails.

Why Windows Update Not Working

Windows Update relies on a background service, a local file cache, and a stable connection to Microsoft's servers — a failure in any one of those three areas can stop updates cold.

As Wikipedia's overview of Windows Update explains, the service has evolved considerably since its early days as a browser-based tool, and now runs through the Windows Update Agent as a core integrated component of the operating system — which means when something goes wrong with it, it tends to affect the whole update pipeline rather than just one piece.

It's also worth knowing you're not imagining it if updates have felt shakier than usual recently. As Forbes reported on Microsoft's ongoing update reliability issues in early 2026, a security update caused some PCs to fail to shut down or hibernate properly, and the company's own emergency out-of-band patch didn't fully resolve it for every affected device — a reminder that update problems aren't always something wrong on your end.

Step-by-Step: General Troubleshooting

Run the Windows Update troubleshooter. Go to Start > Settings > System > Troubleshoot > Other troubleshooters, locate Windows Update, and select Run. This resolves the majority of common issues automatically.
Check your internet connection. Go to Start > Settings > Network & Internet > Wi-Fi and confirm you're actually connected — a dropped or unstable connection is a common, easy-to-miss cause.
Confirm you have administrator access. Some updates require admin permissions to install; if your account doesn't have them, you'll need an administrator to run the update.
Disconnect unnecessary external hardware. USB drives, docks, and other peripherals can occasionally interfere with the update process.
Clear the Windows Update cache. Stop the Windows Update service via services.msc, delete the contents of C:\Windows\SoftwareDistribution, then restart the service. Corrupted cache files are one of the most common root causes of stuck or failing updates.
Verify date and time settings. Incorrect system time can cause updates to fail silently — enable "Set time automatically" under Settings > Time & language.
Update third-party drivers. Outdated hardware drivers, especially for network or graphics adapters, can block updates from completing.
Free up disk space. A 64-bit OS upgrade needs at least 20 GB free; a 32-bit upgrade needs 16 GB. Low storage is a frequent, easily overlooked cause.
Check for updates again. After working through the steps above, recheck for updates — there may be more available than what was initially shown.
Restart to apply installed updates. Many updates only complete after a restart; if updates seem "stuck," a restart is sometimes all that's needed.

Common Error Codes and What They Mean

Error Code	Likely Cause
0x8007000d	Corrupted update cache or update files
0x800705b4	Update took too long or was interrupted
0x80240034	Stuck update process due to a connection issue
0x800f0922	Insufficient disk space or a .NET Framework conflict
0x80070057 / 0x80080005	Corrupted files or incorrect system configuration
0xC1900101	An incompatible driver is blocking the update
0x80248014	Windows Update service or database isn't running
0x80070005	Access denied — insufficient permissions
0x80070002	Update failed to install

For most of these, the fix path is the same: run the troubleshooter first, then clear the update cache if the troubleshooter doesn't resolve it, and check disk space and driver compatibility for the codes tied to those specific causes.

When "Services" or Windows Update Is Greyed Out

One especially frustrating variant of this problem is when the Windows Update service itself appears greyed out or locked in the Services console, making it impossible to start, stop, or restart. This usually points to one of a few underlying causes rather than the update process itself:

Group Policy restrictions — either from an organization's IT policy or, on personal machines, a misconfigured local Group Policy setting that's disabling the service.
Registry permission issues — the Windows Update service's registry key can end up with incorrect permissions, particularly after malware removal or an incomplete update, which prevents Windows from being able to modify the service's state at all.
A conflicting third-party tool — some "privacy" or "debloat" utilities disable Windows Update at the service level and don't always fully re-enable it if uninstalled.

If the toggle itself is unavailable, checking Local Group Policy Editor (gpedit.msc) for a Windows Update-related restriction, or reviewing the permissions on the relevant registry key, is usually the next step rather than repeating the standard troubleshooting steps above.

Advanced Troubleshooting

If general troubleshooting doesn't resolve the issue, these steps require comfort with the command line and administrator access:

Rename the software distribution folders. Via an elevated Command Prompt, stop the bits and wuauserv services, rename the SoftwareDistribution and catroot2 folders, then restart both services. This forces Windows to rebuild its update cache from scratch.
Run System File Checker. sfc /scannow in an elevated Command Prompt checks for and repairs corrupted system files that could be interfering with updates.
Repair the Windows image. DISM.exe /Online /Cleanup-image /Restorehealth repairs the underlying Windows image itself, which SFC alone sometimes can't fix.
Temporarily remove third-party security software. Some antivirus or firewall tools interfere with the update process — disable or temporarily uninstall them, run the update, then reinstall.
Repair hard drive errors. chkdsk /f C: from an elevated Command Prompt can catch and repair disk errors that block updates from completing.
Perform a clean boot. Starting Windows with a minimal set of drivers and startup programs eliminates software conflicts that can interfere with the update process.

Common Mistakes

Skipping the troubleshooter and going straight to advanced fixes. The built-in troubleshooter resolves most issues in a couple of minutes — it's worth running first even if you expect a deeper problem.
Not checking disk space before troubleshooting further. A surprising number of "stuck" updates are simply out of room to complete.
Ignoring the exact error code. Each code points to a fairly specific cause — matching the fix to the code saves a lot of trial and error.
Forgetting to restart after clearing the update cache. The service needs to be properly restarted, not just the cache cleared, for the fix to take effect.

Conclusion

Windows Update not working almost always traces back to one of three things: the update service itself, a corrupted local cache, or a connectivity/permissions issue and working through the troubleshooting steps in order, starting with the built-in troubleshooter, resolves the overwhelming majority of cases without needing to touch the Registry or Command Prompt at all.

FAQ

What's the fastest way to fix Windows Update not working?

Run the built-in Windows Update troubleshooter first (Settings > System > Troubleshoot > Other troubleshooters) — it resolves the majority of common issues automatically.

Why is my Windows Update stuck at a specific percentage?

This is usually tied to connection speed, update size, or a corrupted cache. Try checking for updates again, or run the troubleshooter if it stays stuck.

Why is the Windows Update service greyed out in Services?

Most commonly a Group Policy restriction, a registry permissions issue, or a third-party tool that disabled the service and didn't fully re-enable it.

Do I need administrator access to fix Windows Update?

Yes, for most fixes — especially anything involving Command Prompt, the Services console, or the Registry.

Should I back up my files before troubleshooting?

Yes, particularly before advanced steps like renaming system folders or running disk repairs — back up personal files first as a precaution.

Is it normal for Windows updates to cause new problems?

It happens more often than most users realize — even Microsoft has publicly acknowledged update-introduced bugs, including one affecting shutdown and hibernation in early 2026 that required multiple emergency patches to address.