Windows 0x80070005Medium

Error 0x80070005 in Windows: Causes and 4 Proven Fixes

Error code 0x80070005 indicates denied access to system files or folders. This guide covers the exact causes of the block and provides step-by-step instructions to restore normal system operation.

Updated at April 5, 2026
15-30 min
Medium
FixPedia Team
Применимо к:Windows 10Windows 11Windows Server 2019Windows Server 2022

What Does Error 0x80070005 Mean

The 0x80070005 code corresponds to the E_ACCESSDENIED system status (Access Denied). Windows generates this error when a process, file, or service attempts to perform a read, write, or registry modification operation without the necessary privileges. This error most commonly appears when running installers, attempting to move files into system directories, or downloading patches via Windows Update. The system interrupts the action and blocks further task execution as a security measure.

Common Causes

This issue is rarely related to hardware failures. In 95% of cases, it is caused by software-level restrictions:

  • Lack of administrator privileges. A user account attempts to modify files in C:\Windows or C:\Program Files without elevated permissions.
  • Corrupted NTFS permissions. Accidental modification of the ACL (Access Control List) for the SoftwareDistribution folder or other system directories.
  • Security software interference. Third-party antivirus programs or advanced firewalls may mistakenly flag a legitimate installation process as a threat and block disk access.
  • Corrupted system files. Registry errors or damaged dll libraries can break the process authentication chain.
  • Service conflicts. Multiple processes attempting to write to the same file simultaneously can cause a deadlock.

Troubleshooting Steps

Follow these steps in order. Start with basic permission checks and only proceed to component resets if the initial steps do not resolve the issue.

Method 1: Run as Administrator and Check Folder Permissions

Most installers require elevated privileges to extract files into protected directories.

  1. Right-click the .exe or .msi file.
  2. Select Run as administrator.
  3. If the error occurs during manual file copying, open File Explorer, right-click the target folder → PropertiesSecurity tab.
  4. Click EditAdd → type Everyone or Users → click Check NamesOK.
  5. In the permissions list, check the box for Full control and apply the changes.

💡 Tip: If the "Edit" button is grayed out, go to the Security tab → Advanced → change the folder owner to your user account.

Method 2: Reset the Windows Update Cache

During system updates, corrupted temporary files often block the download of new components. Resetting the cache recreates the folder with clean access permissions.

Open an elevated command prompt (Win + XTerminal (Admin)) and run the following commands sequentially:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

After stopping the services, rename the cache directories:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Restart the services:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Now, open SettingsWindows Update and click Check for updates.

Method 3: Temporarily Disable Third-Party Security Software

Antivirus programs with HIPS (Host Intrusion Prevention System) features can aggressively block modifications to system directories.

  1. Open your antivirus interface (Kaspersky, ESET, Avast, Bitdefender, etc.).
  2. Locate the Protection or Security section → Pause protection.
  3. Select a duration of 10–15 minutes or Until restart.
  4. Retry the action that triggered the 0x80070005 error.
  5. Immediately after finishing, re-enable protection and add the installer to the exclusion list if the blockage occurs again.

⚠️ Important: Do not disable the built-in Windows Security (Microsoft Defender) if you do not have a third-party antivirus installed. Its components are deeply integrated into the OS kernel, and manually disabling them can cause additional service failures.

Method 4: Repair System Files Using SFC and DISM

If core Windows components are corrupted, standard permission checks will not help. Use the built-in diagnostic utilities instead.

In an elevated terminal, run the system file integrity check:

sfc /scannow

The utility will scan protected files and automatically replace corrupted copies from the component store. If SFC reports that it could not repair the files, run a deeper image repair:

DISM /Online /Cleanup-Image /RestoreHealth

The process may take 5–15 minutes depending on disk speed and internet connection stability (DISM downloads healthy components from Microsoft servers). Once complete, restart your computer.

Prevention Tips

To prevent this error from recurring, follow these best practices for handling system files and updates:

  • Always run installers and system utilities with elevated privileges, especially when working with the Program Files and Windows directories.
  • Do not manually interrupt the system update process. Turning off the PC during patch installation corrupts temporary file permissions.
  • Configure exclusions in third-party antivirus software for the C:\Windows\SoftwareDistribution and C:\Windows\Temp folders.
  • Regularly clean your drive using the Disk Cleanup utility (launched via cleanmgr), removing outdated Windows installations and temporary files.
  • Avoid third-party "registry optimizers" and system tweakers. They frequently modify ACLs without your knowledge, leading to widespread access denied errors.

F.A.Q.

Why does error 0x80070005 specifically occur during Windows updates?
Can I safely ignore error 0x80070005?
Do I need to reinstall Windows after fixing this?
Is it safe to disable my antivirus to fix this issue?

Hints

Run the program as administrator
Check folder permissions
Reset the Windows Update cache
Repair system files using SFC
Temporarily disable third-party antivirus
FixPedia

Free encyclopedia for fixing errors. Step-by-step guides for Windows, Linux, macOS and more.

© 2026 FixPedia. All materials are available for free.

Made with for the community