Forum Discussion
Windows Error 0x80004005: Clear Update and Access Loops
Sharing a quick troubleshooting note for anyone hitting Windows error 0x80004005 during cumulative updates or file transfers on Windows 11. Because 0x80004005 acts as a generic access denied code, it usually means the update engine is stuck reading corrupted cache files or missing script registrations.
On my Windows 11 test PC, flushing the update cache cleared 0x80004005 right away. Open Command Prompt as administrator and stop the update services by running:
net stop wuauserv
net stop bits
Next, press Windows Key + R, open C:\Windows\SoftwareDistribution, and delete the contents inside. Once the folder is clear, go back to your Command Prompt window and restart the services by running:
net start wuauserv
net start bits
If Windows Update still stalls on 0x80004005 after clearing that folder, re-register the system script libraries from an elevated Command Prompt by running:
regsvr32 jscript.dll
regsvr32 vbscript.dll
Close the command window and check for updates again. I kept the full replication steps and environment notes from that test run over at https://syserrorlog.com/windows-error-0x80004005/ if anyone wants the complete breakdown. Let me know which Windows 11 build you are running or if 0x80004005 is showing up on a shared network drive instead.
3 Replies
- KyleS_85226Copper Contributor
Glad you have rediscovered this solution - but FYI, this fix (and ones like it) have been around since the Windows 7 days at least, maybe XP even. Still, it is a good low-risk/impact first step when WU isn't working properly.
- maskwillIron Contributor
Good troubleshooting approach! Clearing the SoftwareDistribution cache often resolves Windows Update error 0x80004005.
A few additional recommendations:
Run DISM /Online /Cleanup-Image /RestoreHealth.
Run sfc /scannow to repair corrupted system files.
Restart Windows and check for updates again.
If the error occurs during file transfers, also check folder permissions and network access.
Note: Re-registering jscript.dll and vbscript.dll is not usually necessary for this error.
Always back up important data before troubleshooting system components.
- syserrorlogIron Contributor
Appreciate the input! Good call on running DISM and sfc /scannow if the update components themselves are damaged. On my test machine, flushing SoftwareDistribution handled the update loop, though I still keep the jscript and vbscript re-registration handy for older Windows builds or stubborn installer scripts where 0x80004005 refuses to budge.