Fix Windows Update Error 0x80070005 (Access Denied)

Error 0x80070005 means Windows Update can't write to system files. Fix permissions with a quick registry tweak or reset the update components. No reinstall needed.

Yeah, this error is infuriating. You click Check for updates, wait forever, and then get smacked with 0x80070005 — access denied. But it's not a hardware failure or a corrupted OS. It's a permissions lockout on critical system files. Here's how I fix it.

The Fast Fix: Reclaim Registry Ownership

Windows Update needs write access to a specific registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate. If a previous cleanup tool or a buggy driver messed with its ACL, updates fail instantly. Let's take ownership and restore full control.

Press Win + R, type regedit, and hit Enter. Click Yes when User Account Control pops up.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
Right-click the WindowsUpdate key and select Permissions.
In the dialog, click Advanced.
At the top, next to Owner, click Change.
Type Administrators in the box, click Check Names, then OK.
Check Replace owner on subcontainers and objects and hit Apply.
Back in the main Permissions window, select the Administrators group and tick Full Control under Allow.
Click OK and close Registry Editor.
Reboot and run Windows Update again.

This works because the WindowsUpdate registry key stores the update session state. When its ACL is broken, Windows Update can't write its own status — so it throws access denied. Restoring ownership to Administrators gives the update service the green light.

Why the Standard Fixes Fail

You'll see advice to run the Windows Update troubleshooter or the DISM tool. I've tried both. They're great for corrupted files, but they don't touch registry permissions. That's why you get stuck in a loop — the troubleshooter says it fixed things, but the error reappears on the next update check. The registry ownership fix is the real solution.

Less Common Variations

1. Error Appears After a Feature Update

If you see 0x80070005 right after a big update (like 22H2 or 23H2), it's often the SoftwareDistribution folder that got locked. Open Command Prompt as Admin and run:

net stop wuauserv
net stop bits
rename C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

This renames the cache folder, forcing Windows to create a fresh one. I've seen this work when the registry fix didn't, especially on older Windows 10 machines.

2. Error Only When Installing a Specific Driver

A single driver can trigger this if its installer writes to protected paths. Try downloading the driver from the manufacturer's site and installing it manually. If that works, the issue is Windows Update's driver delivery mechanism, not your system permissions.

3. Error with Error 0x80070005 in Event Viewer

Check Event Viewer under Windows Logs > System. If you see a source named Microsoft-Windows-WindowsUpdateClient with this error, follow the registry fix. If you see Kerberos or Ntfs errors, that points to a corrupted user profile. Create a new administrator account and try updates from there.

When All Else Fails: System Restore

If the registry fix and the SoftwareDistribution rename don't work, and you have a restore point from before the error started, use it. Go to Control Panel > Recovery > Open System Restore. Pick a point dated before your last Windows Update attempt. This is a sledgehammer, but it's saved my butt twice.

Prevention: Stop It from Coming Back

This error doesn't usually recur after the registry fix, but you can lower the odds. First, uninstall any third-party registry cleaners — they're the number one cause of ACL damage. Second, run Windows Update monthly, not sporadically; a regular cadence keeps the update cache clean. Finally, if you're on Windows 11, keep your system drive with at least 20GB free; low disk space can trigger permission weirdness during updates.

And if you're in a corporate environment, check if your IT policy restricts writing to the WindowsUpdate key via Group Policy. Sometimes the fix is a quick call to IT.

That's it. You'll be back to getting updates in minutes, not hours. If you hit a snag, the Event Viewer will point you in the right direction — trust it over generic advice.