Fix error 0x80004005
0x80004005 is E_FAIL, listed by Microsoft as unspecified failure. It is a catch-all: the component failed but did not return a more exact code. The fix depends on where you see it. For updates run the Windows Update troubleshooter, DISM and SFC. For files, extract with File Explorer or check folder access. For shared folders, check network sharing settings.
Checked November 10, 2026 against the manufacturer's own pages.
The short version
What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.
Official files only, nothing bundled
Step by step
Write down exactly what you were doing
E_FAIL carries no detail, so the task is your best clue. Note whether it happened in Windows Update, while extracting an archive, while copying to a network folder or while starting a virtual machine, then follow the matching step below.
For Windows Update: troubleshooter, DISM and SFC
Go to Settings, System, Troubleshoot, Other troubleshooters and select Run next to Windows Update. Then in an elevated Terminal run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow, and restart.
For zip files: extract instead of opening
Right-click the archive and pick Extract All, then work on the extracted copy. If the zip came from the internet, right-click it, Properties, and tick Unblock if that option is shown. Password protected archives may need the tool that made them.
For network folders: check sharing settings
Open Settings, Network and internet, Advanced network settings, Advanced sharing settings. For your current profile, turn on Network discovery and File and printer sharing. Make sure both PCs are on a Private network profile.
Test with a clean boot
Run msconfig, hide all Microsoft services, disable the rest and disable startup apps in Task Manager. Restart and retry. If the error stops, a background tool such as a third-party security suite or sync client is involved.
Check the event logs
Open Event Viewer, Windows Logs, Application and System. Look for an Error at the same minute. Its source and text usually name the component that really failed, which is the detail E_FAIL hides.
Faster option: let a PC tool do the clean-up
The steps above fix this error. Errors like this often come back on a PC full of junk files, broken registry entries and leftovers from removed programs. A maintenance tool clears those in one scan.
Scan and clean up Windows
Finds junk files, invalid registry entries, startup slowdowns and privacy traces, then fixes them in one click.
Auslogics BoostSpeed 14 · Free version · Windows 11, 10, 8, 7 · 30-day refund on Pro
A generic code with many sources
0x80004005 is one of the oldest codes in Windows. In Microsoft’s list of common HRESULT values it sits next to E_ACCESSDENIED and E_INVALIDARG, but its description says the least: unspecified failure. Any Windows component, driver or app can return it. Because of that, two people with the same code can have completely different problems, which is why online fixes for it often seem to contradict each other.
Using the context to find the cause
The surrounding task narrows it down fast. A failing update points at the update cache or component store. A zip that will not open points at the archive, its download block or its encryption. A share that will not open points at network discovery, the network profile or the sign-in used for that PC. A virtual machine that will not start points at the virtualization software and its drivers. Event Viewer usually fills in the rest, since the component that failed often logs a clearer message there.
A less common cause: a full or nearly full system drive
Some installers and updates return a generic failure instead of a disk space error when they cannot create temporary files. Open Settings, System, Storage. If the C: drive is almost full, use Cleanup recommendations or Temporary files to free space, then retry the task.
Questions
Why is 0x80004005 called unspecified error?
Microsoft's HRESULT tables define E_FAIL as unspecified failure. Programs return it when something went wrong but they have no more specific code to give.
Is 0x80004005 a virus?
No. It is a generic error code. If you suspect malware for other reasons, run a full scan in Windows Security, Virus and threat protection.
Does 0x80004005 mean I lack permission?
Sometimes. Access problems often return their own code, 0x80070005, but some programs report them as a generic failure. If the error appears only in one folder, check that folder's Security tab.
Why does an upgrade to a new Windows version fail with 0x80004005?
The setup program hit a failure it did not classify. Repairing system files, freeing disk space, unplugging extra USB drives and testing with a clean boot cover the usual reasons.