virtualbox.org

Hello,
I am using VB since a few years.
I created some vdi's, which were working perfect.
The host system is WIN7 32bit professional.
After updating Windows (and maybe after updating VB, im not shure), I am unable to start these former working vdi's.

These errors occur:
Für die virtuelle Maschine WINXP_Virtual_Box_4 konnte keine neue Sitzung eröffnet werden.

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

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

I tried to deactivate the real time scanner from Avira (free) and to shut down private firewall,
which did not help.

Do you have any idea how to get VB working again?

This would help a lot.

Thanks a million and best regards

Harald

There have been a number of Win7 updates in recent times which trashed the host certificates database which VirtualBox checks to ensure that all running DLLs are not malware.

KB3004394
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html

KB3045999
http://www.infoworld.com/article/291459 ... albox.html

A short term workaround is to revert to VirtualBox 4.3.12, which is the last version which doesn't do the checks. A better solution would be to repair the damage to your host.

Hello,
thanks for your reply!
"A better solution would be to repair the damage to your host."
How can this be done?

Best regards

Harald

Sorry, that's a Windows support question, and since I've never had the problem I don't know the answer anyway. The articles I linked you to will no doubt suggest some solutions, plus there's the "short term workaround" I mentioned.

Hello,
I made a downgrade to VirtualBox 4.3.12, which is working perfect.

It makes me really afraid, that neither Microsoft nor Oracle is able/willing to fix such a obviously widespread severe bug.

Best regards

It's not a bug, at least on Oracle's part. Poke back through the forum and you'll see that right after 4.3.12 came out someone found that there was a way to get processes running on a PC which also had Virtualbox running to have greater privileges to do stuff than the processes would have had, by injecting the processes into the running Virtualbox processes. Antivirus and video drivers do this legitimately, which is OK. Malware can do this, too, which really put the wind up the Virtualbox developers. Since then the devs seem to have settled on testing if a process is signed by a trust certificate before the process is allowed to inject itself into Virtualbox. Most good programs can get a signed certificate, meaning Virtualbox will be happy with those processes. Some programs, like theme changers, won't or can't get a certificate, meaning Virtualbox won't work until those programs are removed or get signed. If malware ever finds a way to get a certificate, well, that may be a cluster-cuss of epic proportions...

Microsoft, though, seems to have not been as careful as they ought to have been lately about releasing updates that break the trust certificates on core Windows processes, meaning Virtualbox can't tell if the Windows processes are genuine or not. So Virtualbox doesn't run. Microsoft can be brought to see they have made mistakes, as one can see when reading back over the issue (see all the "version 4.3.## errors due to security" posts). Later Microsoft releases an update that fixes the trust certificates, then they release another update that breaks them again.

This is a work in progress. Oracle and all the Virtualbox users are eager not to have their efforts in developing Virtualbox go down the tubes, but the malware guys are making it difficult. Patience is needed. In your situation you may have some of the broken updates still on your PC. Thus mpack's posted links may help. Otherwise, 4.3.12 will get you going, unless you want to run more recent versions of Linux. Just be sure your host remains free of malware.