Windows 4.3.26 Specifically for errors due to Security

[chablis1234]

OS: Windows 8 Enterprise 64 bit

[Flos]

Hi,

I don't know if the issue is related to security, but the situation is that after I applied the latest updates Windows updates from Microsoft, the old 4.3.14 could not start any guests suddenly. Before the updates, it did work. Then I uninstall the 4.3.14, reboot the system and install the 4.3.26, VirtualBox still refuses to start the guests. PS: during whole process, I did not upgrade my antivirus software.

HOST: Windows 7 SP1 32bit with latest updates
ANTIVIRUS: avria free edition
VIRTUALBOX: 4.3.14 and 4.3.26

Regards,
Flos

[moar82]

Hi, After the windows update security I have problems to run all my virtual machines.

After the windows update, windows asked me to update to the latest version of VM, however, It didn't work

Failed to open a session for the virtual machine Debian_1.

The virtual machine 'Debian_1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Bim Bim\VirtualBox VMs\Debian_1\Logs\VBoxStartup.log'.

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

Oracle virtual box 4.3.26-98988

My OS is Microsoft Windows [Version 6.2.9200] aka Windows 8.

The Antivirus protection that I'm running is Avast 2015.10.2.2218

Please help me to find a solution, I've been searching for internet but anything works. Even if I disabled the antivirus.

I can provide further information, thanks.

Attached you will find the screenshots of the error.

[Gord]

Host: 32-bit Windows 8.1
Avira Free Antivirus v15.0.9.504, default install

VBoxStartup.zip

(5.65 KiB) Downloaded 38 times

I encountered a situation where none of my VirtualBox virtual machines would open on my 32-bit Windows 8.1 host. Every one of them failed with

Failed to open a session for the virtual machine <machinename>.

The virtual machine 'pingu' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Gord\VirtualBox VMs\pingu\Logs\VBoxStartup.log'.

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

After researching the problem and trying a number of fixes, including ...

• reinstalling the latest version of VirtualBox (4.3.26),

• removing VirtualBox and installing the previous version (4.3.24),

• removing Windows Update KB3004394

... all without success, I uninstalled Avira Free Antivirus (15.0.9.504) and all of my VirtualBox virtual machines started working. Then I reinstalled Avira Free Antivirus and all of my VirtualBox virtual machines stopped working again.

Point of interest: My roommate has a 64-bit Windows 7 machine with VirtualBox (4.3.26) and Avira Free Antivirus (current version) and it is working fine. Perhaps my 32-bit host has something to do with it?

Updates:

1. Problem still exists with VirtualBox 4.3.27 r99779.
2. Confirmed problem does not exist with 4.3.12.

[F1T4]

Falha ao abrir uma sessão para a máquina virtual Psdlo.

The virtual machine 'Psdlo' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\lucas\VirtualBox VMs\Psdlo\Logs\VBoxStartup.log'.

Código de Resultado: E_FAIL (0x80004005)
Componente: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

zxcsc.jpg (53.71 KiB) Viewed 9590 times

hello good night , I'm in trouble with my virtual box , is giving an error at startup below is the image with the error.

[rtowler]

VBox version: 4.3.27-99378
Host OS: Win 7 Enterprise SP1
Host AV, etc.:
-- McAfee VirusScan Enterprise 8.8.04001
-- McAfee Agent 4.8.0.1500
-- BeyondTrust PowerBroker Desktops Client for Windows 6.5.1.23
-- OPNET Application Capture Agent 3.9
-- Cisco NAC Agent 4.9.0.33

I believe that BeyondTrust might be your problem. I am 99% sure that this is the issue in my environment. I can't confirm until tomorrow but I would suggest uninstalling if you can. For me BeyondTrust wasn't needed anymore, a vestige of days gone by, so the fix was painless once the problem was identified. If you still rely on it, you may be out of luck.

Update: Removing BeyondTrust Power Broker Desktop Client resolved my issue with Virtualbox 4.3.26.

[ScottH]

I just ran into a consistent BSoD in dgmaster.sys whenever I try to start a VM. Where can I find the 4.3.27 test build to see if that eliminates the crash? Apparently my host PC had Digital Guardian installed earlier today. This is in an enterprise environment so removing DG probably isn't an option.

Host OS: 64-bit Windows 7 Enterprise SP 1
VBox version: 4.3.26 r98988

[Gord]

Where can I find the 4.3.27 test build to see if that eliminates the crash?

https://www.virtualbox.org/wiki/Testbuilds

.

[Torchwood]

Well this is certainly fascinating. I have been forced to downgrade my Windows 7 32-bit host to 4.3.12 because of this issue. Here is what I have learned from 4 days of troubleshooting ...

1. Getting failure to launch a VM with VirtualBox 4.3.26, but they all run good on 4.3.12 (apparently some hardening took place beginning with version 4.3.14)

2. There was(were) apparently some bad Microsoft patch(es) ... I have removed these without any improvement.
http://www.infoworld.com/article/291459 ... albox.html
http://www.infoworld.com/article/285911 ... 04394.html

3. Removed Avira Free and reinstalled VirtualBox 4.3.26. VM's launch ok now. But in the startup log I am still seeing plenty of files marked "lacks WinVerifyTrust".

4. Installed Bitdefender Antivirus Free Edition. Got exact same VirtualBox error as with Avira, with an additional initial error prompt to abort.

5. Downgraded to VirtualBox 4.3.12 again. Now happily running with Bitdefender.

My take away here is that something in Windows has been corrupted since the same error affects either antivirus. Perhaps they hook into a DLL somewhere that has been corrupted by a Windows update. The older versions of VirtualBox are apparently un-affected because they are not as security hardened. I guess we will have to wait and see what all the developers figure out regarding how to make this stuff play nice. I'm not holding my breath for a Microsoft fix. My next "patch" will be Windows 10

[Torchwood]

Found this forum thread from 4.3.14 discussing the interaction of the antivirus progs... apparently a known problem since last year.

viewtopic.php?f=15&t=62557

Comment that explains this behavior from Frank Mehnert (Oracle):

"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 "

[ScottH]

Where can I find the 4.3.27 test build to see if that eliminates the crash?

https://www.virtualbox.org/wiki/Testbuilds

Thanks! I'll check it out when I have a chance. I can confirm that 4.3.12 eliminated the BSoD for me.

[mspears90]

When I launch any virtual machine, I wait for about 1 minute then get the following error.

Error:
Error in supR3HardNtChildWaitFor!: Timed out after 60001 ms waiting for child request #1 (CloseEvents). (rc=258)

VirtualBox Error.JPG (19.07 KiB) Viewed 9330 times

HOST OS - Microsoft Windows 7 Ultimate (6.1.7601 Service Pack 1 Build 7601) - Patches up to date as of posting
ANTIVIRUS - Bullguard Internet Security (15.0.301.1)
VirtualBox - 4.3.26 (also tested with 4.3.27, 4.3.24)

MS Update KB3045999 removed

[TZSupport]

OS Information:

Code: Select all

OS Name:                   Microsoft Windows 7 Ultimate
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Product ID:                00426-OEM-8992662-00173
Original Install Date:     18/11/2014, 5:40:02 PM
System Boot Time:          3/5/2015, 12:37:45 PM
System Manufacturer:       System manufacturer
System Model:              System Product Name
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~2788 Mhz
BIOS Version:              American Megatrends Inc. 0610, 8/5/2012

Attached Log file and included hotfixes currently installed

-No AVs installed, Windows Defender disabled, Windows Firewall disabled, full admin access, running the test build

[ScottH]

Where can I find the 4.3.27 test build to see if that eliminates the crash?

https://www.virtualbox.org/wiki/Testbuilds

Thanks! I'll check it out when I have a chance. I can confirm that 4.3.12 eliminated the BSoD for me.

The 4.3.27 test build for Windows that I downloaded this morning also crashes with a BSoD in dgmaster.sys. I tried to attach a memory dump without success.

[frank]

Please could you try the latest Windows test build (>= r100091? It contains a fix which should allow you to install the Microsoft hotfixes which is highly recommended as they contain important security fixes. Thank you!