In this guide
Error 0x80070005 means access was denied, but Windows can show it in the Microsoft Store, activation, backup, an app installer, or Windows Update. The location matters. This guide is for an update that fails in Settings > Windows Update or appears in Update history; it is not a universal permissions reset.
Record the failure point before repairing anything
Open Settings, Windows Update, Update history and write down the KB number, date, and whether the failure occurs during download, installation, or restart. Microsoft currently describes 0x80070005 in its update guide as an Access Denied error or insufficient permissions to install updates.
| Finding | What it narrows | Next check |
|---|---|---|
| Account is not an administrator | Insufficient rights are plausible | Use an authorized administrator account |
| Only one KB fails | Package or compatibility-specific problem | Check that KB’s known issues and exact error |
| Every update fails | Policy, update components, security, or corruption | Run the troubleshooter and restart |
| Code appears in Microsoft Store | Different workflow and permissions | Use Store troubleshooting, not this sequence |
| DISM or SFC reports corruption | System files or component store affected | Complete repair and retry the same KB |
1. Verify the account and device ownership
Open Settings > Accounts > Your info and confirm the account type. On a personal PC, sign in with an administrator account you control. On a work or school PC, do not remove management, policies, or security tools. Capture the error and give IT the KB number; the update may require organizational approval or a maintenance window.
2. Run the official Windows Update troubleshooter
Open Settings > System > Troubleshoot > Other troubleshooters and run Windows Update. Current Microsoft guidance may launch an automated flow in Get Help. Apply the recommended fix, restart even if the tool reports success, and then test the same update once.
Judge the result in Update history, not only by the troubleshooter’s closing message. If the update now stalls without 0x80070005, the symptom has changed; use the Windows Update stuck checklist instead of repeating permissions changes.
3. Check the event that preceded Access Denied
Review whether the problem began after installing a security suite, changing a work policy, restoring a backup, or using a system-tuning script. Check the security product’s history for a block at the same time as the update. Do not permanently disable protection. If a vendor documents a temporary test, follow it briefly and turn protection back on immediately.
Restart Windows from the Start menu, connect a laptop to power, leave adequate free space on the system drive, and disconnect a VPN temporarily only when policy allows. Change one condition at a time so a new error code remains useful evidence.
4. Use DISM and SFC when corruption is plausible
If the troubleshooter reports damaged components, several Windows features fail, or multiple updates repeatedly fail, open Terminal or Command Prompt as administrator. Microsoft recommends servicing the Windows image with DISM before running System File Checker:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannowLet each command finish and record the final message. A percentage that pauses is not proof that the tool has frozen. Restart after repairs and retry Windows Update. If DISM cannot find source files, do not point it at an image from a different Windows edition or build.
5. Reinstall the current Windows version only as a later repair
Windows 11 may offer Settings > System > Recovery > Fix problems using Windows Update, which reinstalls the current version to repair system files and components while preserving apps, files, and settings. Microsoft notes that this option can be unavailable on managed devices or older releases. Back up important files and confirm BitLocker recovery access before any advanced repair.
If Windows asks for a recovery key after the restart, use the BitLocker recovery key guide. If the machine instead crashes with a stop code, photograph the code and follow the blue-screen diagnosis after an update.
Avoid broad permission recipes
- Do not grant Everyone Full Control over C:Windows, System32, or registry branches.
- Do not run an ACL-reset script copied from an unknown forum without a scoped diagnosis and backup.
- Do not download replacement DLL files or update packages from unofficial sites.
- Do not erase SoftwareDistribution as the first step before recording the KB and running the troubleshooter.
- Do not reinstall Windows before protecting files and checking device encryption.
When to escalate
Contact organizational IT for managed devices. For a personal PC, seek Microsoft or qualified support when the same KB still fails after the troubleshooter, administrator check, restart, and completed DISM/SFC repair; when DISM cannot repair the image; or when disk, encryption, or boot errors appear alongside 0x80070005.
Provide the Windows edition and version, KB number, exact code, failure stage, and final DISM/SFC messages. Those details make the case actionable and avoid a destructive generic permissions reset.
Frequently asked questions
Does 0x80070005 always mean I need an administrator account?
No. Administrator access is the first check, but policy, security software, or damaged update components can also produce Access Denied.
Should I reset all Windows permissions?
No. Broad permission changes can weaken security and create additional failures. Scope the error to Windows Update and a specific KB first.
Will DISM and SFC delete personal files?
They service the Windows image and protected system files, but you should still maintain a current backup before advanced repair.