How to Fix Error 0x80004005 in Windows 11

Error 0x80004005 means an operation failed without returning a more specific reason. Windows may show it during an update, file extraction, network-share connection, virtual-machine startup, or application task. The same code can therefore represent completely different problems.

The useful clue is not the code alone. It is where the error appeared and what you were doing immediately before it. Match that situation to the relevant section below instead of applying every repair on the page.

Start With the Failed Operation

Where the error appears	Most likely area	Start with
Windows Update or an upgrade	Update cache, storage, driver, or compatibility problem	Run the Windows Update troubleshooter
Copying or moving a file	Permissions, path length, destination, or storage	Try a short local path
Extracting a ZIP archive	Damaged download, encryption, or unsupported archive method	Download again and extract locally
Opening a shared folder or NAS	Credentials, permissions, name resolution, or SMB compatibility	Test the share by IP address
Starting a virtual machine	Saved state, version mismatch, virtualization, or VM configuration	Read the VM program’s detailed log
Outlook or one application	Profile, add-in, local data, or application fault	Update and repair that application
Several unrelated Windows features	Windows component corruption	Run DISM followed by SFC

Record the full message, affected file or update number, application name, and time of failure. Restart Windows and repeat the exact action once. A restart can clear a locked file or stuck service, but a recurring error needs a context-specific repair.

Fix 0x80004005 During Windows Update

Start with Windows’ automated update diagnostics:

1. Open Settings > System > Troubleshoot.
2. Select Other troubleshooters.
3. Find Windows Update and select Run.
4. Apply the recommended correction.
5. Restart the computer and check for updates again.

Microsoft includes restarting, checking available space, disconnecting unnecessary hardware, and retrying among its Windows upgrade and installation error guidance.

For a feature upgrade, disconnect nonessential USB drives, memory cards, printers, docks, and adapters. Keep the keyboard, mouse, display, and internet connection available. Confirm that the Windows drive has adequate free space under Settings > System > Storage.

Rebuild the Update Cache Only When the Same Update Keeps Failing

A repeatedly corrupted download can keep producing the same error. Open Terminal (Admin) and run these commands one at a time:

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

Restart Windows and check again. Renaming the folders allows Windows to create clean replacements while leaving the old copies available temporarily. Do not force-delete an update folder while its service is using it.

The dedicated Windows Update cache guide explains what each folder contains and what to do when a service refuses to stop.

Use a clean boot only when the update succeeds with non-Microsoft services disabled or when a specific background program is suspected. Do not leave antivirus, VPN, or startup services disabled permanently after testing.

Repair Windows Components When the Error Is System-Wide

DISM and System File Checker are appropriate when 0x80004005 affects several Windows features, follows an interrupted system update, or appears with other signs of component corruption. They are unlikely to repair one damaged ZIP file or an incorrect network password.

Right-click Start, select Terminal (Admin), and run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for DISM to finish, then run:

sfc /scannow

Microsoft’s system-file repair instructions specify this DISM-before-SFC order. Restart when both commands finish.

When SFC reports that Windows Resource Protection could not perform the requested operation, use the Windows Resource Protection error guide rather than running the same scan repeatedly.

Fix the Error When Copying or Moving Files

The wording “an unexpected error is keeping you from copying the file” points toward the source item, destination, permissions, or storage rather than Windows Update.

Try these checks in order:

1. Create C:\Temp and copy the item there.
2. Shorten deeply nested folder and file names.
3. Confirm that the destination has enough free space and is writable.
4. Right-click the file, select Properties, and use Unblock when the option appears and the source is trusted.
5. Check the Security tab and confirm that your account can read the source and write to the destination.
6. Restart Windows Explorer through Task Manager if all file operations have become stuck.

Do not grant Everyone full control over a personal or system folder to bypass one error. On a work or school PC, access may be intentionally restricted by policy.

For an external drive, try another cable or USB port. Back up important data when the drive disconnects, becomes unusually slow, or reports file-system errors. A failing drive should be treated as a storage problem, not repaired with repeated permission changes.

Fix 0x80004005 While Extracting a ZIP File

Download the archive again from its original trusted source and compare its size or published checksum when available. Move it to a short local path such as C:\Temp before extracting it.

Windows File Explorer does not support every compression and encryption method. A password-protected archive may require a reputable archive utility from its official publisher. Changing .rar or .7z to .zip does not convert the archive.

Create a small test ZIP containing a harmless text file. When the test archive extracts successfully, the original archive, password method, or download is the likely cause. When every ZIP fails, check storage and run the Windows component repairs above.

Avoid uploading private archives to random online extraction sites. That gives the service access to their contents.

Fix the Error When Opening a Network Share

Start by testing the same share through its local IP address:

\\192.168.1.20\ShareName

Replace the example with the server’s actual address and share name. When the IP path works but \\ComputerName\ShareName fails, investigate name resolution rather than changing permissions.

Make sure both devices are connected to the intended private network. Temporarily disconnect a VPN that routes local traffic elsewhere. Under Settings > Network & internet > Advanced network settings > Advanced sharing settings, enable Network discovery and File and printer sharing only for the trusted private profile.

Remove a stale saved login without deleting unrelated credentials:

1. Open Control Panel > User Accounts > Credential Manager.
2. Select Windows Credentials.
3. Expand the entry for the affected computer or NAS.
4. Select Remove.
5. Reconnect to the share and enter the correct username and password.

Windows folder access depends on both the share permission and the folder’s Security permission. A user allowed by one layer can still be denied by the other. The Windows Samba share setup guide covers both permission layers.

Do not enable SMB 1.0 as a routine fix. Update the NAS or server to support SMB2 or SMB3. Equipment that requires SMB1 creates a separate security decision and should not be exposed to an untrusted network.

Handle E_FAIL 0x80004005 in a Virtual Machine

VirtualBox and other virtualization programs may display E_FAIL (0x80004005) when the VM cannot start. The code is still generic, so open the application’s detailed log and read the lines immediately before and after it.

Check these likely causes:

• The virtualization application does not support the current Windows build.
• An extension pack does not match the main application’s exact version.
• The VM has a damaged saved state.
• Hardware virtualization is disabled in UEFI or BIOS.
• The VM configuration references a missing disk, snapshot, or inaccessible folder.
• Another hypervisor or Windows security feature conflicts with that specific software version.

Update the virtualization software from its official publisher. Shut down the VM cleanly when possible. Discarding a saved state removes unsaved work inside that suspended session, so do it only after accepting that loss.

Do not disable Hyper-V, Memory Integrity, or virtualization-based security simply because an old tutorial lists it. First confirm that the current virtualization product documents a conflict with the enabled feature.

Fix the Code in Outlook or Another Application

An error during Outlook Send/Receive belongs to Outlook, the mailbox, profile, add-ins, or a local data file. It is not a reason to reset Windows Update.

Start Outlook in Safe Mode with:

outlook.exe /safe

When the problem disappears, disable recently added COM add-ins one at a time. Install Office updates and run Quick Repair from Settings > Apps > Installed apps > Microsoft 365 > Modify. Back up locally stored POP mail and archive files before removing a profile or data file.

For another application, update it, test without optional plug-ins, use its repair option, and inspect its own log. A program may translate several internal failures into the same generic Windows code.

Use Event Viewer to Find the Missing Detail

Event Viewer can connect a generic pop-up to the service or application that actually failed.

1. Right-click Start and select Event Viewer.
2. Open Windows Logs > Application and System.
3. Select Filter Current Log.
4. Include Critical, Error, and Warning events.
5. Match the event time to the failed operation.

Focus on the event source, faulting application, filename, and any additional error code recorded at the same time. An unrelated warning from hours earlier is not evidence of the cause.

For Windows Update, also check Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational.

Reserve Windows Repair or Reset for Broad Failures

An in-place repair is reasonable when the error affects several Windows components and remains after DISM, SFC, update repair, and a clean boot. On supported systems, check Settings > System > Recovery > Fix problems using Windows Update > Reinstall now.

The current-version Windows repair guide explains the reinstall option that preserves personal files, installed applications, and most settings.

Resetting Windows is not an appropriate response to one inaccessible NAS, corrupted archive, broken Outlook profile, or failing external drive. A reset cannot repair something outside the Windows installation.

Avoid Generic Fixes That Add Risk

• Do not download individual DLL files from third-party DLL sites.
• Do not run a registry cleaner or delete unrelated Registry entries.
• Do not give Everyone full control over system or personal folders.
• Do not enable SMB1 without a documented legacy requirement and a security plan.
• Do not disable antivirus or Windows security features permanently.
• Do not reset Windows before identifying whether the failure belongs to Windows.

Error 0x80004005 becomes manageable once it is treated as a symptom rather than a diagnosis. Repair the feature that failed, verify the result by repeating the same operation, and stop when that branch is working. System-wide commands belong only to system-wide symptoms.