Error message when starting VMs: Error In supR3HardenedWinReSpawn

[asdfafds]

Almost everyday when I start my machine and run Vbox and try to start a vm, a msgbox appears with the following error:

VirtualBox - Error In supR3HardenedWinReSpawn
(rc=-5640)
Please try reinstalling VirtualBox.
where supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.

When I click "ok", another msgbox appears:

Failed to open a session for the virtual machine Ubuntu 16.04.

The virtual machine 'Ubuntu 16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jbassi\VirtualBox VMs\Ubuntu 16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

This has been happening for month, with current version, last version, tests versions, etc. The reason I haven't reported this bug until now is because if I try again a few times (two or three) the VM starts up correctly. So I cannot reproduce everytime. In order to reproduce I need to restart the machine. The first time I try after a reboot almost always fails.

Version: Version 5.1.4 r110228 (Qt5.5.1) Host: Windows 8.1 Enterprise CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz

[duane]

I am also experiencing exactly these symptoms.

Host: Windows 7 x64, V5.1.4r110228 (QT5.5.1), CPU I7-2860QM Guest: Ubuntu 16.04 x64

Seeing the issue about 50% of VM starts.

Have enabled & disabled shared folders (which fail) ... no effect.

Have enabled & disabled PAE ... no effect.

Confirmed Error also occurs with Ubuntu 13.10 x64

VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640) Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread

This is followed by the same error described by the original poster.

Typically, if I just try again two or three times the error disappears.

[Calvini_03]

I have the same issue. Followed same steps by previous poster but machines do not start.

Host: Windows 10 CPU I5 Guest: Linux Mint 64 Bits 18.1

Tried upgrading to 5.1.22r115126 from 5.1.14-112924 with no results.

I tried creating a new Linux VM and it presents the same error.

From my log files, the issue appears to be related with the AV (McAfee in this case). Similar posting in ​https://forums.virtualbox.org/viewtopic.php?t=68869. Unfortunately, in this case disabling enterprise AV is not an option.

The message when trying to start the test Linux VM is the following:

Failed to open a session for the virtual machine Test Linux1.

The virtual machine 'Test Linux1' has terminated unexpectedly during startup with exit code -1073740940 (0xc0000374).

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[Jeff223344]

I am having the exact same issue as the original poster, same error messages, same result. However, even if I try re-starting multiple times VirtualBox will not start my virtual machine so I am completely stuck. Given that, I would classify this error as a High priority, not "minor".

I have tried this re-installing and rolling back to earlier versions and have gotten this error in every case. I have tried V5.1.22, 5.1.24, and 5.1.26.

Host: Windows 10 Enterprise V1607, 64-bit Intel Core i7-7600 8 GB RAM Guest: Lubuntu 64 bit v16.04.1 Windows Defender in a corporate environment so I cannot disable it.

[vendan]

I'm having the same issue, reverting to 4.3.12 worked.

[Jachym]

Hello,
I have the same problem. On windows 8 everything was ok. Unfortunately, after a disk failure, Windows 10 was installed. And here the problem with running the virtual machine started.

"...
(rc=-5640)
Please try reinstalling VirtualBox.
..."

I reinstalled VirtualBox several times. With administrator rights, older version, no changes. I currently have VirtualBox 5.2.8 r121009 (Qt5.6.2)
Has someone managed to solve the problem? Or know the exact reason?

[lexxus]

Lexxus's LOGs

[lexxus]

I have the same issue on Win10 with 5.1.22

[asdfafds]

Edit: after changing hardware, installing Windows 10 instead of 8, installing Virtual Box (5.2.12 r122591 (Qt5.6.2)), creating new VMs, it keeps happening. The only thing in common with my previous setup is the McAfee Antivirus. Again, not a big deal, because after one or two retries it works.

[asdfafds]

I confirm this still happens under on Win10 enterprise v1809 (OS build 17763.1397) with VirtualBox 6.1.12r139181 (Qt5.6.2).

[HV]

This issue still exists as documented with Win10 Enterprise 19041.804 running Virtualbox 6.1.16 r140961.

[asdfafds]

Sometimes it happens that no matter how many times you try, you get the same error. That is because there is not enough free memory to start up the VM. Close every program and try again a few times.

If it still doesn't work, disable start-up programs, restart the machine and try again. This happens on 100% of the machines of one of the big four...