Error 0x80070005, which translates to “Access is denied,” appears in Windows 10 when a process or service lacks the necessary file, folder, or registry permissions to complete an operation. The fix usually involves granting the affected service or user account explicit permissions, resetting the Windows Update components, or repairing the registry keys that control service access.
What Causes Error 0x80070005
This error is a permissions problem at its core. Windows 10 relies on a strict access control system where every file, folder, and registry key has an associated security descriptor that lists which users and groups can read, modify, or execute it. When a service tries to access a resource it does not have rights to, the operating system returns error code 0x80070005.
Common triggers include:
- Windows Update failing to install updates because the SoftwareDistribution folder has incorrect permissions
- Third-party antivirus software locking system files that services need to access
- Corrupted user profile permissions after a failed upgrade or restore
- Registry keys under HKLM\SYSTEM\CurrentControlSet\Services that have lost their default security settings
- Services running under a local account that lacks the “Log on as a service” right
The error frequently appears in the Windows Event Viewer under the System log, often alongside Event ID 7000 or 7023, which indicate that a service failed to start. It also shows up when running certain command-line tools like sc start or when installing applications that register Windows services.
How Permissions Work in Windows Services
Every Windows service runs under a security context, typically LocalSystem, NetworkService, or LocalService, or a dedicated user account. The service control manager (SCM) checks the service’s executable file, its dependencies, and the registry keys that store its configuration before allowing it to start.
The registry path HKLM\SYSTEM\CurrentControlSet\Services\[ServiceName] holds critical settings including the image path, start type, and account credentials. If the security descriptor on this key is missing the default entries for SYSTEM, Administrators, and Users, the SCM cannot read the configuration and returns access denied.
Similarly, the service executable itself must have read and execute permissions for the account the service runs under. If a service is configured to run as a domain user but that user has been removed or its password changed, the SCM cannot authenticate and throws 0x80070005 rather than a more specific credential error.
Step-by-Step Fixes for Error 0x80070005
Start with the simplest fix and work through the list until the error clears. Most users resolve this within a few minutes.
- Run the Windows Update troubleshooter. Open Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Update, and run it. This automated tool resets the Windows Update service permissions and clears the download cache.
- Reset Windows Update components manually. Open an elevated Command Prompt (right-click Start, choose “Command Prompt (Admin)” or “Windows PowerShell (Admin)”). Run these commands one at a time:
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver
Then rename the SoftwareDistribution and catroot2 folders:ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.old
Finally, restart the services:net start wuauservnet start cryptSvcnet start bitsnet start msiserver - Grant the service account full control. Open the Services console (services.msc), find the service that failed, right-click and select Properties. Go to the Log On tab, note the account, then open the registry editor and navigate to the service’s key. Right-click the key, choose Permissions, and add the service account with Full Control.
- Check the service executable permissions. Navigate to the file path in the service’s ImagePath (found in the registry key). Right-click the executable, go to Properties > Security, and ensure the service account has Read & Execute rights.
- Repair the registry security descriptors. If the above fails, export the affected service key as a backup, then delete it and restart the computer. Windows will recreate the key with default permissions. Only do this for non-critical services.
- Perform a system file check. Run
sfc /scannowin an elevated Command Prompt. This verifies that all protected system files have the correct versions and permissions.
When the Error Affects Windows Update Specifically
If 0x80070005 appears when checking for or installing updates, the SoftwareDistribution folder is the prime suspect. This folder stores downloaded update files and temporary data. Over time, its permissions can become corrupted, especially after a failed update or an interrupted shutdown.
Beyond the reset steps above, you can also use the DISM tool to repair the Windows image itself. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt. This command checks the component store for corruption and fixes it using Windows Update as the source, which is a more thorough repair than SFC alone.
Another common cause is third-party security software. Antivirus programs that integrate deeply with the operating system can block legitimate service operations. Temporarily disabling real-time protection or uninstalling the security suite entirely can confirm whether it is the culprit. If the error disappears after uninstalling, consider switching to a different security product or adding an exclusion for the Windows Update folders.
Registry Permissions and the Services Key
The registry is where the most persistent instances of this error originate. The HKLM\SYSTEM\CurrentControlSet\Services key contains hundreds of subkeys, one for each installed service. Each subkey has a default security descriptor that grants SYSTEM full control, Administrators read and write, and Users read.
If a cleanup tool, a malware infection, or a manual registry edit strips these permissions, the service fails to start with access denied. To check and repair:
- Open regedit.exe as administrator
- Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[ServiceName] - Right-click the key, select Permissions
- Ensure SYSTEM has Full Control, Administrators has Read, and Users has Read
- If any are missing, click Add, type the group name, and assign the appropriate rights
For a broader fix, you can restore the entire Services key to its default ACL using the secedit command or by importing a known-good registry backup. However, this is an advanced operation and should only be attempted with a full system backup first.
Common Misconceptions and Pitfalls
One frequent misunderstanding is that 0x80070005 always means the user account is locked out or the password is wrong. While credential issues can cause a similar error, this specific code points to a permissions problem rather than an authentication failure. Changing the service’s password without fixing the file or registry ACLs will not resolve it.
Another mistake is running the fix commands without administrator privileges. The net stop and ren commands require an elevated prompt. If you run them from a standard user account, you will get a different access denied error, which can be confused with the original problem.
Some users also attempt to take ownership of the entire Windows folder or grant Everyone full control over system directories. This is not recommended because it weakens the security model and can cause other services to fail or behave unpredictably. The correct approach is to grant permissions only to the specific service account that needs access.
Finally, remember that a reboot is often necessary after making permission changes. The service control manager caches security information, and some changes only take effect after a restart. If the error persists after applying fixes, restart the computer before trying more aggressive solutions.
Frequently Asked Questions
Can I ignore error 0x80070005 if it only appears once?
If it appears once and the related service or update works afterward, it may have been a transient issue. However, if it recurs, it indicates a persistent permission problem that should be fixed to prevent future failures and potential security vulnerabilities.
Will resetting Windows fix this error?
Yes, a Windows reset or in-place upgrade repair will restore all default permissions and registry settings. This is a last-resort option because it reinstalls the operating system while keeping your files, but it takes time and may require reinstalling applications.
Is this error caused by a virus?
Not necessarily, but malware can modify registry permissions or replace system files, which would trigger this error. Running a full antivirus scan is a reasonable diagnostic step, but the error alone does not indicate an infection.
Why does the error appear when installing software?
Installers often create new services or modify existing ones. If the installer runs without sufficient privileges or the target service key has restrictive permissions, the installation fails with 0x80070005. Running the installer as administrator usually resolves this.
Does this error affect Windows 11 as well?
Yes, the same error code and underlying permission mechanisms exist in Windows 11. The fixes described here apply to both operating systems, though the Settings menu layout differs slightly in newer versions.
How do I know which service is causing the error?
Open Event Viewer, navigate to Windows Logs > System, and look for red error events around the time the problem occurred. The event details will name the specific service and often include the error code. The Services console also shows the status of each service, and any that fail to start will display a message.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Error 0x8007025d in Windows 10
- Fix Alexa App Stuck on Setup
- Android Camera for 7 Office Tasks: Step-by-Step
- Pair Phone to Pioneer Stereo After Bluetooth Reset
- Fix Windows Not Saving Remote Desktop Credentials
- Essential Tips for macOS Users Switching to Windows