Error 0x80070005Access denied

What it means

0x80070005 is Windows telling you, in its standard error format, that a process was denied access. The prefix 0x8007 marks a Win32 (system) error, and the last part, 0005, is decimal 5, the constant ERROR_ACCESS_DENIED. Whatever the operation, something it needed to read, write or modify was refused by the permission system or by a program guarding those resources.

Because "access denied" is generic, the same code appears across Windows Update, the Microsoft Store, System Restore, backup, activation and scripting. The context tells you what was being accessed; the cause is nearly always permissions, ownership, or a security product intervening.

Fixes, safest first

1. Run the built-in troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update (or the relevant one). It resolves the common permission and service problems automatically.

2. Confirm you are an administrator. Settings → Accounts shows your account type. Update, Store and restore operations need administrative rights; a standard account can hit 0x80070005.

3. Temporarily pause third-party antivirus. Security products sometimes lock the very files an update or restore needs. Disable real-time protection briefly, retry, then re-enable it. Microsoft Defender rarely causes this.

4. Reset Windows Update components (for update-specific 0x80070005). In an elevated prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Then check for updates again.

5. Repair system files. Corruption can present as access errors:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

See DISM and sfc.

6. Try Safe Mode for System Restore or backup failures, so third-party software is not loaded to interfere.

If it involves file or folder access

When 0x80070005 accompanies a specific file or registry path, it is a direct permissions problem. Take ownership and grant your account access, carefully; see Windows file permissions. Do not grant Everyone Full Control as a shortcut.