How to Fix Error 0x80070005 (Access Denied) in Windows

Quick Fix

Try this first (under a minute):

1. Make sure you are logged into an Administrator account, not a Standard user account.
2. Open the Start menu, search ‘Command Prompt’, right-click it and choose Run as administrator (this alone fixes it if the error appeared because a command or install wasn’t run elevated).
3. Temporarily disable third-party antivirus software and retry the action that failed (update, install, or activation).
4. Restart your PC and try again – a simple reboot clears temporary locks on files that can trigger this error.

Step-by-Step Guide

What Error 0x80070005 Means

Windows Update error 0x80070005 (E_ACCESSDENIED) occurs if the update process can’t access required files, folders, or registry entries, and this error typically indicates a permissions problem that affects the Windows component store, the Software Distribution folder, or related system resources. The exact same code also shows up in other contexts – installing or updating Microsoft Store apps, activating Office or Windows itself, running System Restore, or even deleting a file – because in every case Windows is essentially saying ‘I don’t have permission to do this.’

Error Code 0x80070005 in Windows is synonymous with the term ‘Access Denied.’ This issue takes place when the system does not have enough permissions to proceed with an update. Common underlying causes include:

1. The TrustedInstaller service account not having permissions on the WinSxS or SoftwareDistribution folders, incorrect permissions on the registry subkey for Component Based Servicing, a third-party antivirus or security tool locking update-related files, the SYSTEM account lacking Full Control permission on the Windows folder, or a Group Policy setting restricting write access to system directories.
2. The Access Denied error notification comes up when a Windows user tries to install some system updates but does not have the required permissions to operate due to the personal computer’s security policies and settings.
3. If files are damaged or entries in the registry database are incorrect, this may be because the system has been infected with malware.

Step-by-Step Fixes (Windows – try in order)

1. Confirm you’re using an administrator account

Ensure you are logged in as an Administrator, since this error often triggers because a Standard User account cannot write the necessary update files. Go to Settings > Accounts > Family & other users to check your account type, or switch to an existing administrator account and retry.

2. Run the built-in Windows Update Troubleshooter

Microsoft provides a built-in Windows Update Troubleshooter that automatically identifies and fixes common update-related issues, including permission problems like error 0x80070005. Go to Settings > Update & Security > Troubleshoot, select Windows Update, click Run the troubleshooter, and follow the on-screen instructions to complete the process, which can resolve simple misconfigurations and help move the update process forward.

3. Run SFC and DISM to repair system files

If corrupted system files are causing the issue, running the System File Checker (SFC) tool can help: open Command Prompt as an administrator, type sfc /scannow and hit Enter, then let the scan complete – it will detect and repair corrupted files automatically. If problems remain, follow up with a DISM repair. To repair the component store, run the DISM RestoreHealth command at the command prompt; by default, DISM uses Windows Update as a repair source. Restart afterward and retry.

4. Reset Windows Update components

If the error persists, reset all Windows Update components. At an administrative command prompt, run: net stop wuauserv, net stop bits, net stop cryptSvc, ren %windir%SoftwareDistribution SoftwareDistribution.old, ren %windir%System32catroot2 catroot2.old, net start cryptSvc, net start bits, net start wuauserv. Then restart the computer and try the update again.

5. Reset permissions on the component store (advanced, Windows 10/11 and Server)

Open an administrative Command Prompt and run: icacls “%windir%WinSxS” /reset /t /c /q and icacls “%windir%SoftwareDistribution” /reset /t /c /q, then to designate that the TrustedInstaller account owns the WinSxS folder, run icacls “%windir%WinSxS” /setowner “NT SERVICETrustedInstaller” /t /c /q. Restart and retry after each command. Back up your system disk before doing this, as recommended in Microsoft’s own troubleshooting documentation.

6. Check antivirus and security software

A third-party antivirus or security tool can lock update-related files or folders, causing this exact error. Temporarily disable it (or add an exclusion for the Windows folder) and retry. Follow up with a full malware scan using Windows Defender or your preferred antivirus, since in some cases malware infections can alter system settings and block updates, and running a full malware scan can help identify and remove malicious software that may be interfering with the update process.

7. If it’s happening with Microsoft Store apps specifically

If the error mainly occurs when using apps from the Microsoft Store, try resetting the Store cache using the built-in wsreset tool: press Windows key + R to open the Run dialog, then type wsreset and press Enter. Some users have also had success by adjusting registry permissions on specific file-type extension keys, granting ‘Full Control’ to ‘All Application Packages,’ though this is an advanced step best attempted only if you’re comfortable editing the registry.

8. If it’s happening during Office or Windows activation

If the 0x80070005 error started after updating Windows, you may be able to fix it by updating the registry – though Microsoft warns using Registry Editor incorrectly can cause serious problems. For Office specifically, running Office as administrator helps fix permission issues that might cause Office activation to fail, and the Microsoft 365 activation troubleshooter can help you identify and fix activation issues. For Windows Server activation, the issue can involve DCOM permissions: the SELF account not having the correct DCOM permissions can be fixed by opening dcomcnfg (Component Services) and restoring those permissions.

9. Check disk space and try a clean boot

Windows Updates require significant free space (often 7GB+); delete temp files or clear your Recycle Bin to ensure the install doesn’t fail mid-process. If the error still won’t clear, a clean boot can help isolate a conflicting startup program or service: a clean boot can assist in identifying the source of startup failures, software crashes, and Windows Update issues, and non-essential services are momentarily disabled when you do a clean boot.

When to Seek More Help

If you’ve worked through the steps above (administrator account, troubleshooter, SFC/DISM, component reset, antivirus check, and permission resets) and still see 0x80070005, treat it as a deeper issue:

1. Repeated failures after multiple fixes can indicate corrupted registry permissions from a botched previous repair, third-party ‘tune-up’ tool, or malware that altered ownership of system folders – at this point posting your WindowsUpdate.log or CBS.log details on the Microsoft Q&A forum, or contacting official Microsoft Support, is the fastest path forward.
2. On a business or server machine (Windows Server, domain-joined PC), check with your IT administrator first – Group Policy settings and management agents can intentionally restrict permissions, and changing them yourself could violate company policy or break other systems.
3. If this coincides with other odd symptoms (random crashes, unfamiliar programs, browser hijacking), prioritize a full malware/rootkit scan before doing further permission changes, since infections are a known cause of this exact error.
4. As a last resort, an in-place upgrade repair install (keeping files and apps) or a clean Windows reinstall will reset all system permissions from scratch and resolves the vast majority of persistent 0x80070005 cases – back up your data first.

Note: All steps above are Windows-specific (Windows 10, Windows 11, and Windows Server). This error code does not occur on macOS, Linux, consoles, or mobile platforms – it is unique to the Windows HRESULT error system.