Page 1 of 1

VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 12. Jul 2014, 21:13
by MichaelH
I uninstalled 4.3.12, rebooted, and installed 4.3.14 RC1 94905. Afterwards I get the error in supR3HardenedWinReSpawn. Error relaunching VirtualBox VM process 5 Command line: (the rest is in the picture). I've tried both with and without the extension pack installed and there is no change. I've also tried uninstalling and reinstalling with right click "Run as admin". I've tried launching all of the VMs I have and none work. There was another error I didn't get a screenshot of that said "failed install ntcreatesection".

What should I try next? I'd like to help test the release candidate.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 12. Jul 2014, 21:55
by yesoos
I'm having exactly the same issue in this thread: Windows 8.1 x64 Host, can't start any VM. (can't post links yet). Windows 8.1 x64 host, also tried new clean installs, with removing profile, recreating vms etc. Still have this error.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 13. Jul 2014, 23:02
by MatthijsM
Start of VBox 4.3.14_RC1-94905 on Win7prof/SP1 gives the following error dialogue:
Wimdows error dialogue
Wimdows error dialogue
VirtualBox-4.3.14_RC1-94905-Win_Errors.png (71.94 KiB) Viewed 21077 times
Reinstalling VBox 4.3.12 resolves the problem...

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 14. Jul 2014, 13:35
by frank
Thank you. Are you running any virus scanner on your system? If so, which one?

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 14. Jul 2014, 20:24
by yesoos
Frank,

I'm running Kaspersky Internet Security (latest version), but had the same issue when disabling KIS.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 15. Jul 2014, 23:56
by MichaelH
I am running Avast! free antivirus. 2014.9.0.2018 with current definitions. It didn't report anything blocked or quarantined during or after the install.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 10:23
by frank
The problem is not the virus scanning engine but the habit of virus scanners to map certain DLLs into Windows processes. VirtualBox 4.3.14 has extended hardening features which may conflict with virus scanners. We did several tests but obviously didn't catch every case. The final 4.3.14 release contains more fixes in this regards but I've read in other topics that certain users have still problems :-(

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 11:25
by MikeDiack
Sorry to say Frank that the final build still is very problematic in this area. Even disabling Avast, Comodo, Symantec AV's still prevents the final build starting correctly.

Can I suggest pulling this release and updating it to give a option to turn the hardening support on or off?

Mike

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 20:45
by yesoos
@Frank

Still have the same issue with final version of 4.3.14. Should I create a bug for that or have this already been created?

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 21:36
by MichaelH
Install of 4.3.14-95030 immediately shows this error. Is there a bug I should post to at this point? I'll uninstall my antivirus and see if that helps.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 21:39
by Jacob Klein
When posting, please also indicate your Operating System, just in case the issue here is Operating-System-specific.
I have not had problems with Windows 8.1 Update 1 x64, using the built-in Windows Defender antivirus.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 23:11
by MichaelH
I am running Windows 7 SP1 x64 all security updates installed.

After uninstalling Avast! Antivirus and reinstalling VirtualBox 4.3.14-95030 VMs launch just fine. I'll see if reinstalling Avast! at this point breaks it again or not.

If if it breaks again I'll switch to Windows Defender for now.

Re: VirtualBox 4.3.14 RC1 94905 for Windows Errors

Posted: 16. Jul 2014, 23:33
by MichaelH
Okay, reinstalling Avast! lead to the same problem. Installing Microsoft Security Essentials doesn't seem to cause any problems though.