Error 0x80004005 appears to be a widespread issue for Windows users. You might have tried accessing Shared Folders, starting Virtual Machines, or updating your Windows, but you failed and were presented with an Error message. When troubleshooting it, this error can appear as ‘unspecified’, which evokes even more confusion.
In this article you can find a gathering of solutions to various cases in which you might have encountered Error 0x80004005. These solutions were confirmed to be helpful by users.
It could be its registry key that is causing the problem. To solve this issue, follow these steps:
- Hold the Windows key, then press ‘R’.
- A box will pop up, in which you should type ‘regedit’. Press OK.
- After the Registry Editor shows up, go to this registry path:
After you’ve found it, delete this key.
If the Error is still appearing, try turning your antivirus off. And if this doesn’t work either, try uninstalling the antivirus. See if the Error shows up again. If it doesn’t, reinstall the antivirus. Also, maybe consider installing a different antivirus instead. AVG and Security Essentials are surely some of the better ones that I recommend.
Shared Drive or Folder Error
- Repeat the same step as with VirtualBox Issue: Press Windows key + ‘R’ and type in ‘regedit’.
- Go to this registry path:
- Right-click on the screen and ‘Create a New DWORD or QWORD Value’ (DWORD if you have a 32-bit system; QWORD if you have a 64-bit).
- Name it ‘LocalAccountTokenFilterPolicy’ and click OK.
- Its numeric value will be preset to ‘0’, however, you should change it by double-clicking it and choosing ‘1’.
- After that, reboot your system and try entering Shared Drive/Folder.
If this didn’t resolve the issue, try this:
- Press the Windows key and ‘R’ again. This time, type ‘hdwwiz.cpl’. Device manager will pop up.
- Choose ‘Network Adapters’ and select ‘View from Menu’, then ‘View Hidden Devices’.
- Click ‘Expand Network Adapters’. If you can see the Microsoft 6to4 Adapters, right-click them all and ‘Remove Devices’.
- Again, restart your machine and test for Error 0x80004005
Problem When Installing Windows 7 or Windows Server 2008 R2 SP1
Download CheckSUR. Run it and run the System Update Readiness tool, then go for the SFC Scan.
Problem With VirtualBox Setup on Ubuntu
In case you come across the E-Fail 0x80004005, it might be that you are using more than 3 GB of RAM for the Virtual Machine on a 32-bit System. Only 64-bit systems support more than 3 GB.
Virtual Machine Failed to Open a Session
To resolve this, Open ‘Network Center’, then click ‘Change Adapter Settings’. Click on your VirtualBox’s Adapter and choose ‘Properties’.
Check if ‘VirtualBox NDIS6 Bridget Networking Driver’ is enabled. If not, enable it. Then try opening VirtualBox again.
If this didn’t fix the issue, enable ‘VirtualBox NDIS6 Bridget Networking Driver’ for all the adapters you have, then try again.
Another thing you can do is uninstall Microsoft 6to4 devices, you can do so by following the following steps:
- Press Windows key and ‘R’, then type ‘devmgmt.msc’ and click OK.
- Click ‘View’ and ‘Show Hidden Devices’. This will allow you to see the devices, which you previously couldn’t.
- Double-click ‘Network Adapters’.
You will see a list of Microsoft 6to4 devices. Right-click and ‘Uninstall’ all of them.
Restart your computer and log back into your Windows account. This should have resolved the Error 0x80004005 issue.