4.3.14 conflicts with anti-virus packages.

[Jacob Klein]

bird:
When we install a test build, is it normal behavior for the registry key:
HKLM\SOFTWARE\Oracle\VirtualBox\InstallDir
...
to be BLANK?

No, that's a genuine bug. Thanks for noticing! I can reproduce it locally and have field an internal bug report for our installer guy. I fear the fix will have to wait till 4.3.18 as the guy is on vacation right now.

I'm confused. Are you suggesting that this was reported too late to include in the upcoming public release? This is NOT the first time I've posted about this. I posted as soon as I spotted it, over 6 weeks ago! In this very thread. viewtopic.php?f=6&t=62615&p=294032&hili ... ir#p294032 .... I even provided every single detail at that point. I guess that you just never saw it.

I had assumed that, since you weren't responding, that perhaps it was normal behavior for a test build. Rom (my BOINC developer contact) suggested I wait until we get a release candidate, and retest with it. So, for the 7 test builds, I manually put the registry key in, each and every time after the install, so I could continue testing with BOINC. And then, when you posted the build for us to think of as a "release candidate", I was shocked to find the bug still present.

I expect this to be fixed BEFORE any public release, as it is a significant bug! Showstopper for the BOINC community.

I discovered that bug because BOINC reads that registry information to determine if VirtualBox is installed, and what version. Without InstallDir, though, BOINC ends up thinking VirtualBox is not even installed. I'm sure other apps do similar behaviors, reading that information to determine if VirtualBox is installed. So, please ensure it gets fixed before the public release. We in the BOINC community hate to keep telling our users "don't use VirtualBox version blah, because it too has a showstopper bug for us."

- Jacob

[Cognizant]

Thanks. latest build (7) VirtualBox 4.3.15 (build 95923) Finally working.
Win 8.1 64b - Avast

Thanks for your hard work. Much appreciated.

[MikeDiack]

Sorry to report that the latest build 4.3.15 build 95923 has regressed seriously compared to 95713 on my systems:

I'm running 3 Windows 7 x64 SP1 systems with Symantec Endpoint Protection 12.1.4112.4156.

Since upgrading from build 95713 to 95923, I now see the following on starting a guest VM:

1) A very long pause (even on a fast 8 core 16GB RAM machine) of at least 30 seconds, before the starting message appears with "Creating process for virtual machine".
2) The "Creating process for virtual machine" message box (entitled Starting VM) and progress bar then stay unchanging for several minutes (the progress bar remains at 0%) and eventually times out and disappears. The guest OS itself never even shows the BIOS, never mind the OS itself.
(I've tried this with Windows XP and Windows 7 x86 SP1 guests that worked fine with build 95713)

In short the virtual box application is basically becoming unresponsive and is hanging and timing out before it ever starts the guest OS running.

Just in case this was a problem of upgrading direct from 95713 to 95923, I've tried uninstalling Virtual Box 95713 and reinstalling 95923. The results are the same.

I've attached one such startup log for a Windows 7 guest

Mike

[MikeDiack]

Further confirmation of my previous posting (hanging problems with VB build 95923 and Symantec EPP 12.1.4112.4156 on Win 7x64 SP1 host):

On all 3 machines that were exhibitting the problem:
I uninstalled VB 4.3.15 build 95923 and reinstalled VB 4.3.15 build 95713, and the problems had gone - VB guests booted up correctly.

So in conclusion it does appear that VB 4.3.15 build 95923 has problems with Symantec EPP 12.1.4112.4156 (on Windows 7 x64 hosts at least).

[planetf1]

After trying to get 4.3.14 to work, I finally found the thread & installed 4.3.15 (add link on download page to thread?)

I can confirm I see the same issue as the previous poster wrt running 4.3.15 with SEP 12 installed. The "creating process" seems to take forever

Virtualbox seems unusable,

[RobBrownNZ]

4.3.15 build 95923 is a bust for me, I'm afraid. It behaved very strangely and I could not boot any VMs with it.

Windows 8.1 x64, Avast! Free 2014.9.0.2021.

I have always upgraded Virtualbox by simply installing over the previous version and then running Virtualbox from the last page of the installer wizard. I did that with 95923, but the Virtualbox manager didn't launch. After waiting a few minutes and looking for it in Task Manager (in case it was just taking a long time), I launched it from the Windows Start menu and it did launch. I tried to start a VM, but there was an error message:

Code: Select all

00:00:02.680155 VMSetError: Implementation of the USB 2.0 controller not found!
00:00:02.680155 Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings

There is a log of this attempted start in the Logs.zip I'm uploading, it's "VBox.log". There's an interesting line in there that says "fHMForced=true - 64-bit guest". The guest is definitely 32 bit.

I realised that I still had the 4.3.12 extension pack loaded, so I tried to update it. This gave an error message:

vb_uninst_extpack.png (11.1 KiB) Viewed 11241 times

I rebooted my PC and was able to remove the extension pack. Then I tried to install the 4.3.14 pack, and got a very similar error to the previous one:

vb_inst_extpack.png (12.41 KiB) Viewed 11241 times

I rebooted again and was able to add the extension pack. Then I tried to start a VM, and got another error (retyping this because of the 3-attachment limit):

Code: Select all

Failed to open a session for the virtual machine Gentoo32.
The virtual machine 'Gentoo32' has terminated during startup with exit code -1073740940 (0xc0000374). More details may be available in 'D:\vm2\Gentoo32\Logs\VBoxStartup.log'.

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

The VBoxStartup.log in 'Logs.zip' is from this attempt.

At this point, I gave up and went back to 4.3.12. Let me know if I can offer any other useful information.

[Montenegrino]

Hi,

I had similar problems with 4.3.14 version, so I upgraded to 4.3.15. version(build 95923), and now I have other problem:
System starts to boot (Ubuntu 14.04., 32-bit), and after finishing all installation steps it shuts down Virtual Box with this message:

problem - message.jpg (30.46 KiB) Viewed 11150 times

Can anyone help how to fix it?

[quiettime]

Test build #7 (think of it as an release candidate): https://www.virtualbox.org/download/tes ... 23-Win.exe

I am on a Windows 7 x64 host and I had the VERR_SUPDRV_APIPORT_OPEN_ERROR with VirtualBox-4.3.14-95030-Win.exe, so I upgraded to test build #7 (above) but I received the same error even after a reboot. The only anti-virus software on this computer is MBAM Premium 1.75.0.1300 with database v2014.09.08.05. I exited MBAM but it didn't help. I checked the Virtual Box DLL list in Process Explorer but I didn't see any foreign DLLs.

I have downgraded to VirtualBox-4.3.12-93733-Win.exe which solves the problem.

[PerseP]

There is something broken with the latest version of VirtualBox 4.3.15 r 95923 when you start a saved vm.
The steps to reproduce are:
- Start a vm with Ubuntu 14.0.4.1 LTS 32 bit desktop with guest additions 4.3.15 and 3d acceleration
- Save the machine state
- Start the saved vm
- Get a black screen that doesn't respond. You have to power down the vm.

My host is Windows 7sp1 64
My guest is Ubuntu 14.0.4.1 LTS 32 bit desktop with guest additions 4.3.15
VirtualBox 4.3.15 r95923

[revere521]

WIndows 7 64bit
Avast anti-virus

Vbox was working with VirtualBox-4.3.15-95713-Win.exe, upgraded to VirtualBox-4.3.15-95923-Win.exe and i am also experiencing the issue where no VMs will start.

I have serveral machines, windows, linux, bsd, android etc. and none will start - the dialog "Creating process for virtual machine "xxxxx" (GUI/Qt)...(1/2)" loads after about 30 seconds and hangs.

The machine never loads, and if i cancel (clicking on the close 'x') the dialog disappears - but an orphaned VirtualBox.exe process remains running that i can not end in the task manager.

Here is an example VboxStartup.log for Mint lnux:

Code: Select all

32dc.32e0: Log file opened: 4.3.15r95923 g_hStartupLog=0000000000000018 g_uNtVerCombined=0x611db110
32dc.32e0: Calling main()
32dc.32e0: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
32dc.32e0: SUPR3HardenedMain: Respawn #1
32dc.32e0: System32:  \Device\HarddiskVolume3\Windows\System32
32dc.32e0: WinSxS:    \Device\HarddiskVolume3\Windows\winsxs
32dc.32e0: ProgDir:   \Device\HarddiskVolume3\Program Files
32dc.32e0: ComDir:    \Device\HarddiskVolume3\Program Files\Common Files
32dc.32e0: ProgDir32: \Device\HarddiskVolume3\Program Files (x86)
32dc.32e0: ComDir32:  \Device\HarddiskVolume3\Program Files (x86)\Common Files
32dc.32e0: '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
32dc.32e0: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBox.exe)
32dc.32e0: supR3HardNtEnableThreadCreation:
32dc.32e0: supR3HardNtDisableThreadCreation: pvLdrInitThunk=000000007767c340 pvNtTerminateThread=00000000776a17e0
32dc.32e0: supR3HardenedWinDoReSpawn(1): New child 32ec.32f0 [kernel32].
32dc.32e0: supR3HardenedWinPurifyChild: PebBaseAddress=000007fffffdd000 cbPeb=0x380
32dc.32e0: supR3HardNtPuChFindNtdll: uNtDllParentAddr=0000000077650000 uNtDllChildAddr=0000000077650000
32dc.32e0: supR3HardNtPuChTriggerInitialImageEvents: uLdrInitThunk=000000007767c340 uNtTerminateThread=00000000776a17e0
32dc.32e0: supR3HardNtDisableThreadCreation: pvLdrInitThunk=000000007767c340 pvNtTerminateThread=00000000776a17e0
32dc.32e0: supR3HardNtPuChTriggerInitialImageEvents: executable[2nd] mapped at 0000000000050000 LB 0xfa000

Rolling back to the last version until the next release candidate.

[J.L.]

Doesn't even start anymore, tried reinstalling.

[cwahlgren]

I can confirm what MikeDiack, planetf1 and revere521 says about test build #7 4.3.15-95923 - a VM doesn't start any longer. The dialog "Starting VM / Creating process for virtual machine..." just hangs at 0%.
I have Windows 7 SP1, Symantec Endpoint Protection 12.1.2100.2093. VB r95733 was the last version that I tested that worked. After reinstalling r95733 VB works again.

[DonC]

I found that 4.3.15 fixed the issue on my system.

[yzT]

is there a 64 bit version of 4.3.15? Because the one linked at the first post is to a 32 bit (working, but I rather 64 bit)

[rrutkows]

Hello, all!
Yet another report/confirmation:
4.3.14r95030 @ Windows 7 x64 Pro host with Trend Micro OfficeScan 11 gave:

Code: Select all

Error relaunching VirtualBox VM process: 5
Command line: '81954AF5-4D2F-31EB-A142-B7AF187A1C41-suplib-2ndchild --comment SZNMT --startvm 2fea2a4a-82d8-4a5f-97d3-550746779dec --no-startvm-errormsgbox' (rc=-104)

Then, after aborting:

Code: Select all

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

With 4.3.15r95923 I'm now able to run my guests, both Windows 7 and Debian, without any errors. If you need any more information, let me know.

Regards,
Rafał