0x80004005 Error

Question

My system displays a 0x80004005 error message when I reboot the system or attempt to install a new application,

Answer 1

Hi,

It is an unspecfied error as per the error code. Let us see if an application is behind it.

Does the issue persist in a clean boot state?

Type “msconfig” (without quotes) and press Enter.

In the System Configuration window, select the Services tab.

Check the box next to “Hide all Microsoft services”. Ensure you do it carefully, and not disable all Microsoft services.

Click on “Disable all”.

Select the Startup tab and click on “Open Task Manager”.

In the Task Manager window, select each startup item and click on “Disable”.

Close Task Manager and click on OK in the System Configuration window.

Restart your computer.

More details: https://aka.ms/wincleanboot

I’m eager to hear back and work together to find a solution.

Answer 2

Error code 0x80004005 is a generic Windows error that means “unspecified error.” Because it is generic, the cause must be found in the logs around the time of the failure.

For application installation failures showing 0x80004005 on Windows, use this approach:

1. Check installation logs
   • Locate the installer’s own log (for example, setup logs under the application’s folder or under %ProgramData% or %Temp%).
   • Look for the first failure before 0x80004005 to identify the real cause (missing file, access denied, etc.).
2. Review Windows and app logs
   • Open Event Viewer (eventvwr.msc).
   • Check Windows Logs → Application and System around the time of the reboot or install attempt.
   • Correlate any error or warning just before the 0x80004005 entry to see what component is failing.
3. Use Configuration Manager / app logs if managed
   • If the app is being deployed via Microsoft Endpoint Configuration Manager (ConfigMgr/Intune), review the Configuration Manager application logs on the client and merge them with the installer logs to see what happened immediately before 0x80004005.
4. Use Process Monitor for deeper diagnosis
   • If the missing or failing resource is unclear, run Process Monitor while reproducing the error.
   • Filter on the installer process and look for operations that fail just before the error (for example, ACCESS DENIED, NAME NOT FOUND, or SHARING VIOLATION). This will show which file, registry key, or resource is causing the problem.
5. Fix common underlying causes
   • Permissions / access denied: If Process Monitor or logs show access denied, adjust NTFS or registry permissions (for example, using icacls) so the installing account has the required rights.
   • Missing or corrupted components: Some installers require core Windows components such as .NET, Visual C++ runtimes, or DirectX. Make sure Windows is fully updated so these components are installed correctly.
   • Corrupted user profile: If the error appears only under one user account, test with a new Windows user profile. If the new profile works, the original profile may be corrupted.
6. Keep Windows updated
   • Run Windows Update and install all important updates. This ensures required frameworks and system components are present and not corrupted, which can prevent setup failures.

If the error also appears during reboot (outside of app installs), the same principles apply: use Event Viewer to find the first failing service or driver before 0x80004005, then troubleshoot that specific component.

---

References:

• Application installation common error codes reference
• Error message when you install a Microsoft game or mapping program