How to Fix Error 0x80004005 in Windows 11

The Problem

0x80004005 is E_FAIL — the least helpful error in Windows. It means "something went wrong and the component that failed did not say what". It is not one fault with one fix; it is a blank space where a real error message should have been.

That makes the context the whole diagnosis. The same code means five different things depending on where you saw it, and the fix for one will do nothing for another. Find your situation below and go straight to that step.

| Where you saw it | Go to | |---|---| | Windows Update | Step 2 | | Opening a shared folder on the network | Step 3 | | Extracting a ZIP or moving files | Step 4 | | A virtual machine failing to start | Step 5 | | Everything, intermittently | Steps 6–8 |

Symptoms

• Windows Update fails with 0x80004005 and no further detail.
• "Unspecified error" when opening a network share or mapped drive.
• Extracting an archive or renaming a folder fails with the code.
• VirtualBox or VMware refuses to start a VM after a Windows update.
• Outlook cannot send or receive, reporting the same code.

Step 1: Get the Real Error From the Logs

Because the code itself says nothing, the log entry beside it usually does.

1. Windows + R → eventvwr.msc → Enter.
2. Open Windows Logs → Application and System, and sort by time to find the entry matching when the failure occurred.
3. The event beside the failure normally names the actual component, file, or permission at fault.
4. Full method: how to use Event Viewer to find why your PC crashed.

Step 2: Fix It for Windows Update

1. Right-click Start → Terminal (Admin) and reset the update cache:

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

2. Reboot and retry the update.
3. Run the built-in troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.
4. Disconnect any VPN and turn off metered connection settings before retrying.
5. More: fix Windows 11 update errors and fix Windows Update stuck.

Step 3: Fix It for Network Shares

Modern Windows disables the old, insecure sharing protocol, and older NAS boxes and routers still require it. That mismatch produces 0x80004005.

1. Turn discovery on first: Settings → Network & internet → Advanced network settings → Advanced sharing settings. Enable Network discovery and File and printer sharing for the Private profile.
2. Confirm the network is set to Private, not Public — sharing is blocked outright on Public.
3. If the share is on an older NAS or router, enable the legacy client: Windows + R → optionalfeatures → tick SMB 1.0/CIFS Client only. Leave Server unticked.
4. ⚠️ SMB 1.0 is an obsolete protocol with known remote vulnerabilities. Enable the client only if the device genuinely cannot do better, keep it off any untrusted network, and check the device maker for firmware that supports SMB2 or later — that is the correct fix.
5. Test with the IP address rather than the name: Windows + R → \\192.168.1.50. Success by IP but not by name is a name-resolution problem, not a permissions one.
6. Related: share files between Windows PCs on the same network.

Step 4: Fix It for File and Archive Operations

1. Extract the archive with 7-Zip rather than File Explorer's built-in handler, which reports this code for any problem it meets.
2. Copy the archive to a local drive first — extracting straight from a network share or a USB stick is a frequent trigger.
3. Check the destination path length. Paths beyond 260 characters fail with unhelpful codes; extract to C:\temp to test.
4. Confirm you can write to the destination: fix access denied and "you need permission".
5. If the file itself is damaged, the code is genuine — see fix error 0x80070570.

Step 5: Fix It for Virtual Machines

VirtualBox and VMware conflict with the Windows hypervisor, and the collision surfaces as 0x80004005.

1. Check whether Hyper-V or a related feature is on: Windows + R → optionalfeatures → look at Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform.
2. Memory integrity also claims the hypervisor — Windows Security → Device security → Core isolation details → turn Memory integrity off and reboot.
3. Update VirtualBox or VMware to a current version; recent releases coexist with Hyper-V far better than older ones did.
4. Confirm hardware virtualization is enabled in firmware: how to enable virtualization (VT-x / AMD-V) in the BIOS.
5. If you want to use Hyper-V instead: how to enable Hyper-V in Windows 11.

Step 6: Repair System Files

1. In Terminal (Admin):

   sfc /scannow
   

2. Then:

   DISM /Online /Cleanup-Image /RestoreHealth
   

3. Reboot and run sfc /scannow again.
4. Detail: how to run SFC and DISM. If DISM fails too, see fix DISM error 0x800f081f.

Step 7: Rule Out Security Software

1. Fully exit any third-party antivirus, or disable its real-time protection, and retry the failing action.
2. Check Windows Security → Virus & threat protection → Manage ransomware protection and turn Controlled folder access off temporarily — it blocks writes to Documents, Pictures, and Desktop and reports vague errors when it does.
3. If disabling helps, add an exclusion rather than leaving protection off.
4. Scan for malware while you are here: remove a virus or malware from Windows 11.

Step 8: Clear the Temp Folder and Test a New Profile

1. Windows + R → %temp% → Enter, select all, and delete. Skip anything in use.
2. Empty the Recycle Bin and reboot.
3. Create a fresh local administrator account: Settings → Accounts → Other users → Add account → I don't have this person's sign-in information → Add a user without a Microsoft account.
4. Sign in as that user and retry. If it works there, your profile is damaged: fix "signed in with a temporary profile".
5. Free up space if the drive is nearly full — many 0x80004005 failures are just a full disk: free up disk space when the C drive is full.

What Not to Do

• Don't leave SMB 1.0 enabled once you have proven it was the cause. Fix the device's firmware or replace it, and turn the feature back off.
• Don't apply every step in this guide at once. The code means five different things — identify your context first, or you will change settings that were never the problem.
• Don't turn off memory integrity permanently unless a virtual machine genuinely requires it. It is a real security protection.
• Don't trust "0x80004005 fixer" downloads. Every genuine fix here uses tools already in Windows.

Still Not Working?

If the error follows a brand new user profile, survives SFC and DISM, and appears in more than one context, an in-place repair install replaces every system component while keeping files and apps: reinstall Windows without losing data.

Related: fix error 0x80070005, fix "can't delete file in use", and fix OneDrive sync issues.