[Solved] Error relaunching VirtualBox VM Process: 5 | VirtualBox won't start

In this article we are going to discuss about the 'supR3HardenedWinReSpawn' error. When i was exploring the Cisco IOU tool, I had to import a Cisco IOU VM which was in OVF file format. But as soon as i double click the ovf file, VM refused to start and an error popped up, saying:

Error in supR3HardenedWinReSpawn

Result Code: E_FAIL (0x80004005)

Component: Machine

Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Error relaunching VirtualBox VM process: 5

Command line: '81954AF5-4D2F-31EB-A142-B7AF187A1C41-suplib-2ndchild--comment Fedora32 --startvm fd699e30-a77b-4eac-8ced-1210d756855d --no-startvm-errormsgbox' (rc=-104)

The error that you receive might not be as exact as it's given here, since VM details are also part of the error. For example,

If you look at the error shown above, My VM name 'GNS3 IOU VM' is also part of the error. 

Why do I see this error ?

Well, When i was doing a little research on this topic, i found out that this error might show up because of any one of the below points. 

1. It could be an issue with the VirtualBox version that you are trying on, I found the latest VirtualBox version 5 to be very buggy. 
2. It might be your Antivirus which causes this error.
3. It might be because of your registry settings.

How to resolve this E_FAIL (0x80004005) error ?

Try the below solutions one by one,

Solution 1:

Find the below entry in Registry Editor and delete it.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"="DISABLEUSERCALLBACKEXCEPTION"

Solution 2:

Uninstall or Disable your Antivirus software.

Solution 3:

If the above 2 solutions did not work, Try degrading the degrading the VirtualBox to version 4.3.12 from the version that you are currently running. You can download VirtuablBox 4.3.12 from this link. https://www.virtualbox.org/wiki/Download_Old_Builds_4_3_pre24

If you still face this issue, I would recommend you to try the other desktop virtualization softwares like Vmware Workstation or Hyper--V.

I hope this post helps you to solve the mentioned error.