Windows 4.3.20 specifically for errors due to security

[mpack]

Installed VB 4.3.20 on Windows Vista host; failed to open, attached is the log file 9split in 2) that I hope will help.
As I could not open my database without VB running (Paradox on windows XP) I could not find my forum login details !
Both problems 'solved' by uninstalling VB 4.3.20 and re-installing 4.3.12. However, if an easy fix is available I'll try again.
I will not update VB on my Mac.
Ultimate solution is to replace Vista with Win 7 to avoid need for VB on my PC as Paradox works in Win 7, however, I don't see a reason to pay to have to replace a defective product (Win Vista) !

[Greybeardjsy]

Installed VirtualBox 4.3.20 (install file = VirtualBox-4.3.20-96997-Win.exe) and downloaded the latest Guest Additions as an update from VirtualBox 4.3.12.

Host: Windows 7 (64-bit) Home Premium SP1, AVG Free Edition 2015, running in 16GB RAM
Guest O/S: Kubuntu (64 bit) configured to run in 8GB RAM

Installed VirtualBox OK, but get the following error when trying to start the VM:

NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
(RC=-101)
Make sure that the kernal has been loaded successfully

Followed by a second VirtualBox - Error:

Failed to open a session for the virtual machine Darktable-64
The virtual machine 'Darktable-64' has terminated unexpectedly during startup with exit code 1 (0x1). more details may be available in 'C:\Users\Paul\VirtualBox VMs\New group\Darktable-64\Logs\VBoxStartup.log'.

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

I had previously tried upgrading from a VirtualBox 4.3.12 installation but reverted to 4.3.12 when the upgrade failed in a similar way to above.

Any suggestions on how I resolve the issue would be welcome.

Kind regards, Paul

[JayEm]

After today's windows-updates, none of my virtual machines are starting.

See attached log.

[EugenioLl]

Same issue

Host: Windows 7 64 bit (Spanish)
Guest: Windows XP 32 bit (Spanish)
VB versión: 4.3.20 r96997
Antivirus: Microsoft Security Essentials

Working fine yesterday. With today's Windows updates, my virtual machine isn't starting.

Error message:

Code: Select all   Expand viewCollapse view

Fallo al abrir una sesión para la máquina virtual WindowsXP.

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

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

[scaira]

(4.3.20 - W7) I had the same problem as last 3 posts. I uninstalled KB3004394 - all ok now.

[levamizol]

Same problem here. I've got it working util yesterday. Today after windows updates I've started to receive:

Code: Select all   Expand viewCollapse view

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

on every VM I have, no matter if it's Linux or Windows.
My host is Windows 7 SP01 x64 and Virtualbox is 4.3.20 r96997.
Seems like Microsoft pwned us this time!

PD: Solved by uninstalling KB3004394 Windows update. Thanks to scaira.

[zAfLu]

Version: 4.3.20 r96997

Code: Select all   Expand viewCollapse view

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


Host: Win7 x64 (Pro)
Security: Windows Firewall + ESET NOD32 (Just the Anti-Virus without the Firewall)

[cwaa]

Host: Windows 7 SP1 64bit
virtualbox: 4.3.20 r96997

The VM cannot start since today.
The error in the log file shows C:\Windows\system32\crypt32.dll is rejected during startup.
I tried reinstall virtualbox and got same error.
After that, I found out that crypt32.dll was updated by windows update KB3004394, which was installed this morning.
After uninstall the KB3004394 update, everything seems ok.

[wat]

Host OS : Windows 7 32bit Sp1
Guest OS: XP 32 bit
4.3.20 r96997

Code: Select all   Expand viewCollapse view

Failed to open a session for the virtual machine Windows XP.

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

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





Antivirus microsoft security essentials.

Just reinstalled windows, downloaded the new version of vbox, it worked fine until windows update, and now everything is broken for my vm's.

[Pierre Maurette]

Hi,
Windows 7 x64 host, same problem (crypt32.dll rejected). After reading cwaa's message (thanks), I uninstalled KB3004394, via uninstall program panel, option "uninstall update" (I unvalidated restore feature ). Worked fine. After reboot, the KB3004394 appears again in my "wednesday's updates". Before shutting down, I launched Update Manager and masked the KB3004394. Now I can work, waiting for new Windows' or Virtualbox's patch.

[dethrophes]

vbox stopped working after the latest windows update.

windows 7 . seems to be the same as the rest.
I've inlcuded the log file for reference.

[jonesn]

Virtualbox stopped working (again) on 4.3.18-> 4.3.20

Error is

2970.2998: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll' (C:\Windows\system32\crypt32.dll): rcNt=0xc0000190
2970.2998: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\system32\crypt32.dll'
2970.2998: Fatal error:
2970.2998: Error loading 'crypt32.dll': 1790 [C:\Windows\system32\crypt32.dll]

I've run sfc /scannow . I have SEP 12 installed.
No issues reportde on crypt32.dll by sfc .......

[lcf]

KB3004394 was causing the problem in my case, too (crypt32.dll problem in the log).

Reinstalling VirtualBox with that KB active resulted in errors related to vboxdrv.

Had to re-install VirtualBox after removing KB, and 4.3.20 is running fine, now.

Thanks for the info, scaira, and thanks for morning full of heavy curses, Microsoft.

[Stepa]

For kernel module missed is on Win7 Pro SP1, fully updated

E_FAIL (0x80004005)

NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
(RC=-101)
Make sure that the kernal has been loaded successfully

Confirm to uninstall update KB3004394
Stop install this update at reboot.
Unistall - reboot and install VMBox 4.3.20 working now

Thx.

[pri3006]

Hello,

Yesterday, I upgraded to Virtual box to the latest version (VirtualBox v 4.3.20 r96697), from 4.3.18. After the upgrade I am unable to open any of my VMs (FreeBSD10 , Fedora 19, RHEL)

My desktop's details are:

OS:
Windows 7 Enterprise
Build 7601: Service Pack 1

AV: Symantec Endpoint protection 12.1.5337.5000

VirtualBox version: VirtualBox v 4.3.20 r96697

I see the following error:

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

I have attached the VBoxStartup.log with this post.