Fix Error 0x80070005 on Windows 11 (Access Denied)

Error 0x80070005 on Windows 11 is an “Access Denied” error that typically appears when Windows Update, Microsoft Store, or certain apps try to write to protected system folders or registry keys. This guide walks you through the most effective fixes, from simple permission checks to deeper system repairs, so you can restore normal functionality without reinstalling Windows.

What You’ll Need

An administrator account (you’ll need to confirm UAC prompts)
Internet connection (for some steps like Windows Update troubleshooter)
Backup of important files (recommended before modifying registry or taking ownership)

Step-by-Step

Run the Windows Update Troubleshooter

Go to Settings > System > Troubleshoot > Other troubleshooters. Click Run next to “Windows Update.” Follow the prompts. This automatically fixes common permission and corruption issues.
Check Folder Permissions

If the error occurs when installing an app, right-click the installation folder (e.g., C:\Program Files\AppName), select Properties > Security. Click Edit, select Users, and check Full control under Allow. Apply and retry.
Run SFC and DISM

Open Command Prompt as administrator (search “cmd”, right-click, “Run as administrator”). Type sfc /scannow and press Enter. After it finishes, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. Restart your PC.
Reset Windows Update Components

In the same admin Command Prompt, run these commands one by one:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

Then rename the SoftwareDistribution and CatRoot2 folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 Catroot2.old

Restart the services with net start wuauserv, net start cryptSvc, net start bits, net start msiserver. Reboot.
Use Registry Editor to Fix Permissions

If the error persists, press Win+R, type regedit, and navigate to the key mentioned in the error (often HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate). Right-click the key, select Permissions, and ensure Administrators have Full Control. Apply and restart.
Take Ownership of Problem Files

In File Explorer, right-click the file/folder, go to Properties > Security > Advanced. Next to “Owner,” click Change. Type Administrators, click Check Names, then OK. Check “Replace owner on subcontainers and objects” and apply. Then grant Full Control to Administrators.
Perform a Clean Boot

Press Win+R, type msconfig, go to Services tab, check “Hide all Microsoft services,” click Disable all. Then go to Startup tab and open Task Manager, disable all startup items. Reboot and try the update/install again. If it works, re-enable services one by one to find the culprit.
Use the Microsoft Store Apps Troubleshooter

If the error is from Store, go to Settings > System > Troubleshoot > Other troubleshooters, run “Windows Store Apps.” This resets app permissions.

Common Mistakes

Skipping the Troubleshooter: Many users jump straight to complex fixes, but the built-in troubleshooter often resolves the issue quickly.
Not running Command Prompt as administrator: SFC and DISM will fail if you don’t elevate. Always right-click and select “Run as administrator.”
Modifying the wrong registry key: Double-check the exact key path from the error message. Editing the wrong key can cause system instability.
Ignoring third-party antivirus: Security software can block system changes. Temporarily disable it (if safe) to test.

Tips

Create a system restore point before making registry changes or taking ownership of system folders.
Use the “Reset this PC” option (keep files) as a last resort—it reinstalls Windows without losing personal data.
Keep Windows 11 updated to the latest version; Microsoft often fixes permission bugs in cumulative updates.
If the error occurs during a Windows Update, try pausing updates for a week and then resuming—sometimes the update server is the issue.

Troubleshooting

If the steps above don’t resolve the error, try these additional checks:

Check disk for errors: Run chkdsk /f /r in admin Command Prompt (you’ll need to reboot). This repairs file system corruption that can cause access issues.
Create a new user account: Go to Settings > Accounts > Family & other users, add a new user with admin rights. Log into that account and try the operation. If it works, your original profile is corrupted—consider migrating.
Use System Restore: If the error started recently, restore to a point before it occurred. Search “Create a restore point,” click “System Restore,” and choose a restore point.
Check Event Viewer: Search “Event Viewer,” look under Windows Logs > System and Application for errors around the time of the failure. This can give more specific clues.

Frequently Asked Questions

1. What causes error 0x80070005?

It’s an “Access Denied” error, usually caused by insufficient permissions on system folders or registry keys, often after a Windows update or when a third-party app modifies security settings.

2. Can I fix this without admin rights?

No, most fixes require administrator privileges. If you’re on a work or school computer, contact your IT department.

3. Will resetting Windows Update components delete my updates?

No, it only resets the update cache. You’ll need to re-download updates, but your installed updates remain intact.

4. Is it safe to take ownership of system folders?

It’s generally safe if you only change permissions for the specific folder causing the error. Avoid taking ownership of entire C:\Windows, as it can weaken security.

5. How long does the DISM command take?

It can take 10-30 minutes depending on your system speed and internet connection. Don’t close the Command Prompt during the process.

6. What if the error appears when installing a specific app?

Try reinstalling the app as administrator (right-click installer, “Run as administrator”). Also, check if the app’s installation folder exists and is not read-only.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →