virtualbox.org

Hi - I am using the Virtualbox 5.0.6 version and I am trying to run the HortonWorks Sandbox with HDP 2.3. I am getting the below error.


Failed to open a session for the virtual machine Hortonworks Sandbox with HDP 2.3.

The virtual machine 'Hortonworks Sandbox with HDP 2.3' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Documents and Settings\krish\VirtualBox VMs\Hortonworks Sandbox with HDP 2.3\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Post the log the error message mentioned, in a zip file. We'll see what can be done.

Here is the zip file of the log

There's a lot of "Lacks WinVerifyTrust" instances on Windows files. I think this means one of the recent Windows updates that broke the Windows certificate database is on your PC. Take a look through this lllooonnnngggg thread viewtopic.php?f=6&t=67840 I think the bad updates are mentioned in there. Also google this: "windows updates security hardening site:forums.virtualbox.org"

Hi - I just wanted to update that I reverted back to 4.3.12 version as suggested in the forum and re-imported the cloudera VM I was trying before and it imported fine. So I am not sure if the issue that says lacks WinverifyTrust is an issue with Windows update or the newer version of VB or combination of both.

VB 4.3.12 was the last version of VirtualBox that had no hardened security feature. So you lose some security.

The "lacks WinVerifyTrust" problem comes from bad Windows Updates, which prevent good Windows files from passing the security check done by Virtualbox.

4.3.14 & onward have been trying to plug a security hole where malware on the host can inject itself into running Virtualbox processes and get greater privileges & permissions than it could have got on its own, meaning greater potential for damage to the host.

If you run 4.3.12 you will need to keep malware off your host, and the most recent guest OSs won't run. Or you could hunt down the bad Windows updates and run more recent Virtualbox.

As I have a pretty locked down computer from the company, hopefully it is not subjected to lot of malware but its hard to say.
With regards to the bad windows update, how does one go about looking for the bad update as I have about 100 or more updates listed in my update history.

Doing a google search for "bad Windows update" would be one way.

I found this in a recent post from Mpack:

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