How to Fix Windows Error Code 0x80004005 (Complete Guide – 2026)

Windows · System Errors · Updated August 2026

Windows shows this one as “Error 0x80004005 — Unspecified error”, which tells you nothing at all. It is a generic failure code, and the same eight digits appear when an update fails, when a shared folder refuses to open, when a zip file will not extract, and when a virtual machine will not start.

Because the code is generic, the fastest route is not to work through every possible repair. It is to notice where the error appears, then apply the two or three fixes that match that situation. This guide is arranged that way.

⚡ The Short Answer

1. Error during a Windows update? Reset the update components. Fix 3
2. Error opening a shared folder? Check permissions, then the SMB client. Fix 5 and Fix 9
3. Error extracting a zip or rar? The archive is usually damaged or in an unsupported format. Fix 6
4. Error anywhere else? Repair the system files first. Fix 4

⚠ Two things you will see recommended elsewhere — do not do them. Never enable SMB 1.0 to reach an old network device. Microsoft removed it because it is the protocol ransomware families such as WannaCry spread through, and turning it back on exposes the whole machine. And do not switch your antivirus off to test: add a specific exclusion instead, as shown in Fix 7.

Where Is The Error Appearing?

Pick the line that matches what you were doing when the code appeared, and start there.

SITUATION A During Windows Update

An update download or install fails and rolls back. Go to Fix 2, then Fix 3, then Fix 4.

SITUATION B Opening a shared folder, NAS or network printer

The most common cause of all. Go to Fix 5, then Fix 8 and Fix 9.

SITUATION C Extracting a zip or rar file

Almost always the archive itself, not Windows. Go straight to Fix 6.

SITUATION D Copying files, launching an app, or starting a virtual machine

Usually damaged system files or a security block. Go to Fix 4, then Fix 7.

Table of Contents

1. Where is the error appearing?
2. Restart and note the exact wording
3. Run the Windows Update troubleshooter
4. Reset the Windows Update components
5. Repair system files with SFC and DISM
6. Fix folder and share permissions
7. Deal with a damaged or unsupported archive
8. Add an antivirus exclusion instead of disabling it
9. Update the network adapter driver
10. Turn on the SMB client and network discovery safely
11. Clean boot, then System Restore
12. Quick reference — all 10 fixes
13. Mistakes that make it worse
14. The order to follow
15. Frequently asked questions

The 10 Fixes, In Order

1Restart and note the exact wording

MEDIUM IMPACT DO THIS FIRST 5 min NO DATA LOSS

A restart clears file locks and half-finished operations, and a genuine number of 0x80004005 sightings never come back after one. More importantly, the restart gives you a clean run at reproducing the error so you can record exactly what triggers it.

Steps

1. Choose Restart from the Start menu — not Shut down. With fast startup enabled, shutting down does not fully reload Windows, but a restart does.
2. Try the same action again and write down the full message, including any file or folder path it mentions.
3. Note which of the four situations above it matches. That decides which fix you go to next.

✅ Verify it worked: either the action completes normally, or you now know exactly which situation you are in.

2Run the Windows Update troubleshooter

HIGH IMPACT SITUATION A 10 min NO DATA LOSS

Windows has a built-in repair routine for update failures that resets the relevant services and clears stuck downloads. It is not a magic wand, but it costs ten minutes and it resolves a fair share of update-time 0x80004005 errors on its own.

Steps

1. Windows 11: go to Settings → System → Troubleshoot → Other troubleshooters.
2. Windows 10: go to Settings → Update & Security → Troubleshoot → Additional troubleshooters.
3. Find Windows Update and click Run.
4. Let it finish, restart the PC, then check for updates again.

✅ Verify it worked: the update downloads and installs to completion instead of rolling back.

3Reset the Windows Update components

HIGH IMPACT SITUATION A 15 min

If the troubleshooter did not clear it, the update cache itself is damaged. These commands stop the update services, rename the two folders Windows stores downloads in, and start the services again. Windows rebuilds both folders from scratch on the next check, so nothing is permanently deleted.

Steps

1. Press Win + S, type cmd, right-click Command Prompt and choose Run as administrator.
2. Enter each of these lines in turn, pressing Enter after each one.

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

3. Restart the PC and check for updates again.

Note: if a ren line reports that access is denied, one of the services is still running. Repeat the four net stop lines and try again.

✅ Verify it worked: the update now downloads from zero and installs without the error.

4Repair system files with SFC and DISM

HIGH IMPACT 30 min NO DATA LOSS

Damaged Windows system files produce this code in every situation, which is why it is worth running these two tools regardless of where the error shows up. Run them in this order: if SFC cannot repair everything, DISM restores the component store that SFC pulls its replacement files from, and SFC then succeeds on the second pass.

Steps

1. Open Command Prompt as administrator.
2. Run the first command and let it reach 100 percent without closing the window.

sfc /scannow

3. If it reports files it could not repair, run this next. It needs an internet connection and can take twenty minutes.

DISM /Online /Cleanup-Image /RestoreHealth

4. When DISM finishes, run sfc /scannow once more, then restart.

✅ Verify it worked: SFC finishes with either no integrity violations found, or a message that it repaired them successfully.

5Fix folder and share permissions

HIGH IMPACT SITUATION B 10 min

When the error appears on a shared folder, permissions are the first thing to check. Windows shares have two separate layers — the share permissions and the NTFS security permissions — and access is only granted when both allow it. A folder that looks correct on one tab can still be blocked by the other.

Steps

1. On the computer that hosts the folder, right-click it and choose Properties.
2. Open the Sharing tab, click Advanced Sharing → Permissions, and confirm your account or group is listed with the access it needs.
3. Now open the Security tab and check the same account there. If it is missing, click Edit → Add, type the account name and grant the access required.
4. Click Apply, then try reaching the folder from the other computer again.

⚠ Grant only what is needed. Giving Everyone full control does clear the error, and it also opens the folder to every device on the network. Add your specific user account instead.

✅ Verify it worked: the shared folder opens from the other machine without a prompt or an error.

6Deal with a damaged or unsupported archive

HIGH IMPACT SITUATION C 10 min

If the code only appears while extracting, Windows itself is almost certainly fine. The built-in extractor handles standard zip files and nothing else, and it also fails on any archive that arrived incomplete — which is very common with large downloads.

Steps

1. Check the file size against the size listed on the page you downloaded it from. A mismatch means the download was truncated — download it again.
2. Right-click the file, choose Properties, and if you see an Unblock checkbox near the bottom of the General tab, tick it and click Apply. Windows blocks archives from the internet and that alone can produce this error.
3. Move the archive to a short local path such as the root of the C drive. Very long paths and network locations both cause extraction failures.
4. If the file is a rar, 7z or any other non-zip format, the built-in extractor cannot open it at all. Use an archive utility that supports that format.

✅ Verify it worked: the archive extracts fully with no error and the extracted files open normally.

7Add an antivirus exclusion instead of disabling it

MEDIUM IMPACT SITUATION D 10 min

Security software genuinely does block operations and return this code, particularly around virtual machine files and installers. The usual advice is to switch protection off and see what happens. Do not do that — an unprotected machine on the internet is a real risk, and people forget to turn it back on. A targeted exclusion tests the same theory safely.

Steps

1. Open Windows Security → Virus & threat protection.
2. Under Virus & threat protection settings, click Manage settings.
3. Scroll to Exclusions and click Add or remove exclusions.
4. Add only the specific folder the failing operation uses — for example the folder holding your virtual machine files.
5. Try the action again. If it now works, you have found the cause without ever lowering your defences.
6. If you use third-party security software, the same option exists in its settings, usually under exclusions or exceptions.

✅ Verify it worked: the operation completes with the exclusion in place, and real-time protection is still switched on.

8Update the network adapter driver

MEDIUM IMPACT SITUATION B 10 min

An outdated or mismatched network driver disrupts the file-sharing protocol underneath, and the failure surfaces as this same generic code. This is worth doing after permissions but before anything more involved.

Steps

1. Press Win + X and choose Device Manager.
2. Expand Network adapters and right-click the adapter you actually connect through.
3. Choose Update driver → Search automatically for drivers.
4. If the trouble started right after a driver update, open the adapter’s Properties → Driver tab and use Roll Back Driver instead.
5. Restart the PC afterwards.

✅ Verify it worked: the driver date has changed and network locations open normally.

9Turn on the SMB client and network discovery safely

HIGH IMPACT SITUATION B 10 min

Shared folders travel over a protocol called SMB. Windows 10 and 11 ship with the modern versions enabled, but network discovery is often switched off, and a machine that cannot see the network path returns this error. Fix that first.

⚠ Never enable SMB 1.0. You will find guides telling you to tick SMB 1.0/CIFS File Sharing Support in Windows Features to reach an old NAS or printer. Microsoft disabled that protocol because it has no meaningful security and is the route ransomware such as WannaCry used to spread across networks. If a device truly cannot speak anything newer, update its firmware, or connect it through a modern device rather than reopening that door.

Steps

1. Go to Settings → Network & internet → Advanced network settings → Advanced sharing settings.
2. For your Private networks profile, turn on Network discovery and File and printer sharing. Leave the Public profile switched off.
3. Press Win + S, open Services, and confirm Function Discovery Resource Publication and Function Discovery Provider Host are running.
4. Open Turn Windows features on or off and confirm SMB Direct is available. Leave the SMB 1.0 entry unticked.
5. Restart and try the share again.

✅ Verify it worked: the other computer appears under Network in File Explorer and its shared folders open.

10Clean boot, then System Restore

MEDIUM IMPACT LAST RESORT 45 min

A clean boot tells you whether installed software is responsible, and System Restore undoes whatever change introduced the problem. Try them in that order, because a clean boot identifies the cause while a restore only hides it.

Steps

1. Press Win + R, type msconfig and press Enter.
2. On the Services tab, tick Hide all Microsoft services, then click Disable all and restart.
3. Reproduce the error. If it is gone, re-enable the services in small groups until it returns to identify the culprit, then undo the msconfig change.
4. If the error persists even in a clean boot, press Win + R, type rstrui and choose a restore point dated before the trouble began.
5. If a restore point is not available and nothing else has worked, Settings → System → Recovery → Reset this PC with the Keep my files option is the final step.

⚠ Remember to undo the clean boot. Go back into msconfig and re-enable the services, or your antivirus, printer and backup software will stay switched off.

✅ Verify it worked: the failing action completes normally and the error does not return over the following days.

Quick Reference — All 10 Fixes

#	Fix	Best for	Time
1	Restart and note the wording	Everyone — start here	5 min
2	Windows Update troubleshooter	Situation A	10 min
3	Reset update components	Situation A	15 min
4	SFC then DISM	Any situation	30 min
5	Folder and share permissions	Situation B	10 min
6	Damaged or unsupported archive	Situation C	10 min
7	Antivirus exclusion	Situation D	10 min
8	Network adapter driver	Situation B	10 min
9	SMB client and network discovery	Situation B	10 min
10	Clean boot, then System Restore	Nothing else worked	45 min

Mistakes That Make It Worse

• Enabling SMB 1.0. The single worst piece of advice attached to this error code. It does sometimes make an old device reachable, and it leaves the machine open to attacks that modern Windows was specifically hardened against.
• Turning antivirus off to test. Use an exclusion. It proves exactly the same thing and leaves you protected.
• Granting Everyone full control on a share. It clears the error and hands every device on the network unrestricted access to those files.
• Applying registry edits copied from a forum. Several tweaks circulated for this error weaken the security model of remote connections. If a guide does not explain what a registry value changes, do not add it.
• Reinstalling Windows first. This error is rarely deep enough to need it, and a reinstall costs a day. Work through the list in order instead.

The Order to Follow

1. Restart and identify the situation. This decides everything that follows. Fix 1
2. Update failing? Troubleshooter, then reset the update components. Fix 2 then Fix 3
3. Shared folder failing? Permissions, then driver, then network discovery. Fix 5, Fix 8, Fix 9
4. Extraction failing? Check and unblock the archive. Fix 6
5. Something else failing? Repair system files, then try an exclusion. Fix 4 then Fix 7
6. Still stuck? Clean boot to find the cause, then restore. Fix 10

Frequently Asked Questions

What does error 0x80004005 actually mean?

It is a generic failure code that Windows returns when an operation did not succeed and no more specific reason was reported. That is why the message says “unspecified error”. The code itself tells you nothing about the cause — where it appeared does.

Will any of these fixes delete my files?

No. Every fix from 1 to 9 leaves personal files completely untouched, including renaming the update folders in Fix 3, which only affects Windows update caches. Only the Reset option mentioned at the end of Fix 10 changes the installation, and even that has a Keep my files setting.

Should I enable SMB 1.0 to reach my old NAS?

No. Microsoft disabled it because it offers no real security and was the mechanism ransomware used to spread across networks. Check whether the device has a firmware update that supports a newer version, and if it does not, treat that device as end of life rather than weakening the PC to accommodate it.

Why does the error only happen sometimes?

Because it is not one fault. The same code covers update failures, permission denials, security blocks and damaged archives, so it can appear in one task on Monday and a completely unrelated one on Friday.

Is it a virus?

Usually not. It is far more often a permission or a damaged-file problem. That said, malware can corrupt the system files that produce it, so a full scan with Windows Security is a reasonable thing to run alongside Fix 4.

I get it in VirtualBox or Hyper-V. Same fixes?

Mostly Fix 7. Virtual machine disk files are large and constantly written to, and security software frequently locks them mid-operation. Add the folder holding the virtual disks as an exclusion, and make sure hardware virtualisation is enabled in the BIOS.

SFC says it found corrupt files but could not fix them. What now?

That is exactly the situation DISM is designed for. Run the RestoreHealth command in Fix 4 with an active internet connection, then run SFC again. The second pass usually succeeds because DISM has repaired the source files SFC copies from.

How do I stop it coming back?

Install Windows updates as they arrive rather than deferring them for months, keep the network driver current, avoid granting broad share permissions, and leave real-time protection enabled with narrow exclusions where they are genuinely needed.

📌 Another Windows error to untangle?

TechFix Radar has clear, step-by-step fixes for Windows, laptops, Android and iPhone — written to be followed, not skimmed.

Start here Free tools

Related Fixes

• Why Windows Updates Fail and How to Fix Them
• Windows 11 24H2 Slow After Update? Proven Fixes
• Windows 11 Slow Performance? Step-by-Step Fixes
• Laptop Frozen But Mouse Moves? Fixes That Work