0x80070005This guide concerns Windows Update, not the same code in other products. A denied resource, policy restriction and security block require different decisions.
Windows Update error 0x80070005
0x80070005 means access was denied during Windows Update. Identify the update, device management and any resource named in the logs before deciding what to repair.
Try this first
2 quick checks · ~8 min
Find your situation
See all the clues. Choose the one that matches what you observe.
Work or school device
Policy or a management agent may restrict access. Coordinate with IT without bypassing controls.
An explicit security block is recorded
Match the file and time to the attempt; having antivirus installed is not enough.
A log identifies a resource
The specific path enables targeted repair; do not generalize its permissions across Windows.
The denied object is not identified
Keep that limitation and the results before considering broader component repair.
Diagnostic signals
- ObservationE_ACCESSDENIED in the failed attempt
- It indicates denied access in this context; the line and time matter when choosing a resource to investigate.
- ObservationDISM/SFC finish without errors
- It does not prove every permission is correct or rule out policy or security restrictions.
Step-by-step solutions
Confirm the context, update and time
Confirm that 0x80070005 occurs during Windows Update and record the update or KB and the failed attempt’s time. Here it means E_ACCESSDENIED: access to a required resource was denied. The same number in Store or while opening a file needs a different diagnosis.
It does not identify the missing permission by itself. Microsoft lists WinSxS, SoftwareDistribution, the Component Based Servicing key, TrustedInstaller or SYSTEM permissions, policies and security blocks. These are categories to investigate, not instructions to reset all of them.
If installation has ended with an error and Windows responds, save work and you may restart normally and retry once. If the code returns, keep the new time and move to logs; do not repeat restarts or interrupt an active install.
Separate device management from a recorded block
If this is a work/school device or settings are managed, contact IT with the KB, time and code. An administrator account does not prove policy permits the operation; do not disconnect the organization or force permissions.
Check your security tool’s history at that time. If it records a blocked update file or folder, keep the event and ask the vendor or IT to review that case. A matching alert is a useful lead; no alert does not rule out every block.
Do not disable antivirus/firewall, download permission utilities or add broad exclusions. If no specific block or policy explains it, identify the resource in CBS or Windows Update before choosing a repair.
Look for the denied resource in the logs
Open a copy of C:\Windows\Logs\CBS\CBS.log in a text viewer without changing the original. Use the actual Windows directory if installed elsewhere. Search for 0x80070005 or E_ACCESSDENIED near the attempt’s time and read adjacent lines: they may name the file, folder, package or key involved.
Get-WindowsUpdateLogRun in Windows PowerShell to generate a readable copy of Windows Update logs; it does not reset permissions. Open the output path it reports and search for the code around the recorded time.
A named path alongside denied access guides targeted repair; a line saying a package could not be opened does not establish which ACL is wrong. Do not diagnose the current attempt from an old error for another update.
If no object is clear or you cannot access the log, preserve that limitation. Do not take ownership of the file to read it: ask IT/Microsoft for help with the relevant excerpt. If another code replaces 0x80070005, follow the new state.
Advanced checks
Continue if the earlier steps did not help. Read each procedure’s precautions first.
Choose a targeted repair with a backup
If a log identifies WinSxS, SoftwareDistribution or a specific key, take that path and context to IT or Microsoft. Repair must match the resource and official instructions applicable to this machine; a path appearing in a log does not itself authorize changing its security.
Resetting an ACL changes who can access a resource; changing ownership changes who can administer its permissions. On protected components this can affect servicing and updates. Do not extend a correction across C:\Windows or every registry key.
No ACL-changing commands or manual registry edits are supplied here because readers do not share one diagnosed object. If support specifies a correction, verify an OS-disk backup, authorization and a recovery procedure before applying it. Then retry the same KB and compare the log.
Consider DISM and SFC when no targeted cause is established
If the object could not be identified and there is no unresolved block or policy, Microsoft-supported component repair may be reasonable. Do not use it to bypass managed restrictions or as proof that permissions caused the failure.
DISM /Online /Cleanup-Image /RestoreHealthRun in a terminal with authorized administrator access and wait for the result. This repairs the component store and normally uses Windows Update as its source. If it fails, keep the code rather than chaining commands as though it succeeded.
sfc /scannowAfter DISM succeeds, check protected system files with SFC and let it finish. If it reports repaired files, restart normally and retry the update.
Finding no corruption does not prove ACLs, policies or blocks are correct. Keep an unable-to-repair result for support. If both tools finish but the same KB still fails with 0x80070005, compare the new log rather than endlessly repeating the sequence. DISM 0x800f081f belongs to repair-source troubleshooting.
Still not working?
Keep the KB, time, code and relevant log lines with private details removed. State whether the device is managed and what DISM/SFC reported if used. Ask IT or Microsoft for a targeted repair; do not reset random permissions or repeat repairs without new information.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Microsoft LearnOfficialTroubleshoot Windows Update error 0x80070005
- Microsoft SupportOfficialTroubleshoot problems updating Windows
- Microsoft LearnOfficialCommon Windows Update errors
Source review: . A documentation review, not a physical hardware test.