Error in supR3HardenedWinReSpawn

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Adam Hughes
Posts: 3
Joined: 2. Oct 2015, 15:42

Error in supR3HardenedWinReSpawn

Post by Adam Hughes »

Hello,

I configured a virtualbox (Host: Windows 7, Guest Ubuntu 15.04, VBox=4.3.16, Symantec AntiVirus) this week, and it was working flawlessly. Unfortunately, my system admin applied the September Microsoft Patch last night, and also Symantec r16 definition updates, and now I'm getting the following errors (see attached screenshots):

NtCreateFile(\Device\VboxDrvSTub) failed: 0xc000034.... Make sure the kernel module has been loaded successfully.

Failed to open a session for virtualmachine .... has terminated unexpected during startup with exit cod (0x)...

Compressed log file is attached.

There are older threads indicating that this, or a related issue, were present in 4.3.15, but the thread is locked as the issues have been presumably resolved. I'm not sure what to do to begin troubleshooting this.
e1.png
e1.png (47.27 KiB) Viewed 1141 times
e1.png
e1.png (47.27 KiB) Viewed 1141 times
Thanks.
Attachments
VBoxStartupLog.zip
(9.51 KiB) Downloaded 6 times
e2.png
e2.png (24.87 KiB) Viewed 1139 times
Adam Hughes
Posts: 3
Joined: 2. Oct 2015, 15:42

Re: Error in supR3HardenedWinReSpawn

Post by Adam Hughes »

Guess I'm out of luck, huh?
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Error in supR3HardenedWinReSpawn

Post by Perryg »

While I don't do windows I can tell you that it appears that you have a corrupt certification database on the Windows host. This has been discussed a lot and there are some things that you can do to fix it. Search through the posts by running the following in is your favorite search engine.
  • Error in supR3HardenedWinReSpawn site:virtualbox.org
Adam Hughes
Posts: 3
Joined: 2. Oct 2015, 15:42

Re: Error in supR3HardenedWinReSpawn

Post by Adam Hughes »

Thanks. My system admin updated to 4.3.28 and the problem is gone!

Sorry, usually it takes much longer to push updates through my system or I wouldn't have made a discussion.
Post Reply