Last Updated on July 11, 2021
Updated November 2022: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
- Download and install the repair tool here.
- Let it scan your computer.
- The tool will then repair your computer.
Many VirtualBox users have faced the following problem when starting a virtual machine after rebooting the computer: “VirtualBox – Error in supR3HardenedWinReSpawn” and after clicking OK, there is no clear explanation of the problem, except that there are many “WinVerifyTrust” DLL files missing.
Problem description: on a Windows 10 computer, after installing the latest version of VirtualBox and rebooting the machine, the following error message appears when starting the virtual machine:
“VirtualBox – Error in supR3HardenedWinReSpawn”.
This guide contains instructions on how to fix the VirtualBox error.
What is the cause of the “supR3HardenedWinReSpawn” error in VirtualBox?
One of the most common reasons for this behavior is a missing driver (VBoxDrv.inf). It is possible that due to authorization issues, the installation of this important driver was not completed during the initial installation. In this case, the problem can be solved by manually installing the VBoxDrv.inf file.
Another possible cause of this error is an anomaly in the registry pointing to the wrong driver directory. If this scenario applies, you can quickly fix the problem by performing a registry check and correcting the ImagePath line if the directory is incorrect.
One of the most common causes of the VirtualBox “Error in supR3HardenedWinReSpawn” error is a missing driver (VBoxDRV.inf). It is possible that the main VirtualBox application is installed without this important driver due to an access rights issue.
One possible cause of this problem is a directory problem caused by a registry mismatch that the VirtualBox driver contributes to. If this scenario applies, you can quickly fix the problem by performing a quick registry check to see if the driver path leads to VBoxDrv.sys.
It turns out that another possible reason for this problem is that virtualization is disabled in the BIOS or UEFI settings. Although hardware virtualization is enabled by default in the vast majority of computer configurations, you may need to manually adjust the settings on older computers.
How to repair the VirtualBox supR3HardenedWinReSpawn error?
- Try installing the latest version of Oracle VirtualBox to fix the error.
- Press the Windows + R key.
- Type control and click OK to open the control panel.
- Go to Programs -> Programs and Features.
- Select VirtualBox from the list of installed applications.
- Click the Uninstall button. Click Yes to confirm the action.
- After uninstalling, go to the VirtualBox download page.
- Download and install the latest version of the software.
- Reconfigure the machine and check for enhancements.
Installing the VBoxDrV.inf file
- Open File Explorer and navigate to the following location:
- You can also copy and paste the above path into File Explorer.
- In the VBoxDrv folder, right-click on the VBoxDrv.inf file and run Install.
- UAC will ask you to confirm the action. Click Yes to continue the installation.
- Then press the Windows key.
- Type cmd, right-click at the Command prompt and select Run as administrator.
- At the command prompt, type the following command and press Enter to start:
sc start vboxdrv
- Once the command is successfully executed, close the command line window.
- Try restarting the virtual machine and see if anything has improved.
Reinstalling the missing file seems to have fixed the problem for many users. This driver may not have been installed due to permission issues, causing problems with the virtual machine.
Allocate more RAM for your virtual machine
- Launch Oracle VM VirtualBox Manager.
- Right-click the current virtual machine installation and select Uninstall.
- In the new dialog box, click Delete Only.
- Then proceed to create a new configuration with the same image.
- However, when you go to the base memory part, make sure that you allocate more RAM than the previous VM installation.
- After creating the configuration, go ahead and boot the VM and see if there are any improvements.
The supr3hardenedwinrespawn error may be due to insufficient memory allocation for the virtual machine. Try allocating more memory for the new configuration and see if the situation improves.
Changing the paravirtualization interface settings
- Start Oracle VM VirtualBox Manager.
- Right-click the virtual machines on which the error occurred and select Settings.
- In the left pane, open the System tab.
- In the right pane, open the Acceleration tab.
- Expand the Paravirtualiaztion Interface menu and select the KVM option.
- Click OK to save your changes.
- Run the virtual machine and see if there is any improvement.
Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here
Frequently Asked Questions
Go to Start (Shell), Control Panel, Programs, and Features. You will see a list of installed applications in alphabetical order. Left-click on "Oracle VM VirtualBox" to select it, then right-click and select "Uninstall" from the menu.
- Install the file VBoxDrV. inf.
- Check if there are any problems with the directory.
- Allocate more RAM for the virtual machine.
- Enable virtualization in your BIOS.
- Change the paravirtualization interface settings.
- Reinstall VirtualBox.
- Go to the Control Panel and uninstall VirtualBox.
- Reboot your computer.
- Download the latest version of VirtualBox.
- Right-click on the downloaded file and select "Run as administrator".
- Follow the on-screen instructions to install VirtualBox.
- After installation, restart your computer.
- Remove the saved state of the virtual machine.
- Stop the VirtualBox process in Task Manager.
- Disable Hyper-V.
- Check the permissions of the virtual machine files.
- Update the VirtualBox software.
- Reinstall the VirtualBox software.