FIX: VirtualBox error in supR3HardenedWiReSpawn – Error restarting VirtualBox VM process 5 (solved) –

Many VirtualBox users (including me) have encountered the following problem when starting a virtual machine after restarting the computer: “VirtualBox – error supR3HardenedWiReSpawn” and after clicking “OK” “Could not open virtual session” another error appeared. machine exit code 1 (0x1) – E_FAIL (0x80004005)”, refer to “VBoxHardening.log” for details about this error. However, the “VBoxHardening.log” file does not have a clear explanation of the problem, only that many DLL files do not have “WinVerifyTrust”.

Problem description: After installing the latest version of VirtualBox on a Windows 10 computer and restarting the computer, the following errors appear when starting the VM machine:

“VirtualBox – error in supR3HardenedWiReSpawn
An error occurred while restarting the VirtualBox VM process: 5
What is supR3HardenedWinReSpawn: 5 VERR_INVALID_NAME (-104) – Invalid (malformed) file/path name.”

FIX: VirtualBox error in supR3HardenedWiReSpawn and hardening issues (resolved)

…and after clicking OK (in the above message) you get the following error:

“Could not open session for virtual machine %VM_Machine_Name%.

Virtual machine ‘%VM_Machine_Name%’ terminated unexpectedly when started with exit code 1 (0x1). More details can be found in “C:\Users\Admin\VirtualBox VMs\%VM_Machine_Name%\Logs\VBoxHardening.log”.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}”

Virtual machine shut down unexpectedly - VBoxHardening.log'

This guide contains instructions for solving the following VirtualBox errors:

  • VirtualBox error in supR3HardenedWiReSpawn. Error restarting VirtualBox VM process: 5…supR3HardenedWinReSpawn What is: 5 VERR_INVALID_NAME
  • Could not open session for virtual machine…Virtual machine terminated with exit code 1 (0x1)”
  • The The “VBoxHardening.log” file reports multiple .dll files [lacks WinVerifyTrust].

How to fix: Error 5 when restarting VirtualBox VM process [lacks WinVerifyTrust]

Important: Before doing the following steps, try the following steps and check if you can start the VM (after applying each of them):

1. Disable AV Real Time Protection or uninstall the antivirus software and then try to start the VM. *

*Note: If you are the owner HP Pro or an HP Elite computerContinue with HP preinstalled software and turn off the following programs:

  • HP Customer Security
  • Click HP of course
  • HP Sure Sense

2. Make sure of it Hyper-V Off. To do so, go to Control Panel > Programs and features > Turn Windows features on or off and Remove the mark the Hyper-V feature.

3. Navigate to “C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv”, right click. VBoxDrv.inf and press Installation.


4. Uninstall and reinstall VirtuaBox by doing the following:

a. go to Control Panel > Programs and features and Delete VirtualBox
b. Restart your computer.
c. Download it The latest version of VirtualBox.
d. Right click on the downloaded file and click Run as administrator.
e. Restart your computer.
f. Try starting the VM and if you get the same error, try the following steps:

Step 1. Change the startup type of the VBoxDrv service (VBoxDrv.inf) to 2 (Autoboot)*

*Note: The idea is to change the “Start” value of the VBoxDrv service 2It came up after reading the Fix Hardening (workaround) for error after installation and restart on the VirtualBox forums, where it is recommended to change the “Start” value to 3. But that change didn’t work and things got worse.

1. Opening Registry editor.
2. Go to this button on the left panel:

3. Double click on the right panel Start REG_DWORD value.

FIX: What is supR3HardenedWinReSpawn: 5 VERR_INVALID_NAME

4. Change the value data from 1 2 and press OK. *

* Possible values ​​for the startup type of the “VBoxDrv” service (“Start” is stored in the REG_DWORD value).

Value Run Type Explanation
0 The download service is loaded at boot.

1 System: The service is loaded During KERNEL initialization (boot).
2 Automatic: The service is loaded automatically by the Service Control Manager.
3 Manual: The service is loaded manually (on demand).
4 Disabled: The service is disabled.


5. Close Registry editor and restart computer.
6. Try to start the VM. If the VM fails to restart, go to step 2 with the error “Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87).

Step 2. Disable Hyper-V at boot.

On Windows 10 PRO or Enterprise, HYPER-V is enabled at startup by default, so go ahead and disable it.

1. It’s open Command line as administrator.
2. Type the following command and click Enter:

  • bcdedit / set the hypervisor startup type

Disable HYPER-V at boot

3. Restart your personal computer.
4. After rebooting, start the VM.

That’s it! Let me know if this guide helped you by leaving a comment about your experience. Please like and share this guide to help others.

If you found this article useful, please support us by donating. Even $1 can make a big difference for us We continue to help others while keeping this site free:

Leave a Comment