How to Repair “Error in supR3HardenedWinReSpawn” on VirtualBox

  • The “Error in supR3HardenedWinReSpawn” problem occurs when installing Oracle Virtualbox – usually a few seconds after trying to start a virtual machine.

Virtualbox Hardened

Therefore, VirtualBox (VBOX) enlists the help of the kernel to try to protect its processes. The source code refers to this as Process Hardening. VBOX tries to protect the processes from the same user the process is running under. A detailed rationale and technical overview is provided in source code comments. The TL;DR; is the protection gates access to the VBOX kernel drivers, which due to design have a number of methods which can be used to compromise the kernel, or at least elevate privileges. This is why VBOX tries to prevent the current user compromising the process, getting access to the VBOX kernel driver would be a route to Kernel or System privileges. As we’ll see though while some protections also prevent administrators compromising the processes that’s not the aim of the hardening code.

It seems that supR3HardenedWinReSpawn is having an error (rc=-5640). If this is so, please reinstall VirtualBox. where: supR3HardenedWinReSpawn what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (5640) – Process Verification Failure: There are multiple threads in the process.

During the first time the virtual machine is run after Oracle VirtualBox is installed, supr3hardenedwinrespawn errors may occur.

I am getting a supR3HardenedWinReSpawn error on a virtual machine that has worked flawlessly for quite a while. The problem started after a power failure while the VM was running. The VM is supposed to boot from a physical disk, and I can indeed boot Linux on the real machine from that disk with no problems. I’ve read what I could find here and elsewhere, but couldn’t find enough guidance to solve the problem. I’ve run System File Checker. I’ve uninstalled VirtualBox and then reinstalled it from scratch, selecting Run as Administrator. I’ve deleted the virtual machine and created a new one. I’ve made sure virtualization didn’t somehow get turned off in the BIOS.

As soon as you try to start a virtual machine after installing Oracle Virtualbox, you encounter the error “Error in supR3HardenedWinReSpawn”. Virtualbox becomes completely inoperable after this problem occurs (each new virtual machine displays the same error message).

Virtualbox Hardening

Vbox has been my primary tool for months and I’ve run into problems hardening it ever since. I got a short-term fix that has worked well, but it’s getting old.

Earlier this week, I had updates installed on my Windows 7 host, and I decided to restart for virtualization so I could play around with my W10 virtual machine. However, I was greeted with the following error message: Error in supr3hardenedwinrespawn.

VirtualBox fails to start after installation of the latest version and restarting the computer:

A virtual box is reporting an error. “SupR3HardenedWiReSpawn failed”.

What is the cause of the “Error in supR3HardenedWinReSpawn” error in VirtualBox?

What is the cause of the "Failed to Acquire a VirtualBox COM Object" error?

  • A missing driver (VBoxDRV.inf) is often indicated by the VirtualBox “Error in supR3HardenedWinReSpawn” error. This might be the result of a permissions problem with the main VirtualBox application.
  • Alternatively, the VirtualBox driver may be contributing to a registry shift that causes this problem.
  • Older computers may require manual adjustments in order to enable hardware virtualization by default, which can also cause this problem. While hardware virtualization is enabled by default in many computer configurations, it may need to be enabled manually in the BIOS or UEFI settings.
  • One of the most common reasons for this behavior is a missing driver (VBoxDrv.inf). Perhaps due to authorization issues, the installation of this important driver was not completed during the initial installation.

How to resolve the “Error in supR3HardenedWinReSpawn” in VirtualBox?

Vbox Hardening

My understanding is that VirtualBox Hardening provides additional checks for compiled applications. For example, during the build, you must specify the exact location of the built application, as well as the name of the application. In order to run the app, the requirements must be met. It is for this reason that you cannot rename VirtualBox.app, or relocate VirtualBox-5.2.18.app. “VirtualBox-5.2.18.app” will not work.

You may be getting this error because of a lack of RAM allocation in your virtual machine. If it persists, try allocating more RAM to your new configuration and see if it solves the issue.

I receive the following error message almost every time I launch VBox and attempt to start a virtual machine:

It says that the file name is invalid (malformed) in the error message: “where: supR3HardenedWinReSpawn what:5”. The VBoxHardening.log shows error opening this file: “c:\WINDOWS\system32\wintab32.dll”.

It is well known that antivirus protections are not perfect, not just because they cannot detect all threats 100%, but also because they sometimes detect things as such processes when they are not. If you receive an error message about VirtualBox supR3HardenedWinReSpawn, I recommend that you look in that direction first.

Steps for fixing VirtualBox error starting virtual machines are as follows:

supr3hardenedwinrespawn can generate the VirtualBox error for several reasons, making diagnosis challenging.

It failed to create NtCreateFile(/Device/VBoxDrvStub), indicating the unknown status -5657 (0xffffe9e7) (rcNt=0xe986e9e7) of supR3HardenedWinReSpawn: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7). Make sure the kernel module is loaded correctly: /Device/HarddiskVolume4/Program Files/Oracle/VirtualBox/VirtualBox.exe (rc=-5657).

Turn on the virtualization in the BIOS

  1. You can bring up the boot screen by pressing F2/F4/F6/F8 several times, depending on the manufacturer of the computer. The keys vary depending on the manufacturer.
  2. The Advanced tab can be found under Advanced Chipset Control or CPU Configuration, if you don’t have it.
  3. Intel’s virtualization technology should be enabled if you use an Intel processor.
  4. Enable AMD-V if your processor is AMD.
  5. The BIOS is then updated to enable virtualization technology and the system is rebooted.
  6. You should be able to run Oracle VirtualBox after restarting the system in order to see whether the supr3hardenedwinrespawn bug has been resolved.

Allot additional RAM for your virtual machine

  1. Use Oracle VirtualBox Manager to manage Oracle VM VirtualBox.
  2. If you would like to uninstall your virtual machine, select Uninstall from the right-click menu.
  3. Click Delete Only in the dialog box that appears.
  4. Make sure that the same image is used in the new configuration.
  5. If you want to install a virtual machine again, make sure to allocate more memory in the Base Memory section than when you last installed a virtual machine.
  6. The virtual machine should be run after the configuration has been created to ensure it is performing well.

Installing the VBoxDrV.inf file

  1. The following directory can be found in the file explorer
    This is the directory where the Oracle VirtualBox drivers are installed.
  2. Copying and pasting the above path into File Explorer is also an option.
  3. VBoxDrv.inf can be installed by right-clicking on it in the VBoxDrv folder.
  4. To continue with the installation, click Yes when UAC asks for your confirmation.
  5. By pressing the Windows key, you will be taken to the Windows desktop.
  6. Choose Run as Administrator from the context menu after typing cmd.
  7. The following command must be typed at the command prompt and executed by pressing Enter:
    Start the VBoxDRV service with the following command:
  8. After you have successfully executed the command, close the command prompt window.
  9. The virtual machine can be restarted to see if improvements occur.

Reinstalling VirtualBox

  1. In order to fix the error, you need to install the latest Oracle VirtualBox version.
  2. You can do this by pressing Windows + R.
  3. Control panel can be opened by typing control and clicking OK.
  4. To access programs and features, go to Programs.
  5. The list of installed applications should include VirtualBox. Select it.
  6. Select Uninstall. Confirm your selection by clicking Yes.
  7. You can download VirtualBox after you have uninstalled it.
  8. Make sure the software is up-to-date by downloading it and installing it.
  9. If your computer is not performing as well as it should, reconfigure it.

Frequently Asked Questions

  1. Install the file VBoxDrV. inf.
  2. Check for problems with the directory. Press Windows + R to open Run.
  3. Allocate more RAM for the virtual machine. Run Oracle VM VirtualBox Manager.
  4. Turn on virtualization in your BIOS.
  5. Change the settings of the paravirtualization interface.
  6. Reinstall VirtualBox.

After installing Oracle VirtualBox, you may experience a supr3hardenedwinrespawn error problem. This problem occurs when the user runs the virtual machine for the first time after installing the program. The reason for this error is due to a missing VBoxDrv.

The easiest way to solve the problem, in this case, is to uninstall the current version of VirtualBox and then install the latest available stable version.

  1. Go to the Control Panel and uninstall VirtualBox.
  2. Reboot your computer.
  3. Download the latest version of VirtualBox.
  4. Right-click on the downloaded file and select "Run as administrator".
  5. Follow the on-screen instructions to install VirtualBox.
  6. After installation, restart your computer.

Website | + posts

Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog, techquack.com, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.