The 0x80004005 error translates as an unspecified error and generally occurs when the user cannot access the shared folder, drives, and virtual machines, and when Windows updates cannot be installed. The solution depends on the origin and origin of the error message. Since the error does not specify what the problem is, even in Microsoft books, it is defined as “error number.”
With the help of this manual, you should be able to solve the problem. I have compiled working solutions for a variety of scenarios and have included them in this post. Read the following sections and then use the solution that applies to your situation.
- Repair corrupt system files
- Error 0x80004005 in a VirtualBox
- Error 0x80004005 when accessing a Shared Drive
- Error 0x80004005 when installing Windows 7 or Windows Server 2008 R2 SP1
- E_FAIL (0x80004005) when configuring VirtualBox in Ubuntu
- Cannot log in to the virtual machine
- Uninstall Microsoft 6to4
- Error 0x80004005 when extracting files
Repair corrupt system files
The system file checker (SFC) tool is used to check for corrupt or missing Windows system files and restore them to their previous states.
- SFC is a command based tool so you need command prompt to run it.
- Open the command prompt by searching for cmd in the start menu, right-click it, and select run as administrator.
- Now in command prompt and enter the following command: SFC /scannow
- Press enter and it will start scanning for corrupt windows files.
- It will automatically fix corrupt files if found any. If you don’t find any corrupt files then move to the next method.
Error 0x80004005 in a VirtualBox
It is usually the registry key that is causing problems.
- Hold the Windows key and press R. In the run window type Regedit and click OK.
- Go to the following log pathway:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ AppCompatFlags\Layers
- “C: \Program Files\Oracle\VirtualBox\VirtualBox.exe” =”DISABLEUSERCALLBACKEXCEPTION”
- In case the above key is present, delete it and try again. If eliminating the key doesn’t help, disable your antivirus.
We will use regedit to create a LocalAccountTokenFilterPolicy value.
- Press the Windows key and press R.
- Enter regedit and click OK
- Go to the following path in regedit
- HKLM \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Policies \ System
- For a 32-bit system, create a new DWORD value called LocalAccountTokenFilterPolicy.
- For a 64-bit system, create a QWORD (64-bit) called LocalAccountTokenFilterPolicy.
- In both cases, set the value to 1 numerically (that is, enabled), and don’t forget to click OK.
- Typically, the LocalAccountTokenFilterPolicy value is created before you can set the amount of the data. No problem, just double click and change the data from 0 to 1.
- Then restart your computer and see if you can now access the shared drives or folders.
- If the problem persists after having followed all the previous steps. so
- Press down the Windows key and then press R. Then type hdwwiz.cpl to open Device Manager.
- Select Network adapters, click Show on the menu, and then click Show hidden devices.
- Extend network adapters. If you see Microsoft 6to4 adapters, remove all adapters by right-clicking and selecting Remove device.
- Then restart your PC and test it.
Error 0x80004005 when installing Windows 7 or Windows Server 2008 R2 SP1
Upload CheckSUR here and run it. Run SFC Scan after the System Update Preparation Tool finishes checking the system components.
E_FAIL (0x80004005) when configuring VirtualBox in Ubuntu
If you try to allocate more than 3 GB of RAM to the virtual machine, confirm that the host is a 64-bit system and that real hardware transfer (VT-x) is allowed.
Cannot log in to the virtual machine
The following error may appear in some sessions on a VM (VirtualBox). Open Network Center and select Change adapter settings to fix this problem. Right-click on your Virtualbox virtual host adapter and choose Properties. Please enable “Virtualbox NDIS6 Bridget Networking Driver” if it is disabled and try again. VirtualBox should now start correctly. If not, allow the Virtualbox NDIS6 Bridget network driver for any existing network adapters (Ethernet, WiFi, etc.) and always disable NDIS6 and try.
Uninstall Microsoft 6to4
To resolve this issue, you must uninstall Microsoft 6to4 devices from your Task Manager. Please note that you may not see these devices because they are hidden by default. Therefore, you will only see them after you have activated the Show hidden devices option.
Here are the steps to remove these devices.
- Press down the Windows key and then press R.
- Type devmgmt.msc and press Enter
- Click Show and choose Show hidden devices.
- Double-click Network Adapters
- Right-click on the Microsoft 6to4 device and select Uninstall. Repeat this step for all Microsoft 6to4 devices listed
Once you’re done, restart your computer. Your problem should be solved as soon as you log into Windows again.
Error 0x80004005 when extracting files
If this error occurs when extracting or opening ZIP or RAR files, there are some possible solutions.
Method 1: try a different extraction utility
First, make sure the file is not password-protected, and your extraction utility is not equipped to process password-protected data. You can do this by downloading another service such as 7Zip and checking if a password is required when trying to open or extract the same ZIP or RAR file.
Method 2: disable real-time protection of your AV
Another possible cause is a cautious third-party security suite. In certain circumstances, multiple sets of third-party antivirus block the extraction of compressed files.
If you are using an external third-party antivirus instead of the standard security suite (Windows Defender), you can try temporarily disabling the protection or real-time protection of your third-party antivirus and see if the problem is solved.
In case of error 0x80004005 no longer occurs, you should uninstall your current third-party suite and choose a distinct security suite.
If you want to avoid other problems like this, you should choose the integrated security solution.
Method 3: re-register jscript.dll and vbscript.dll
If the above two possible solutions have failed, we will try a different approach. Some users have successfully fixed this by re-registering some dynamic link libraries (DLLs) at an elevated command prompt. To be more specific, this method tries to solve the problem by re-registering jscript.dll (a library used when JScript is run) and vbscript.dll (a module that contains API functions for VBScript). Here is a quick help on how to do it:
Press Windows Key + R to open a run box. Then type in “cmd” and Ctrl + Shift + Enter and press Yes at the User Account Control (UAC) prompt to open an elevated command immediately.
At the elevated command prompt, type the following command and press Enter:
At the same elevated command prompt, type the following command and press Enter:
Restart your computer and check if you can access or extract.ZIP or.RAR files without getting error 0x80004005