Windows 7 Virtualbox 4.3.26 Failed to open a session ...

[Torchwood]

Windows 7 Virtualbox 4.3.26 "Failed to open a session for the virtual machine". But fallback to VirtualBox 4.3.12 works perfectly. I tried 4.3.16 and got exactly the same error message as in 4.3.26 every time (see attachment).

I built these VMs on my linux box, using VirtualBox 4.3.10, which is where I primarily host them. I love VirtualBox. I thought it would be useful to be able to run them on my Windows host. So this weekend I copied the VMs over and downloaded the latest binary of version 4.3.26 for Windows. The first launch gave me this error immediately. I chose "Run as Administrator" for the install, and set the VirtualBox manager to "Run as Administrator" as well. No difference. All my VMs failed with the error.

So I decided to try VMware player as a comparison. After exporting them from my Linux host as .ova files and importing to VMware, they worked fine. Well and good, but I just really prefer to use VirtualBox and was determined to make this work. The exporting and importing is tedious, not to mention you have to install a new flavor of guest additions ... ugh!

I would really like to understand what is causing this issue. But for now, I will keep running 4.3.12 until something else works.

Error Message

VirtualBoxError.jpg (38.98 KiB) Viewed 1929 times

[mpack]

Google for " "lacks winVerifyTrust" site:forums.virtualbox.org".

[Torchwood]

Hey mpack, thanks for pointing me in the direction of the security thread!

I saw that earlier, but hesitated to add to it - not sure if my problem fit that category - based on my generic error message and a Vboxstartup log that I have no experience interpreting.

After your comment, I opened the log in a text editor and did a search for "lacks winVerifyTrust" (as well as on google) ... got a lot of files logged in there that "lacks winVerifyTrust".

Since I just recently installed VBox on Windows, I have no history to compare when working vs not working against my Windows update history. So I went ahead and pulled the two most likely "Evil" Windows updates, (based on other forum members posts) KB3004394 and KB3045999. Rebooted and upgraded VBox to 4.3.26.

Got the same error as before... Something must be messed up in Windows 7. Maybe one of the updates made a persistent change somewhere. System File Checker sfc /scannow runs clean.

Downgraded to VBox 4.3.12 and it's running well ...

Thanks again for your help. I think the only logical choice now is to run as is and clean install the host to Windows 10 when it is RTM. Then convert my existing Win 7 partition into a VM

[Muthu]

I have also faced a similar problem while launching VM(4.3.18) in windows 7 machine. While launching the VM, its not responding, the screen looks freezed.

VBoxStartup.log

Log file

(30.58 KiB) Downloaded 6 times

Freezed screen

Capture.PNG (77.92 KiB) Viewed 1855 times

So, I have hard closed the VM and opened it again, the start menu is in disabled state, then found that it is because of process not getting killed.

Freezed screen

Capture.PNG (77.92 KiB) Viewed 1855 times

I tried to kill process, but its not happening. so I tried to restart the machine, but machine is not shutting down. I tried hard shutdown but still the process is live.

Pls, give us a soution to overcome it.

[mpack]

Yes, lots of people running Win7 (especially 32bit versions) will have this problem, ever since a Windows Update corrupted the certificates database on the host.

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

[Torchwood]

I follow Woody's articles in InfoWorld on a regular basis. Great advice, usually. He maintains a Windows Patch Defcon Status on his web blog askwoody.com ... typically my first stop before Monthly Patch Tuesday. I am very conservative about applying Windows patches and keep automatic updates turned OFF. It's ironic that I got bitten somewhere down the road, as I ususally wait several weeks or months for the Microsoft patch fallout to settle before applying patches.

One of Woody's latest below mentions VBox from InfoWorld | Apr 27, 2015 ... like his astute comment at the end ...

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

"(I figure it’s another case of the cure being worse than the disease. KB 3045999 fixes an escalation of privilege vulnerability that only applies if the bad guys have already logged into your computer, and are able to run a program they devised. There’s a reason why it’s listed as “important.”

In Windows update land, where crying wolf seems endemic, "important" usually means "not very important.)"

Lol, if somebody else can log into your system, then you definitely have bigger problems!

[RGK]

I am using Virtual Box 4.3.26 r98988. I am getting the following error. Please see attachment.

Vbox failed to open

Vbox error.png (105.95 KiB) Viewed 1770 times

Failed to open a session for the virtual machine Hadoop.

The virtual machine 'Hadoop' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\rajk10\VirtualBox VMs\Hadoop\Logs\VBoxStartup.log'. { Nothing written to Log}

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

[mpack]

I'm going to lock this thread, since it seems to be morphing into a redundant duplicate of the existing Security Issues topic.