Fix Windows Error 0x80070005: Access Denied

Windows error 0x80070005, sometimes written as 0x800700005, means an operation was denied access. It can interrupt Windows Update, app installation, Microsoft Store downloads, or file access. Work through the steps below in order, starting with the least disruptive; you will need an administrator account for some repairs.

What You’ll Need

• A Windows account with administrator permission, or access to one.
• An internet connection if the error occurs during an update or Store download.
• About 15–30 minutes, and time to restart Windows.
• If the error affects important files, a current backup before changing permissions or running repairs.

Step-by-Step

1. Identify where the error appears. Note the exact action that triggers it: installing an update, opening an app, downloading from Microsoft Store, or accessing a particular file or folder. If Windows displays an update number or app name, write it down. The code describes an access problem, but the cause differs by task.
2. Restart and retry once. Save your work, restart the PC, and repeat the action. A restart can clear a temporary lock on a file or pending update. If the problem began after connecting a work or school device, or changing security settings, note that context too.
3. Check your account and date settings. Open Settings > Accounts and confirm you are using the intended Windows account. If the task requires administrator rights, right-click the relevant installer or app and choose Run as administrator—only when you trust its source. Also open Settings > Time & language > Date & time and enable automatic time settings if they are wrong; incorrect time can interfere with update and Store services.
4. Run the relevant Windows troubleshooter. Open Settings > System > Troubleshoot > Other troubleshooters. If Windows Update is failing, select Windows Update > Run and follow the prompts. For Store or app issues, use the troubleshooter available for that component in your version of Windows. Names and availability can vary by release; do not run unrelated troubleshooters just to clear the code.
5. Install pending Windows updates. Go to Settings > Windows Update, select Check for updates, install available updates, then restart. Try the original task again. If only one update fails, record its identifier and check its status in Windows Update before attempting any manual installation.
6. Repair system files from an elevated terminal. Right-click Start and open Terminal (Admin) or Command Prompt (Admin). Approve the prompt, then run this command and wait for it to finish:
   DISM.exe /Online /Cleanup-Image /RestoreHealth
   Next run:
   sfc /scannow
   These tools check and repair Windows component and system files. Do not close the window while they are running. Restart if either tool reports repairs, then test again.
7. For Microsoft Store problems, reset its cache. Press Windows key + R, type wsreset.exe, and press Enter. A blank command window may appear briefly; wait for it to close and for Store to reopen, then try the download again. If one app alone fails, open Settings > Apps > Installed apps, select the app, choose Advanced options if available, and try Repair before Reset. Reset can remove that app’s local data, so check its backup or sync options first.
8. Check the specific file or folder only when access is the issue. Right-click it, choose Properties > Security, and review whether your account has the access needed for the task. If it is your own file, ask its owner or an administrator to grant the appropriate permission. Avoid changing ownership of Windows, Program Files, or other system folders; broad permission changes can break apps or weaken security.
9. Retry after checking security software. Security software or a managed-device policy may block an installer or update. Check its notification or protection history for a block at the time of failure. Do not turn off antivirus or firewall protection as a general fix. On a work or school PC, contact the administrator instead of changing policy or permissions.

Common Mistakes

• Changing permissions across the whole drive. Granting broad access to “Everyone” or taking ownership of system directories can create security problems and prevent Windows from working properly. Restrict permission changes to a personal file or folder you own.
• Running every command found online. Use the DISM and SFC commands above only in an administrator terminal, and enter them exactly. Avoid scripts or commands that delete update folders, edit the registry, or disable security without a clear, trusted reason.
• Repeating a failed update without restarting. Complete the requested restart after installing updates or repairing system files, then test the original action once more.
• Resetting an app before checking its data. Repair is less disruptive. Reset may remove local settings or unsynced content.

Tips

• Capture the full message and note the time, app, and action that produced it. This makes it easier to distinguish an update failure from a file-permission issue.
• Keep Windows and the affected app current, and leave enough free space for updates to download and install.
• If you use a managed work or school device, ask IT for help early. Policies can intentionally restrict installation, folders, or updates.
• Back up important personal files before doing advanced repair work. Avoid third-party “permission fixer” utilities.

Troubleshooting

If DISM reports that source files could not be found, confirm the PC is online, install pending Windows updates, restart, and run the command again. If it still fails, note the complete message rather than downloading system files from an unofficial source.

If SFC says it could not repair some files, restart and run sfc /scannow once more after DISM completes. If errors persist, record the result and consider Windows recovery options or support from the device manufacturer or administrator.

If the error affects only one account, test the same task with another authorized account. Do not move another user’s files or change their permissions without consent. If it affects only one download or installer, obtain it again from its official source and check that the file is complete. If several unrelated Windows features fail, stop making permission changes and seek professional support; a managed policy or deeper Windows issue may be involved.

When the problem remains, provide support with the exact code, the affected app or update, what you tried, and any command output. Do not share passwords, recovery keys, or private files.

Frequently Asked Questions

What does error 0x80070005 mean?
It means Windows or an app could not access a required file, folder, service, or resource. The code alone does not identify which permission or component is responsible.

Are 0x800700005 and 0x80070005 the same error?
The commonly used Windows access-denied code is 0x80070005. If a message shows an extra zero, check the original screen or log carefully; do not assume every longer code is identical.

Can I fix this without administrator access?
You can restart, check your account, and run some troubleshooters, but system repairs and certain installations require an administrator. Ask the device owner or administrator rather than trying to bypass restrictions.

Should I disable antivirus to fix it?
No, not as a routine step. Check the security app’s history for a specific block and use its supported, narrowly targeted resolution, or ask your administrator.

Will resetting Microsoft Store delete my files?
wsreset.exe clears the Store cache and is not the same as resetting every app. Resetting an individual app can erase its local data, so check its sync and backup options first.

What if the error returns after these steps?
Record which action triggers it and the full message, then contact your administrator or Windows support with the DISM/SFC results. Avoid broad permission edits or unofficial repair tools.

Related

• How to Add Multiple Telegram Accounts
• Plan Power and Cooling for PCIe GPU Servers
• How to Edit Text in WhatsApp After Sending