Windows 11 update problems: common errors and how to fix them

Windows 11 update problems are more common than they should be for a modern operating system. Whether you're seeing a cryptic error code, an update that stalls at 0%, or a machine that keeps restarting without finishing the job, most failures point to a handful of root causes. This guide covers the most frequent Windows 11 update errors and the specific steps to fix each one.

Why Windows 11 updates fail in the first place

Updates fail for a few predictable reasons. Corrupted system files are the most common culprit, followed by a damaged Windows Update cache, insufficient disk space, and conflicts with third-party antivirus software. Driver incompatibilities can also block feature updates from completing. Knowing which cause applies to your situation saves a lot of time.

Before trying any fix, check that your machine meets the hardware requirements for the update in question. Some Windows 11 feature updates add new minimum specs. A quick check in Settings > Windows Update > Update history will show exactly which update failed and what error code it produced.

Error 0x80070005: access denied

Error 0x80070005 means Windows Update doesn't have the permissions it needs to install files. This happens most often when a third-party security tool or a misconfigured user account is blocking write access to protected folders.

Fix it by running Windows Update as an administrator. Open Settings, go to Windows Update, and restart the update from an administrator account. If that doesn't work, temporarily disable your antivirus, run the update, then re-enable protection immediately after. If a business endpoint security tool is managing your machine, the permissions issue may need an IT technician to resolve at the policy level.

Error 0x80070422: Windows Update service not running

This error means the Windows Update service has stopped or is set to manual instead of automatic. It's a simple fix.

• Press Win + R, type services.msc, and press Enter.
• Scroll to Windows Update in the list.
• Right-click it, select Properties, set the Startup type to Automatic, then click Start.
• Also check that Background Intelligent Transfer Service (BITS) is running the same way.

Restart your PC and try the update again.

Error 0x8007000D or 0x80073712: corrupted update files

These two codes both point to corrupted update packages or damaged Windows component files. The System File Checker and the Deployment Image Servicing and Management tool fix these without requiring a reinstall.

Open Command Prompt as administrator and run this command first:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for it to complete, which can take 10 to 20 minutes depending on your connection speed, since it downloads replacement files from Microsoft's servers. Then run:

sfc /scannow

Restart after both complete. In most cases, the update will then install cleanly.

Update stuck at 0% or freezing mid-install

An update that refuses to move past 0% is almost always a corrupted Windows Update cache. The cache stores partially downloaded update files, and if one becomes corrupt, it blocks all subsequent downloads.

To clear the cache:

1. Open Command Prompt as administrator.
2. Run net stop wuauserv to stop the Windows Update service.
3. Run net stop bits to stop the Background Intelligent Transfer Service.
4. Navigate to C:\Windows\SoftwareDistribution and delete everything inside the Download folder. Don't delete the folder itself.
5. Run net start wuauserv and net start bits to restart both services.
6. Restart your PC and check for updates again.

Windows will re-download the update files fresh. The initial scan may take a few minutes longer than usual.

Not enough disk space for updates

Feature updates (the larger ones Microsoft releases roughly twice a year) need around 20 GB of free space to download, unpack, and install. If your drive is nearly full, the update will fail silently or display a low-disk error.

Run Disk Cleanup first: search for it in the Start menu, select your system drive, and check the "Windows Update Cleanup" and "Temporary files" boxes. This often frees several gigabytes immediately. If your machine is still running low overall, a computer running out of storage can block updates and slow down the whole system, and fixing the underlying space problem is worth doing properly.

Windows 11 feature update failing after restart

Some feature updates fail not during download but during the restart phase, rolling back to the previous version with no clear explanation. The two most common causes are an incompatible driver and a third-party application that the new Windows version doesn't yet support.

Check the Windows Setup log at C:\Windows\Panther\setuperr.log. It lists the specific file or driver that caused the rollback. If a driver is named, go to the manufacturer's website and download the latest version before retrying the update. Graphics drivers (NVIDIA, AMD, Intel) are the most frequent offenders in feature update failures.

If you're still seeing the same rollback after updating drivers, use the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and run it. It patches many common service and registry misconfigurations automatically.

Update error after a third-party antivirus install

Some antivirus products, particularly older versions or those without active Windows 11 support, intercept Windows Update's download process and flag update packages as suspicious. The update fails without producing a clear error code.

Temporarily disable real-time protection, attempt the update, then re-enable it. If the update completes, check whether a newer version of your antivirus is available. Most major vendors publish compatibility notes for each major Windows release.

Microsoft publishes its own Windows Update support documentation covering known conflicts and workarounds, which is worth checking if a specific antivirus vendor is involved.

When Windows Update says your PC isn't eligible

Some Windows 11 feature updates require TPM 2.0, Secure Boot, and a compatible CPU. If your machine passes the original Windows 11 upgrade check but fails a newer feature update, Microsoft may have added a new hardware requirement mid-cycle.

Run the PC Health Check app to confirm whether your hardware meets current requirements. If your CPU or TPM configuration is at fault, the update simply won't install through Windows Update, and the fix is either a hardware upgrade or staying on the current build until your machine reaches end-of-life.

When to get help

Most Windows 11 update problems respond to the fixes above. But if you've cleared the cache, repaired system files, updated drivers, and freed up disk space and the update still fails, the issue may be deeper, such as a corrupted Windows registry or a failing storage drive. These situations benefit from a professional pair of eyes.

A remote computer troubleshooting session can get a technician into your system quickly without you having to take the machine anywhere. Most update failures that resist self-service fixes are resolved in a single session. It's faster than reinstalling Windows and much less disruptive than a hardware swap.

If your machine is showing other signs of trouble alongside update failures, the problem might not be the update at all. Check whether anything else changed recently: a new application, a driver update, or a sudden spike in disk or CPU usage. Updates are often the last thing to fail, not the first.