Skip to content
PermissionsWindows

Fix Windows Error 0x80070005 (Access Denied): Find the Permission Failure Without Risky Resets

Windows error 0x80070005 signals an access-denied operation, but the blocked resource may be a file, service, registry key, update component, or application identity. This guide shows how to identify which operation failed before changing permissions.

Quick Answer

Record the exact app or update that shows 0x80070005 and retry once after a restart. For Windows Update, run Settings → System → Troubleshoot → Other troubleshooters → Windows Update where available, then check update history. For a file or application failure, verify that you are using the intended account and that the specific folder is accessible. Do not recursively take ownership of Windows system folders or disable security software.

What does 0x80070005 mean?

The hexadecimal HRESULT 0x80070005 commonly maps to E_ACCESSDENIED: an operation was rejected because its security context lacked access. The code identifies a class of failure, not the exact resource or the reason. The same code can appear while installing updates, activating Microsoft Store applications, starting a service, opening a file, or running a backup. A repair that is appropriate for one scenario may damage another.

Step-by-Step Troubleshooting

Start with the low-risk checks. Use advanced steps only after the specific failure is identified.

Identify the failing operation

Record the app, update, file path and exact time of the access-denied error.

Try the operation from the correct Windows account

Sign in with the intended account; do not broadly disable access controls.

Check the target resource

Confirm the file or folder exists and inspect its Security tab for the affected user.

Recognize the scenario before troubleshooting

Where the error appears Evidence to collect First area to investigate
Windows Update KB number, update history, time of failure Update service and component health
Microsoft Store or app installer App name, install location, Store error details App package and user account context
File or folder operation Exact path and action attempted File permissions, ownership, encryption, controlled folder access
Backup or scheduled task Task name, run-as account, destination Service identity and destination rights
Application launch App name, event timestamp, installation source App data folder and application-specific logs

Before you begin

  1. Sign in with your normal account and note whether the operation is supposed to require administrator approval. Administrator access does not automatically grant access to every protected file.
  2. Back up important documents. If you intend to change a system configuration, create a restore point where System Protection is available.
  3. Record the full error message and timestamp. Take a screenshot before dismissing the dialog.
  4. Disconnect unnecessary external storage only if the failing operation is unrelated to it. Avoid changing several variables at once.

Step 1 — Reproduce the failure once and isolate its scope

Try the same operation once after restarting Windows. Does the problem affect only one file, one app, one Windows account, or every update? If a different user can complete the operation, investigate account-specific configuration before repairing Windows globally. If the error follows a particular removable drive, check that drive’s file system and access policy instead.

Verification: Record whether the same action fails at the same stage. A changed message is useful evidence; do not treat it as proof that the original problem is fixed.

Step 2 — For Windows Update, use supported diagnostics first

Open Settings → Windows Update → Update history and write down the failed update identifier. Run the Windows Update troubleshooter if it is offered by your Windows version. Restart and try the specific update once. If the update has a known issue or is temporarily blocked for your device, repeated installation attempts are unlikely to help.

To inspect system image health, open Windows Terminal (Admin) and run:

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

DISM /ScanHealth checks component-store corruption; it does not repair it. sfc /scannow scans protected system files and attempts repair. If DISM reports that repair is needed, review Microsoft’s current guidance before running DISM /Online /Cleanup-Image /RestoreHealth, particularly on managed devices or where Windows Update is unavailable. These commands are not universal fixes for 0x80070005.

Verification: Recheck the failed KB in Update history. If it still fails, preserve the update error details rather than repeatedly clearing caches.

Step 3 — For a file or folder, inspect permissions without taking ownership

Right-click the affected file or folder → Properties → Security. Check the account or group and the specific permissions needed for the action. On a work or school PC, access may be intentionally managed. For an ordinary user-created folder, the owner or administrator can grant narrowly scoped permissions after confirming the intended access.

Do not apply Full Control to Everyone, do not recursively replace permissions under C:\Windows or C:\Program Files, and do not take ownership of the entire system drive. Those changes can break servicing and weaken security. If the item is encrypted, permissions alone may not unlock it.

Verification: Test only the originally blocked operation. Confirm other users retain their expected access.

Step 4 — Check whether ransomware protection blocked the app

Windows Security’s Controlled folder access can restrict an untrusted application from writing to protected folders. Open Windows Security → Virus & threat protection → Ransomware protection (availability varies) and review recent protection history. If the exact trusted application was blocked, assess its publisher and provenance before permitting it. Do not disable protection globally as a shortcut.

Verification: Retry the app with protection still enabled. If an allow-list change was made, confirm it applies only to the verified executable.

Step 5 — For services or scheduled tasks, check the running identity

A service or scheduled task can fail even when your interactive account is an administrator. In Task Scheduler, review the task’s configured account and whether it runs only when the user is logged on. In Event Viewer, correlate the task or service failure time with relevant Windows logs. Confirm that the service identity has access to its own data and destination folders. Do not switch services to LocalSystem just to bypass an access denial.

Step 6 — Investigate application-specific failures

If only one app fails, update it from its official publisher and check its own logs or repair option. For Microsoft Store apps, use the app’s Advanced options → Repair if available; consider Reset only after confirming what local data may be removed. For installers, verify that the package was obtained from a trusted source and that corporate device policy is not blocking installation.

Advanced diagnosis: correlate events, do not guess

Open Event Viewer and inspect relevant logs around the recorded timestamp. Windows Update failures may be documented in update history and servicing logs; application failures may be in Application logs or publisher-specific logs. A single event containing Access is denied is not enough to conclude which ACL should be changed. Identify the process, operation, path, and security identity before making a targeted adjustment.

What not to do

  • Do not paste scripts that reset all Windows registry or file permissions.
  • Do not delete SoftwareDistribution or catroot2 folders as a first response.
  • Do not disable Defender, User Account Control, or antivirus protection merely to make an installer run.
  • Do not download third-party “0x80070005 repair” executables.

Confirm the repair

Repeat the exact failing action twice. For updates, confirm the KB appears as successfully installed and Windows Update reports no pending restart. For files, verify both read/write access as appropriate and that unrelated folders remain protected. For scheduled tasks, confirm the next normal scheduled run—not only a manual test—succeeds.

Rollback and escalation

If you changed an individual folder ACL, restore its prior entries from the screenshot or documented baseline. Remove any temporary application exception that is no longer needed. On managed devices, provide IT with the exact error, timestamp, device name, account context, and failed action. If Windows system-file repairs report unrepaired corruption, follow Microsoft servicing guidance rather than escalating immediately to a reinstall.

Solution Checklist

0/5 completed

Frequently asked questions

Does 0x80070005 always mean my account is not an administrator? No. A service, app container, protected folder, or policy can deny access independently of your interactive account’s administrator membership.

Should I run the installer as administrator? Only if the publisher documents that elevation is required and you trust the installer. Elevation is not a substitute for diagnosing a protected resource.

Will SFC fix every access-denied error? No. It targets protected system-file integrity, not ordinary user-folder ACLs or app-specific permissions.

Is this error a sign of malware? Not by itself. Investigate unexpected security changes or suspicious software separately; the code alone is not evidence of infection.

Official references to review before publication

Editorial verification note: Confirm exact Settings navigation against the supported Windows builds and replace general support landing pages with relevant current articles before publishing.

Did this solution fix your problem?

Optional feedback helps us improve this guide. Never send private data.

PRBLEM / COMMUNITY

Discuss This Solution

Ask a question, compare results, or share a safe fix that worked for you.

Describe the exact issueInclude the error, device or software version, and what you already tried.
Protect your informationNever post passwords, recovery codes, private logs or personal data.
Retry if the discussion does not load

Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.

Can't find your answer?

Tell our editors which problem needs a guide. Do not include passwords, API keys, email addresses, private URLs, or full error logs.

Analyze Error

Paste an error message to identify its likely category. Analysis takes place in your browser; only a short error category will be used if you choose to search.

Do not paste passwords, tokens, private URLs or full logs.