virtualbox.org

4.3.16 is now released hence his discussion is now retired. For an equivalent discussion thread about Windows Host issues with 4.3.16 see here.


Mod note. We seem to have about a dozen different threads discussing the same problem of 4.3.14 failing to launch VMs on Windows hosts running certain antivirus packages, or any other software that does DLL injection. I'm trying to refocus these into a single narrow discussion topic - so please post your observations here.

This is not a generic 4.3.14 discussion forum: if you have some other kind of problem or wish to express an opinion then see the normal "Discuss the 4.3.14 Release" topic. Wibble posts in this topic will be deleted.

Oracle has released a seventh test build VirtualBox 4.3.15 (build 95923) which addresses some of these issues. Further work is ongoing.

When posting, please be explicit about any error messages you have or had, and your host OS. Mention your AV package if relevant. Don't just say "same error".

Request from Devteam: If you see a _different_ error that nobody else has reported yet, it would be cool to get the VBoxStartup.log mentioned in the error message with the report as well as OS version + bit count and the list protective software installed.

-----

I just installed Virtual Box 4.3.14 r95030. First I imported a Puppet Learning VM. It worked just fine on my Dell laptop, so I was setting it up at home.





It imported just fine, but when i tried to kick it off, I got the error message box popping up with "Error in supR3HardenedWinReSpawn" and the details said Error relaunching Virtual Box VM Process: 5 ... (attached).

After reading the forums, I re-installed without the bridged network adapter and got the same results. Just to be sure I did not get a bad download, I pulled a fresh copy and did a full re-install again.

I looked over the forums and did a fill Google search on the error but I am coming up empty. I have placed the screen caps of the errors in with this message.

Can anyone provide me with some insight into where the problem may lie so I can correct it?

Specs:
Windows 7 Ultimate 64-bit
8 GB RAM
Intel Core i5-2400

Having exactly same errors messages, on Windows 8.1 and same VB version, while trying to run Vagrant machine based on Ubuntu 14.04 server and which uses Puppet configs.

Host machine:32-bit Atom Z2760 2GB

Pasting error message in text, so more people may find this.

Failed to open a session for the virtual machine vagrant_default_1405474161322_75434.

The virtual machine 'vagrant_default_1405474161322_75434' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I am observing same error raised by VirtualBox after 1st start of Ubuntu from iso.

VirtualBox 4.3.14r95030

Host:
Windows Vista Home Premium 32-bit
Service Pack 2
Intel Core2 Duo P8600 2.4 GHz

Target:
ubuntu-14.04-desktop-i386

Abort Dialog Title
---------------------
VirtualBox - Error In supR3HardenedWinReSpawn

Abort Dialog Message
-------------------------
Error relaunching VirtualBox VM process: 5
Command line: '81954AFS-4D2F-31EB-A142-B7AD187A1C41 -suplib-2ndchile --comment "Ubuntu 14 server" --startvm f2c461eb-6004-4956-9c2f-08280f6c8026 --no-startvm-errormsgbox' (rc=-104)

Abort Dialog screenshot
----------------------------



OnAbort Message
---------------------
Failed to open a session for the virtual machine Ubuntu 14 server.
The virtual machine 'Ubuntu 14 server' has terminated unexpectedly during startup with exit code 1.

OnAbort Details
-------------------
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

OnAbort screenshot
-----------------------

Confirm supR3HardenedWinRespawn error found from v4.3.14 and v4.2.26, no error from v4.3.12.

Host: Windows Vista 32 bit
Guest: Any (32 bit / 64 bit)

07/15/2014:
Cannot start Virtual Box.
Host OS: Windows 7 Pro 64-bit.
Guest OS: Windows 8.1 Pro 64-bit.


07/18/2014:
Disabled Avast Antivirus shields. Virtual Box now starts, however still cannot start VM's.


Will attempt to reinstall Virtual Box and restart VM's with Avast disabled.

Hi guys,

Just upgraded to 4.3.14 and having exactly the same problem, on Windows7. I cannot start my guest VMs (different versions of fedora) and it keeps me from working, I'm kind of stuck.

Is it possible to downgrade (uninstall 3.14, re-install 3.12 ) without loosing configuration ? (VMs config, netowrk adapters)

best regards


UPDATE: I downloaded VirtualBox 3.12 for win64 and just run the executable (without uninstalling the 3.14 version). At the end of the instal wizzard it asked for a restart of the system (win host) and now the downgrade is complete. The VMs work just fine.

Same problem here. I cant start any of my virtual maschines....

Window 8.1 x64 Enterprise German
Virtualbox 4.3.14 r95030



Für die virtuelle Maschine XPTest konnte keine neue Sitzung eröffnet werden.
The virtual machine 'XPTest' has terminated unexpectedly during startup with exit code 1.
Fehlercode: E_FAIL (0x80004005)
Komponente: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


edit1:
I have Symantec Endpoint Protection 12.1.4100.4126 running on my host (corporate antivirus).

edit2:
I re-installed the old version 4.3.12 replacing 4.3.14 (..reboot.. its working again).

I get the following error with McAfee when starting the Manager. I can't disable McAfee since this is a corporate PC and the scanner is configured by Domain settings.

Interesting post in the beta forum. I don't use resident antivirus so I've not tested it :-

JayEm wrote:Ok, i've researched the problem and found the solution.

It is caused by the following entry in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Program Files\\Oracle\\VirtualBox\\VirtualBox.exe"="DISABLEUSERCALLBACKEXCEPTION"

Delete this entry, and everything works as expected.

The DISABLEUSERCALLBACKEXCEPTION registry key has nothing to do with AV software, it's part of a Windows feature. It is currently unknown why some systems have the key set and others don't.

I am trying to use virtualbox on Win 7 x64 Home Premium with AVG, the registry key does not exist and I have exact same error as bhoff
It still persists if I disable AVG or add exceptions for all virtualbox's .exe and .dll files.
Likewise no dice when using Win 7 compatibility modes or "run as administrator".
Even without Windows firewall and defender the same problem is still there.

I'd suggest removing the 4.3.14 download link for windows, maybe replace with 4.3.12, since it obviously does not work properly on this platform.

More info.

Symantec Endpoint Protection 12.1.4100.4126 is incompatible (even if disabled) with 4.3.14 bld 95030
Comodo Internet Security 7 is incompatible (even if disabled) with 4.3.14 bld 95030

BUT

Microsoft Security Essentials Pre-release (4.6) is compatible with Virtual Box 4.3.14.
As of the moment, this appears (to my knowledge) to be the only (common) AV that IS compatible with VB 4.3.14

Ditto to what Hezd said. I'm running on Win 7 x64 Enterprise with Microsoft Forefront Endpoint Protection v2.1.1116.0. I do not have the registry key containing DISABLEUSERCALLBACKEXCEPTION.

Uninstalling 4.3.14 and going back to 4.3.12.

Installed comodo firewall, the same problem on win7 64
previous version does not have this error

I am also seeing this problem with 4.3.14 on Win7. I've tried a lot of the troubleshooting tips seen in other threads: disabling virtual hardware, disabling AV, checking registry keys, etc. No dice on any of it. One thing I did notice was that the latest version of 4.2 has the same error. Perhaps there is an update common to both versions that might help out Oracle. I downgraded to 4.3.12 and it works fine. I think Oracle should rollback their release until they find a fix.

RK