virtualbox.org

Continuation of viewtopic.php?f=6&t=64777 for VirtualBox version 4.3.22.

This topic is specifically for Windows users that may still have issues seen in version 4.3.22 caused by security being strengthened.

If you want to be taken seriously you need to post a few items as attachments (compressed is preferred)

• 1) Host OS and version
  2) VBoxStartup.log (zipped)
  3) Mention any host anti-virus, firewalls, protection software, and debugging programs etc which might be relevant.

As in the previous (4.3.14 through 4.3.20) discussions, the purpose of this topic is to gather diagnostic data needed to solve the hardening issues, and nothing else. Wibble posts, opinion posts, and posts that don't include necessary diagnostics will most likely be deleted. If a test build is created then you'll be expected to have tried it before you post.

Please be explicit about errors. Don't say "same as xxxxx". See list above for what's required.

Test builds (when available) can be found here: https://www.virtualbox.org/wiki/Testbuilds


NOTE 12th Dec: if you have a Windows 7 host that started failing in the last few days then this is most like due to buggy Windows update KB3004394. Microsoft have released a fix here. Do not post about your problem until you have tried their fix. While this Windows bug does trip over the VirtualBox hardening feature, it is not caused by it, and therefore is not a problem that should be discussed in this topic.

Hello,
No go with the latest build.

OS - Win7 Professional 64bit - SP1
Trendmicro Office Scan - 11.0.1454
Virtualbox - 4.3.22-98236

Screen shot and startup log attached.

-Richard

I'm still having the same issue with VirtualBox 4.3.22 starting VM guests. I can successfully install and run VM guests on VirtualBox 4.3.12. I have Avecto Privilege Guard 3.8.320 installed on my machine by corporate policy. It looks like the PGDriver.sys driver inserts itself in every executable process to potentially elevate processes like sudo or runas.

If I change the registry setting HKLM\software\Avecto\privilege guard client\HookLoadMethod from 0x3 to 0x2 and reboot VirtualBox 4.3.22 works. Avecto support says that the 0x2 method uses a legacy appinit_dlls method to inject the DLL used for XP and can optionally be used on Win7 but this method is not available on Windows 8 and above. The new PGDriver.sys driver method is designed for Win7 and above. I have submitted a support ticket to Avecto support but it sounds like VirtualBox has needed to make compromises for AV-like security software.

Another side issue is that the VirtualBox.exe process is not able to close and the computer will need to have the power button held for 10 seconds for force the power off.

Host: Windows 7 64-bit SP1
Special security software: Avecto Privilege Guard 3.8.320 installed with HookLoadMethod = 3 which uses the PGDriver.sys driver

I think I have enough information to submit a bug report. How would I do that?

OS - Win7 Professional 64bit
quanjia scan - 10.6.15950.224
Virtualbox - 4.3.22-r98236

Just installed 4.3.22 update.

Critical error during power up of Windows 10 Tech Preview VM. No previous issues under 4.3.20.

Running on Windows 8.1 Pro with Media Center
Vbox.log and VBox.png attached
Running with CCleaner V5.02.5101 (64-bit), AVG Anti-Virus 2015 Free

• Version: 4.3.22 r98236 (PLEASE! Allow version copy in the "About" screen, it is hard to remember all numbers, and if I do "ALT+TAB" window disappear)
• Host: Win8.1, all important updates installed
• Guest: any (even the one I created today)
• Issue: Can't start any VM, even fresh one with no system yet. Pop up window shows up with message below.
• Firewall, Antivirus: none

Failed to open a session for the virtual machine jenkins.

The virtual machine 'jenkins' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\***\VirtualBox VMs\jenkins\Logs\VBoxStartup.log'.

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

OS - Win7 Professional 64bit
avast free 2015.10.0.2208
Virtualbox - 4.3.22-r98236

Win8.1 Pro x64
Bitdefender totalsecurity (n/a i think)
vb 4.3.22 r98236

started right after installing most recent patch tuesday content.

Receiving same error about vboxdrv

Error when starting Windows x64 VM:

"VirtualBox - Error in supR3HardenedMainInitRuntime - RT3InitExec failed with rc=-1912 (rc=-1912)"

followed by a dialog box with the following information:

Failed to open a session for the virtual machine Windows 8.1 x64.

The virtual machine 'Windows 8.1 x64' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'F:\VM\VirtualBox\Windows 8.1 x64\Logs\VBoxStartup.log'.

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

OS: Windows 8.1 with Update x64 (fully updated)
Security software:
1. Kaspersky Internet Security 2015 MR2 15.0.2.361 (latest release version, fully updated)
2. Malwarebytes Anti-Malware (Free) 2.0.4.1028 (latest release version, no real-time protection).

1) Windows 7 x64 SP1
2) In attach
3) Sandboxie, TrueCrypt, Malwarebytes Anti-Malware (Uninstalled long ago but one remaining driver appeared in previous log, deleting it doesn't help)

Other security software previously installed I'm not likely to be able to list one by one.

Can't start any VM with VirtualBox version greater than V4.3.16. The log was created with VirtualBox V4.3.22 r98236.
The issue still remains after applying KB3024777 or after uninstalling KB3004394.

1) Win7 x64
2) Attached
3) McAffee AntiVirus, Windows-Firewall

4.3.22 is Buggy and it is maybe not another bug according to KB3004394.
Because:
I run vbox 4.3.20 until I installed vbox 4.3.22 flawless. I used it to test the W10TP.
With vbox 4.3.20 it runs fine, but after updating/installing 4.3.22 the W10TP did not work any more.
Any other VM did also not launch.

Got this error message, too:
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.

Same attachment as user "nobother"

thx so far
___
DK

Cant run virtualbox 4.3.22 r98236 (with admin rights too - same error)
latest working version is 4.3.12

Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: E_NOINTERFACE (0x80004002)


1) windows 7 x64 pro
2) attached
3) avast internet security 2015 (latest), avast firewall, Malwarebytes Anti-Malware (run on demand), windows defender is turn off

1) Win 7 Ultimate SP1 Rus (all updates until 17th february 2015) x64, 4.3.22.98236
2) See attachment
3) Standard firewall, ms Security Essentials

VM doesn't start.

A (continuing) success story:

On a Windows 8.1 64 bit host (fully patched) running Comodo Internet Security 8.1.0.4426, Virtual Box 4.3.22.98236 is continuing to work correctly. I've run Linux (Mint) and XP (32 bit) guests ok. Comodo seems to have been OK with most of the more recent releases. I will try 4.3.22 with Symantec 12.1 RU5 later today and post results.