After installing the first test build I was able to start Virtualbox. After the the second one I was able to start the vms. But the performance compared to 4.3.12 is worse.
I can confirm the newest build VirtualBox-4.3.15-95226-Win.exe works for me on Windows 7 SP1 x64, with Symatec Endpoint 12.1.4100.4126, but NOT with Comodo Internet Security 7.0.317799.4142.
Message when running on Comodo:
Failed to open a session for the virtual machine XP.
The virtual machine 'XP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\Mike\VirtualBox VMs\XP\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
BUT:
Like others I've noticed two problems with the 2nd 4.3.15 test build.
SIGNIFICANT PROBLEM:
1) Running a Windows 7 SP1 x86 Guest on the Win 7 SP1 x64 Host (Symantec Endpoint Protection) - the guest Win 7 PC very rarely boots successfully and the guest Win 7 PC often hangs during shutdown (which also hangs virtualbox - needing a reboot of the host machine!). Note - it doesn't seem to happen for XP guests on the host PC.
SMALLER PROBLEM/ANNOYANCE:
2) It is taking longer for the VM's to go to their virtualbox BIOS (i.e. slower startup)
The "Failed to install ntCreateSection monitor" message is gone with the latest VBox Test Builds. But my VM does not start. I probably have a special VM (no VMDK / VDI, but a USB Thumbdrive which contains the data) though.
Failed to open a session for the virtual machine FedoraUSB.
The virtual machine 'FedoraUSB' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'S:\VirtualBox VMs\FedoraUSB\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
I directly installed Fedora on my USB drive through VB and use that to boot the VM. I hope the attached log helps.
They missed it because apparently their testing machines are clean to the extent of not having NVIDIA drivers installed. Or did those specific DLL injections ever cause a crash? Well they clearly didn't test compatibility with antivirus and other common products. P.S. It's a feature, not a bug.
Anyhow, progress update on Avast and hopefully other issues I've reported? New builds ETA if any?
I installed VirtualBox-4.3.14-95030-Win.exe on my Windows 7 Ultimate SP1 x64 machine which is running Comodo Internet Security Premium 7.0.317799.4142.
The VirtualBox installation completed without any problems. But when I click the Oracle VM VirtualBox shortcut in my Start menu I get a "Error In supR3HardenedWinInstallHooks" error saying: "Failed to install NtCreateSection monitor". I've attached a screenshot of the full error message.
I said earlier of the 2nd test build: VirtualBox-4.3.15-95226-Win.exe
SIGNIFICANT PROBLEM:
1) Running a Windows 7 SP1 x86 Guest on the Win 7 SP1 x64 Host (Symantec Endpoint Protection) - the guest Win 7 PC very rarely boots successfully and the guest Win 7 PC often hangs during shutdown (which also hangs virtualbox - needing a reboot of the host machine!). Note - it doesn't seem to happen for XP guests on the host PC.
However, I've now noticed that this hang on shutdown ONLY seems to occur if I have the 4.3.15 guest additions installed for the Win 7 SP1 x86 Guest (configured to run the WDDM drives for Aero support). If I uninstall the guest drivers - the hang on shutdown problem (for the guest) goes, if I reinstall the guest drivers, the hang on shutdown problem (for the guest) reappears.
mpack wrote:How much of this thread did you read before posting? E.g. the first post gives a link to a new build for you to try.
All of it. But I did make one mistake in my post - I installed 4.3.15-95226 and not 4.3.14-95030 as I indicated in my post. Sorry about that. I'll rollback the installation and reinstall everything (using 4.3.15-95226).
I am using win 8.1 update 1 and facing similar problem. I tried installing 4.3.14, and 4.2.26 and still facing the problem. I am using avast and will be trying 4.3.12