Page 1 of 1

Can't start any VM due to Error In supR3HardenedWinReSpawn

Posted: 19. Jul 2015, 20:58
by Klebitz
Since I upgraded my VirtualBox to a newer version, it was like 4.3.x at that time, I wasn't able to run any VM again. After pressing start, it always displays the same error, as you can see in the attachments. I searched on the forum and on google for solutions, tried some of them but nothing helped at all, always the same error.
In this example i have a windows 10 guest but if I try with ubuntu 14 or Kali Linux the result is always the same.

Host:
Microsoft Windows 7 Home Premium
6.1.7601 Service Pack 1 Build 7601
Processor:
Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz, 2301 Mhz, 4 Cores, 8 Threads
RAM: 8 GB

Antivirus/Care tools: Iobit Advanced System Care Pro, CCleaner, Malwarebytes Anti-Malware
VB version: 5.0.0 r101573
oracle_error.PNG
oracle_error.PNG (69.93 KiB) Viewed 3528 times
error2.PNG
error2.PNG (82.64 KiB) Viewed 3528 times
VBoxStartup.zip
(3.76 KiB) Downloaded 29 times

Re: Can't start any VM due to Error In supR3HardenedWinReSpa

Posted: 19. Jul 2015, 23:37
by noteirak
Here is the actual problem:
2664.ef4: supR3HardenedWinReadErrorInfoDevice: 'Found executable memory at 0000000000160000 (0000000000160000 LB 0x1000): type=0x20000 prot=0x40 state=0x1000 aprot=0x160000 abase=ffffffff00000040'
2664.ef4: Error -5619 in supR3HardenedWinReSpawn! (enmWhat=3)
2664.ef4: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5619 (0xffffea0d) (rcNt=0xe986ea0d)
VBoxDrvStub error: Found executable memory at 0000000000160000 (0000000000160000 LB 0x1000): type=0x20000 prot=0x40 state=0x1000 aprot=0x160000 abase=ffffffff00000040
20e8.144c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5619 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5619 (0xffffea0d) (rcNt=0xe986ea0d)
VBoxDrvStub error: Found executable memory at 0000000000160000 (0000000000160000 LB 0x1000): type=0x20000 prot=0x40 state=0x1000 aprot=0x160000 abase=ffffffff00000040
20e8.144c: Error -5619 in supR3HardenedWinReSpawn! (enmWhat=3)
20e8.144c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5619 (0xffffea0d) (rcNt=0xe986ea0d)
VBoxDrvStub error: Found executable memory at 0000000000160000 (0000000000160000 LB 0x1000): type=0x20000 prot=0x40 state=0x1000 aprot=0x160000 abase=ffffffff00000040
Another software on your computer is trying to inject itself into VirtualBox in a supiscious way (similar to what virus, malware & others are doing) and VirtualBox is protecting itself against it.
Klebitz wrote:Antivirus/Care tools: Iobit Advanced System Care Pro, CCleaner, Malwarebytes Anti-Malware
Most likely, one of these program is the culprit. Disable them one at the time, try to run the guests again, and see if it makes any difference. You might need to uninstall them completely.
It also might be another program, so you might need to investigate a bit.

Once you managed to know which one is causing it, you can report here with the exact software name & version, also open a ticket on the BugTracker with the logs so the devs can take a look at it.

Re: Can't start any VM due to Error In supR3HardenedWinReSpa

Posted: 20. Jul 2015, 00:24
by Klebitz
Well, I made sure that none of these were running using the task manager, terminated them all Iobit and Malwarebytes related programs, still pops up the same. I'm not really in the mood to uninstall these programs to discover the 'bad guy'. Still I remember Iobit gave me some problems with other software before...
I tried to terminate RazerSynapse and other background apps like NVidia stuff, still didn't work.
I guess the only way is to uninstall the quoted above and see if it works, once I get the time to do so, thank you for your help.
I will take a chance on the bugtracker too.

Re: Can't start any VM due to Error In supR3HardenedWinReSpa

Posted: 20. Jul 2015, 22:37
by Klebitz
I uninstalled every program quoted above, same result. I don't know what might be causing this to happen. After uninstalling these programs I reinstalled Virtualbox and rebooted, without different results.
This error is the definition of insanity itself.
Any tips ? :mrgreen: