Windows Update error 0x80070005: Access Denied
For Windows Update, Microsoft describes 0x80070005 as an Access Denied error or a sign that the account does not have sufficient permission to install the update.
Retry the update with administrator access
Confirm that the account installing the update has administrator access, then retry Windows Update. If the error remains, run the Windows Update troubleshooter and verify the Windows Update service is running before making deeper changes.
- Open Settings > Accounts and confirm the current account has administrator access, or sign in with an administrator account.
- Open Settings > Windows Update.
- Check for updates and retry the failed installation.
- Restart if Windows requests it and check Update history afterward.
Why this branch first: Microsoft identifies insufficient administrator permission as the primary meaning of 0x80070005 in the Windows Update troubleshooting flow.
Decode the Windows error code
Keep 0x80070005 in context and compare it with the reviewed Windows error catalog.
TroubleByte diagnostic path
Treat 0x80070005 as an Access Denied / permission signal in Windows Update.
Confirm an administrator account is performing the update.
Run the Windows Update troubleshooter and retry.
Only then investigate security software, services or update components.
Original TroubleByte diagnostic map. It summarizes the cited troubleshooting order; it is not a vendor screenshot.
What this usually means
The same hexadecimal code can appear in different Windows contexts, so this page is scoped specifically to Windows Update. Microsoft maps 0x80070005 in that workflow to Access Denied or insufficient permissions.
What we verified from the source material
Microsoft’s Windows Update troubleshooting documentation identifies 0x80070005 as Access Denied or insufficient permissions and recommends administrator access for affected updates. Microsoft’s user-account guidance corroborates how administrator privileges are configured and why elevated access should be limited rather than used casually.
Prerequisites and checks
Prepare first
- Use an administrator account for update repair steps that require elevated permission.
- Record the exact update and failure time before clearing update components.
- Create or confirm a recovery point/backup before advanced permission or system-component repairs.
Checks that prevent the wrong fix
- Confirm the error is shown by Windows Update, not another application.
- Use an administrator account for updates that require elevation.
- Avoid registry ownership or blanket file-permission changes unless a more specific diagnosis proves they are needed.
Applies to
Solutions, in order
Retry the update with administrator access
- Open Settings > Accounts and confirm the current account has administrator access, or sign in with an administrator account.
- Open Settings > Windows Update.
- Check for updates and retry the failed installation.
- Restart if Windows requests it and check Update history afterward.
Why this can work: Microsoft identifies insufficient administrator permission as the primary meaning of 0x80070005 in the Windows Update troubleshooting flow.
Run the Windows Update troubleshooter
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run the Windows Update troubleshooter.
- Apply the recommended fixes.
- Retry Windows Update after the troubleshooter completes.
Why this can work: Microsoft recommends the Windows Update troubleshooter for update failures before deeper manual changes.
Verify the Windows Update service is running
- Press Win + R, enter services.msc and press Enter.
- Find Windows Update.
- If the service is stopped, start it.
- Retry the update.
Why this can work: Microsoft includes checking the Windows Update service in its current update troubleshooting guidance.
How to know the fix actually worked
- Run Windows Update again and confirm the previously failing update installs.
- Check Update history and confirm the update is listed as successfully installed.
- Restart Windows when required and run one additional update check to verify the error does not immediately recur.
Do not count a temporary disappearance of the symptom as a confirmed fix if the problem normally returns after a restart, reconnect or several minutes of use.
When not to keep changing things
- Stop manual permission changes if the error affects broader Windows security/servicing components; use supported repair or administrator escalation instead.
- If storage, filesystem or system-file corruption is reported, address that underlying condition before repeatedly retrying the same update.
Escalation: If the update continues to fail under a confirmed administrator account, capture the failing KB number and update history details. Troubleshooting a specific update is safer than broadly changing system permissions.
Sources used for this record
Primary · checked Sep 6, 2026Microsoft — Troubleshoot problems updating WindowsOfficial documentation used to verify the troubleshooting steps.Corroborating · checked Sep 6, 2026Microsoft — Manage User Accounts in WindowsOfficial Microsoft documentation used to verify administrator-account scope and the security implications of elevated access.Discuss this exact problem
Share what happened on your system, ask a focused follow-up question, or add evidence that may help someone with the same symptom. Community posts are separate from TroubleByte editorial verification.
Start a discussion
Revision history
Show 7 recorded revisions
2026-09-06 — v0.6 media/performance pass: added a dedicated social preview card; indexing remains disabled.
2026-09-06 — v0.5 UX/discovery pass: added decision-oriented diagnostic guidance and kept indexing disabled.
2026-09-06 — v0.4 evidence pass: added a second first-party corroborating source and tightened the evidence summary; indexing remains disabled.
2026-09-06 — v0.4 depth pass: added symptom framing, prerequisites, verification checks and explicit stop conditions; indexing remains disabled.
2026-09-06 — v0.3 trust pass: assigned a named human author/source reviewer, added section taxonomy and an original diagnostic flow; indexing remains disabled.
2026-09-06 — Clarified source-review semantics and evidence scope; no hands-on hardware test is claimed.
2026-09-06 — Created as a Windows Update-specific 0x80070005 record from Microsoft support guidance; held noindex for review.