Windows 4.3.20 specifically for errors due to security

[Greybeardjsy]

Having had the same problem with VirtualBox 4.3.20 not working, I followed the advice above and removed KB3004394, uninstalled VirtualBox 4.3.20, restarted the PC and then reinstalled VirtualBox 4.3.20.

All now seems OK - thanks for the suggestion (scaira)

Interesting though, that my problem occurred before KB3004394 was installed by Windows update...

Regards, Paul

[OlivierJ]

Win7 Pro SP1, fully updated
Virtualbox 4.3.20 r96997

Same problem as above: crypt32.dll not loaded

Have removed the MS update KB3004394. Then reboot.
Seems Ok now.

Regards
O.

[tstolik]

thanks, uninstall KB3004394 repair my problem.

I think will be a new update from virtualbox quickly

[pri3006]

As a followup to my earlier post, the following is the error that I see in the VBoxStartup.log:

1b34.d4c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]

And, I do not see the KB3004394 installed on my Windows 7 though.

[rbrooke]

Installed Windows updates this morning and it broke VBox as with many other users.

Win 7 Ultimate 64bit
VBox 4.3.20
Avast AV

After installing Win update noticed a lot of new/strange behaviours, e.g. unlocking bitlocked drive triggered UAC warnings, ditto in task manager when clicking on 'show processes from all users', and other stupid stuff.

Saw the advice above re. KB3004394. Googled this update - lots of unhappy people reporting similar UAC issues (suspect this is what is troubling VBox). Looks like MS screwed up again with this update.
Following the advice earlier in this thread I removed KB3004394 and did all the rebooting/uninstall&install of VBox. Everything now OK.

For Win8/8.1 I guess there is probably an update applying similar functionality that need removing.

Thanks to the user who identified the problematic update

[Jacob Klein]

For clarity...
We don't yet know if the fault of the problem is with Microsoft's patch(es), or with Oracle's hardened security implementation found in VirtualBox 4.3.14+. My bet is that this is on Oracle to fix.

The patch resulting in the problematic behavior:
KB3004394 - December 2014 update for Windows Root Certificate Program in Windows
http://support.microsoft.com/kb/3004394

Also, from what I was reading, the following rollup looks to include that Root Certificate KB, so installing it will likely result in the same problematic behavior:
KB3013769 - December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
http://support.microsoft.com/kb/3013769

I personally did not have any problem starting my VMs on Windows 8.1 x64 after installing both patches. So, the issue might actually involve some other component as well.

Regards,
Jacob

[EBrio]

I am a novice at this but needed assistance with my vms that suddenly stopped working.
They were working yesterday and this morning stopped.
I have 1 x32 and 1 x64 Windows 7 both have the same issue.
Failed to open a session for the virtual machine Windows 7 Ent 32bit.
The virtual machine 'Windows 7 Ent 32bit' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: E_FAIL (0x80004005)

VirtualBox Ver. 4.3.20
I have no AV installed (yet)
Host machine is Windows 7 64bit 16GB RAM just imaged with AV
No other issues on the system

[sunboy]

Installing KB3004394 crashes the local certificate store.
So verifying of dll and exe do not work anymore.
This crashe Vbox but also the entire MMC, which now needs an Admins Click to run.

It is assumed the MS will deliver a new, fixed KB3004394 for KB3004394...

Why crypt32.dl was changed?
Because NSA wants to be able to change the root ceritificate in 2*24 hours back and fore, not requiring twice a week to swap...


AFAIS: This is not a problem related to the Vbox security checks or oracle can fix.
There is already an other thread for that

[herrmeier]

Situation:
On a windows 7 prof.-host, virtualbox 4.3.20 r96997 is installed, running two vms.
Last night at 3:11 a.m., windows auto-update decided to reboot.
Virtualbox does not seem to have shutdown smoothly the two running vms, one beeing ubuntu 14.04 server, one beeing Windows XP.
Now both VMs don't start again.

Do you have any clue, how I could save my settings and work on those two VMs.
What I've read so far does not seem to be very promising.

What I want to do is to copy the vdi-files and use them with different new VMs.

Now I have two questions:
1. Is there a way to make sure, VMs are shutdown smoothly before a windows 7 reboot
2. Is there a way to recover those VMs?

The error translated from german into english is:

The virtual Machine >>VM-Name<< could not open a new session.

The virtual machine >>VM-Name<< has terminated unexpectedly during startup with exit code 1(0x1). More details may be available in C:\Users\username\VirtualBox VMs\>>VM-Name<<\Logs\VBoxStartup.log.
error code: E_FAIL (0x80004005)
component: Machine
Interface: IMachine {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}

VBoxStartup.log reads ends with:

1208.179c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\crypt32.dll
1208.179c: Error (rc=0):
1208.179c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=5 \Device\HarddiskVolume3\Windows\System32\crypt32.dll
1208.179c: Error (rc=0):
1208.179c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll' (C:\Windows\system32\crypt32.dll): rcNt=0xc0000190
1208.179c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\system32\crypt32.dll'
1208.179c: Fatal error:
1208.179c: Error loading 'crypt32.dll': 1790 [C:\Windows\system32\crypt32.dll]
16d8.de8: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 143 ms, the end);
1110.56c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 745 ms, the end);

I deinstalled KB3004394, but it doesn't seem to help yet:
https://forums.virtualbox.org/viewtopic.php?p=306551#p306551

UPDATE: After a reboot of KB3004394 virtualbox started just like before! Thank you very much!!!

Before I do anything else I'll backup the vdi-files. Thank you in advance!

[notleavingwithoutmyRAM]

+1 worked for me too. The MS update(s) was the problem.

1) Remove MS update KB3004394
2) Uninstall VirtualBox v4.3.20 (VB wouldnt start properly after that)
3) Restart
4) Re-install VirtualBox.

-
And for those wondering what KB3004394 was for:

About this updateThe Windows Root Certificate Program enables trusted root certificates to be distributed automatically in Windows. Usually, a client computer polls root certificate updates once a week. After you apply this update, the client computer can receive urgent root certificate updates within 24 hours.

- Doesnt seem like a big loss for most people.

[mpack]

Guys, I think there has been enough chat about the KB3004394 issue. It seems that this is not a VirtualBox "security" bug and hence discussion does not belong here. Sure, it's useful to draw folks attention, but I'd say that's been done now.

[Edit] "Bird" mentions in another thread that the issue affects Win7 hosts only (not Win8.x), and is caused by failure to include a catalog file on that host. The resolution is to uninstall the KB3004394 update and await a fix from Microsoft. Now that it's been definitively determined not to be a VirtualBox bug, I won't be allowing any more posts about it here.

[rwardfmc]

I'm working with VirtualBox for the first time.
I'm trying to install Ubuntu 64 bit.
After creating the virtual machine, it won't start.
Can you give me any advice on how to resolve this issue?

Thanks

Rich Ward

screenshot attached.

Machine is Dell T3600, running windows 7 64 bit, sp1.
McAfee antivirus installed.

Failed to open a session for the virtual machine rw linux.
The virtual machine 'rw linux' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\rward\VirtualBox VMs\rw linux\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

[mviara]

Virutal box 4.3.20 on Windows 7 do not start. Before I have use it for months.

[Niels C. (UK M2M)]

Hi,

I cannot start my VM, and am therefore halted.
I get this message:

Failed to open a session for the virtual machine CentOS 5.6 Nov13.

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

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

My host system is:
Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
Dell Precision M2800
Intel(R) Core(TM) i7-M4810MQ CPU @ 2.8GHz, 2801MHz, 4 cores, 8 logical processors

Best regards
Niels

[mpack]

People: if you have a Windows 7 host then uninstall the KB3004394 update. Do not post about your problem until you have tried that.