Windows system administrator troubleshooting update error on computer workstation
0x80070005Windows UpdateWindows

Fix Windows Update Error 0x80070005 – Windows 10, Windows 11 2026

Windows Update error 0x80070005 indicates access denied permissions preventing update installation. This comprehensive guide provides five proven methods to resolve permission issues and restore Windows Update functionality.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
10 Mar 202612 min read0 views
Error Code0x80070005
ProductWindows Update
KB ArticleKB5034441
Solutions5 methods
Sources2 official
Affected SystemsWindows 10, Windows 11
Quick Fix

Run Windows Update Troubleshooter from SettingsSystemTroubleshootOther troubleshootersWindows Update. If that fails, reset Windows Update components by running net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver in elevated Command Prompt, then restart these services.

Symptoms

  • Windows Update fails with error code 0x80070005
  • Update downloads but fails during installation
  • "Access is denied" message appears during update process
  • Windows Update service stops responding
  • Update history shows failed installations with 0x80070005
  • System cannot download or install security updates

Possible Causes

  • Corrupted Windows Update service permissions
  • Insufficient user account privileges for update installation
  • Damaged Windows Update components or registry entries
  • Third-party antivirus software blocking update processes
  • Corrupted system files affecting update mechanisms
  • Windows Update service dependencies not running properly
1

Run Windows Update Troubleshooter

Windows includes a built-in troubleshooter specifically designed to resolve update issues automatically.

  1. Press Windows + I to open Settings
  2. Navigate to SystemTroubleshootOther troubleshooters
  3. Locate Windows Update and click Run
  4. Wait for the troubleshooter to scan and detect issues
  5. Follow any recommended actions presented by the troubleshooter
  6. Restart your computer when prompted
  7. Test Windows Update by checking for updates manually

Verification: Open SettingsWindows Update and click Check for updates. The error should no longer appear.

2

Reset Windows Update Components

This method manually resets all Windows Update services and clears cached update files.

Warning: Run Command Prompt as Administrator for all commands in this method.
  1. Press Windows + X and select Command Prompt (Admin) or PowerShell (Admin)
  2. Stop Windows Update services by running these commands one by one:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
  1. Clear Windows Update cache by deleting temporary files:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
  1. Restart the Windows Update services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
  1. Reset Windows Update policies:
gpupdate /force
  1. Restart your computer
  2. Test Windows Update functionality

Verification: Run sc query wuauserv to confirm the Windows Update service is running, then check for updates.

3

Run SFC and DISM Scans

System file corruption can cause permission errors during updates. These tools repair corrupted system files.

  1. Open Command Prompt as Administrator
  2. Run System File Checker to scan for corrupted files:
sfc /scannow
  1. Wait for the scan to complete (this may take 15-30 minutes)
  2. If SFC finds issues, run DISM to repair the Windows image:
DISM /Online /Cleanup-Image /RestoreHealth
  1. After DISM completes, run SFC again to ensure all files are repaired:
sfc /scannow
  1. Restart your computer
  2. Attempt Windows Update again
Pro tip: If DISM fails to download repair files, use an offline Windows installation media as the source with DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

Verification: Check the SFC log at C:\Windows\Logs\CBS\CBS.log to confirm repairs were successful.

4

Reset Windows Update Registry Permissions

Incorrect registry permissions can prevent Windows Update from accessing necessary keys.

Warning: Always backup your registry before making changes. Incorrect modifications can cause system instability.
  1. Press Windows + R, type regedit, and press Enter
  2. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
  1. Right-click on the WindowsUpdate key and select Permissions
  2. Click Advanced button
  3. Click Change next to Owner
  4. Type Administrators and click Check Names, then OK
  5. Check Replace owner on subcontainers and objects
  6. Click OK to apply ownership changes
  7. In the Permissions dialog, select Administrators and ensure Full Control is checked
  8. Click AdvancedEnable inheritanceReplace all child object permissions
  9. Repeat steps 2-10 for this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
  1. Close Registry Editor and restart your computer

Verification: Open Registry Editor and confirm you can access the WindowsUpdate keys without permission errors.

5

Create New User Account and Transfer Profile

If the error persists, the issue may be with your user profile permissions. Creating a new administrator account can resolve deep-seated permission problems.

  1. Press Windows + I to open Settings
  2. Navigate to AccountsFamily & other users
  3. Click Add someone else to this PC
  4. Select I don't have this person's sign-in information
  5. Choose Add a user without a Microsoft account
  6. Create a username and password for the new account
  7. After creation, click on the new account and select Change account type
  8. Change the account type to Administrator
  9. Sign out of your current account and log into the new administrator account
  10. Test Windows Update from the new account
  11. If updates work, transfer your files from the old profile:
robocopy "C:\Users\[OldUsername]" "C:\Users\[NewUsername]" /E /XD "AppData" "Application Data" "Local Settings" "My Documents" "NetHood" "PrintHood" "Recent" "SendTo" "Start Menu" "Templates"
  1. Install your applications on the new account
  2. Once everything is working, you can delete the old user account
Pro tip: Before deleting the old account, ensure all important data has been transferred and all applications work correctly.

Verification: Log into the new account and successfully install Windows Updates without encountering error 0x80070005.

Verification

To confirm the Windows Update error 0x80070005 has been resolved:

  1. Open SettingsWindows Update
  2. Click Check for updates
  3. Verify updates download and install without errors
  4. Check Windows Update history for successful installations
  5. Run this PowerShell command to verify update service status:
Get-Service -Name wuauserv, cryptsvc, bits, msiserver | Format-Table Name, Status

All services should show "Running" status. Additionally, check the Windows Update log for any remaining errors by running:

Get-WindowsUpdateLog

Still Having Issues?

If the above methods didn't resolve error 0x80070005, try these advanced alternatives:

Advanced Registry Reset

Use the Windows Update Reset Tool from Microsoft or manually reset additional registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Clean Boot Troubleshooting

Perform a clean boot to eliminate third-party software conflicts. Press Windows + R, type msconfig, select Selective startup, and uncheck Load startup items. Restart and test Windows Update.

Windows Update Medic Service

Ensure the Windows Update Medic Service is running by executing:

sc config WaaSMedicSvc start= auto
net start WaaSMedicSvc

Manual Update Installation

Download updates manually from the Microsoft Update Catalog and install them directly if the automatic process continues to fail.

System Reset Consideration

If all methods fail, consider using Windows Reset while keeping personal files: SettingsSystemRecoveryReset this PC.

Frequently Asked Questions

What does Windows Update error 0x80070005 mean exactly?
Error 0x80070005 translates to "Access Denied" and occurs when Windows Update lacks sufficient permissions to modify system files, registry entries, or access required services during the update installation process. This typically happens due to corrupted permissions, damaged Windows Update components, or interference from security software.
Can third-party antivirus software cause error 0x80070005?
Yes, aggressive antivirus software can block Windows Update processes, causing error 0x80070005. Real-time protection features may prevent updates from modifying system files or accessing registry keys. Temporarily disable your antivirus during updates or add Windows Update processes to the exclusion list. Popular antivirus programs like Norton, McAfee, and Kaspersky have been known to cause this issue.
Is it safe to modify registry permissions for Windows Update?
Modifying registry permissions is generally safe when following proper procedures, but always create a registry backup first. Use the built-in Registry Editor backup feature or create a system restore point. Only modify permissions for specific Windows Update keys, and ensure the Administrators group has Full Control. Incorrect registry modifications can cause system instability or boot failures.
Why does error 0x80070005 keep coming back after fixing it?
Recurring error 0x80070005 often indicates underlying system issues such as corrupted user profiles, persistent malware, failing hard drives, or group policy conflicts in domain environments. Run comprehensive malware scans, check disk health with chkdsk, and verify no conflicting group policies are applied. Consider creating a new user profile if the issue persists only for specific accounts.
How long should I wait for SFC and DISM scans to complete?
SFC scans typically take 15-45 minutes depending on system speed and drive health. DISM RestoreHealth can take 30 minutes to 2 hours, especially when downloading repair files from Windows Update. Don't interrupt these processes as they're critical for system integrity. If scans appear stuck for over 3 hours, restart and try running them in Safe Mode or use offline repair methods.

Which method worked?

Vote to help others

Official Resources

About the Author

Emanuel DE ALMEIDA

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...