The 0x80070005 windows update error is one of the most stubborn problems you can hit on Windows 10 or Windows 11. It usually shows up as “Access Denied” when Windows Update tries to download or install an update, leaving your system stuck without the latest security patches. The good news is that this error is almost always fixable without reinstalling Windows. This guide walks you through 8 proven fixes, starting with the easiest and moving to the deeper repairs.
If you run into other update failures along the way, you may also want to check our guide on the 0x80070422 Windows Update error, which covers a related service-startup problem.
What Causes the 0x80070005 Error?
The 0x80070005 code translates to “Access Denied.” In the context of Windows Update, it means the update process tried to read or write a file, folder, or registry location and was blocked by the system’s permission settings. This can happen after a failed update attempt corrupted ownership on the SoftwareDistribution folder, after third-party antivirus software locked down system folders, or after a malware infection changed file permissions.
Another common cause is running with a standard user account instead of an administrator account. Windows Update needs elevated privileges to replace system files, and if your account lacks them — or if the admin token is being filtered by a broken security policy — the update engine fails with access denied. Corrupted system files reported by the CBS (Component-Based Servicing) store can trigger the same code, since Windows refuses to overwrite files it cannot verify.
How to Fix the 0x80070005 Error
Fix 1: Run the Windows Update Troubleshooter
The built-in troubleshooter automatically detects and repairs common update problems, including permission glitches.
- Open Settings and go to System > Troubleshoot > Other troubleshooters (Windows 11) or Update & Security > Troubleshoot > Additional troubleshooters (Windows 10).
- Find Windows Update in the list and click Run.
- Follow the on-screen prompts and let it apply any recommended fixes.
- Restart your PC and try running Windows Update again from Settings > Windows Update > Check for updates.
Fix 2: Make Sure You Are Using an Administrator Account
Updates cannot install properly from a standard account.
- Open Settings > Accounts > Your info and check whether it says Administrator under your name.
- If it says Standard user, sign in with an administrator account, or ask your PC’s administrator to change your account type under Settings > Accounts > Family & other users.
- Right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin), and confirm the UAC prompt — if the prompt appears, your account has admin rights.
Fix 3: Reset the Windows Update Components
Clearing the update cache fixes permission problems inside the SoftwareDistribution and Catroot2 folders.
- Open an elevated Command Prompt: right-click Start and choose Terminal (Admin).
- Stop the update services one by one:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver - Rename the cache folders so Windows rebuilds them cleanly:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old - Restart the services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver - Restart your computer and check for updates again.
Fix 4: Run SFC and DISM Scans
These tools repair corrupted system files and the Windows component store.
- Open an elevated Terminal or Command Prompt.
- Run the System File Checker: sfc /scannow
- Wait for the scan to finish (it can take 15–30 minutes), then run the DISM repair commands in order:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth - Restart your PC when DISM completes, then try the update again.
Fix 5: Fix Permissions on the SoftwareDistribution Folder
If the update folder itself has broken ownership, reset it directly.
- Open File Explorer and navigate to C:\Windows.
- Right-click the SoftwareDistribution folder and choose Properties.
- Go to the Security tab, click Advanced, and check the owner at the top.
- If the owner is unknown or wrong, click Change, type SYSTEM, click Check Names, then OK.
- Tick Replace owner on subcontainers and objects, click Apply, then OK.
- Restart and retry the update.
Fix 6: Temporarily Disable Third-Party Antivirus
Some antivirus suites block Windows Update from writing to protected folders.
- Open your antivirus program and look for a temporary disable or pause-protection option (usually a right-click on its taskbar icon).
- Disable real-time protection for 15–30 minutes — long enough to run the update.
- Go to Settings > Windows Update and click Check for updates.
- Re-enable your antivirus immediately after the update finishes or fails, whichever comes first.
Fix 7: Install the Update Manually from the Microsoft Update Catalog
Bypassing the automatic update engine often works when the automatic path is blocked.
- Note the KB number of the failing update from Settings > Windows Update > Update history.
- Visit the Microsoft Update Catalog at catalog.update.microsoft.com and search for the KB number.
- Download the version matching your system (x64 for most modern PCs, ARM64 for Snapdragon devices).
- Double-click the downloaded .msu file and follow the installer prompts.
- Restart if asked, then verify the update appears in your update history.
Fix 8: Perform a Clean Boot and Retry
A clean boot starts Windows with only essential services, ruling out software conflicts.
- Press Win + R, type msconfig, and press Enter.
- On the Services tab, tick Hide all Microsoft services, then click Disable all.
- Switch to the Startup tab and click Open Task Manager; disable every startup item.
- Click OK and restart your PC.
- Try Windows Update again. If it works, re-enable services in small groups to find the culprit.
How to Prevent This Error
- Keep your user account as an administrator on personal PCs so updates never hit permission walls.
- Run a full antivirus scan monthly — malware is a frequent cause of mangled file permissions.
- Avoid “debloater” scripts and aggressive permission-tweaking tools that strip SYSTEM ownership from Windows folders.
- Keep at least 15–20 GB free on your system drive so updates can stage files without errors.
- Do not interrupt updates mid-install; sudden shutdowns corrupt the update cache.
- Run sfc /scannow every few months as preventive maintenance.
FAQs
What does error 0x80070005 mean?
It means “Access Denied.” Windows Update tried to access a file, folder, or registry key it did not have permission for. The underlying cause is usually broken permissions, a corrupted update cache, or interference from security software.
Can 0x80070005 be caused by a virus?
Yes. Some malware deliberately changes file and registry permissions to block security updates from installing. If the fixes above do not work, run a full scan with Windows Security or a trusted second-opinion scanner before going further.
Will resetting Windows fix 0x80070005?
A reset will almost certainly fix it, but treat it as a last resort. The 8 fixes in this guide resolve the error in the vast majority of cases without touching your files or apps. Only consider Settings > System > Recovery > Reset this PC if every method above fails.
Does 0x80070005 affect Windows 10 and 11 the same way?
Yes. The code and the standard fixes are identical on both versions. Only the Settings menu paths differ slightly, and both are covered in the steps above.
Why does the error return after I fixed it once?
Recurring 0x80070005 usually points to an ongoing cause: a permission-stripping utility, persistent malware, or a failing drive corrupting files again. Run a disk check with chkdsk C: /f and investigate what changed on the system between fixes.
Conclusion
The 0x80070005 Windows Update error looks intimidating, but it is really just Windows telling you something blocked its access. Work through the fixes in order — troubleshooter, admin check, update-component reset, SFC/DISM, permission repair — and you will have updates flowing again in most cases. If you hit a different update code during the process, our related guides below cover the most common ones.
