Failed to open a session for the virtual machine

Discussions related to using VirtualBox on Windows hosts.
Post Reply
frimton
Posts: 4
Joined: 16. Oct 2017, 12:08

Failed to open a session for the virtual machine

Post by frimton »

I have been using virtual box 5 for some time in a Windows 10 pro environment with no problem. The virtual machine is a windows XP 32 bit.
Yesterday the virtual machine crashed, possibly as the result of a Malwarebytes or Kaspersky scan, and when I try to load the virtual XP I get the following error message:


Failed to open a session for the virtual machine Virtual XP Clone.

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

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}



When I checked the VBoxhardening log I can see that the VirtualBox DLL did not load.
I attach a copy of the log and hope that someone can guide me into getting the VM to launch successfully.

I have already tried uninstalling and then reinstalling the latest version of virtual box.
Attachments
VBoxHardening.rar
(12.93 KiB) Downloaded 26 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Failed to open a session for the virtual machine

Post by mpack »

Make sure Windows 10 did not helpfully enable Hyper-v for you.

After that, see FAQ: Diagnosing VirtualBox Hardening Issues.
frimton
Posts: 4
Joined: 16. Oct 2017, 12:08

Re: Failed to open a session for the virtual machine

Post by frimton »

Hyper-V is not enabled.
frimton
Posts: 4
Joined: 16. Oct 2017, 12:08

Re: Failed to open a session for the virtual machine

Post by frimton »

I've tried all the suggestions in the FAQ.
The last few lines of the log are as follows:

supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 0) fWinVerifyTrust=1 for '\Device\HarddiskVolume4\Windows\System32\mpr.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a6a40000 'C:\WINDOWS\system32\rsaenh.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a8390000 'C:\WINDOWS\System32\crypt32.dll'
2850.3584: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 0) fWinVerifyTrust=1 for '\Device\HarddiskVolume4\Windows\System32\win32u.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a6a40000 'C:\WINDOWS\system32\rsaenh.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a8390000 'C:\WINDOWS\System32\crypt32.dll'
2850.3584: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 0) fWinVerifyTrust=1 for '\Device\HarddiskVolume4\Windows\System32\gdi32.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a6a40000 'C:\WINDOWS\system32\rsaenh.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a8390000 'C:\WINDOWS\System32\crypt32.dll'
2850.3584: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 0) fWinVerifyTrust=1 for '\Device\HarddiskVolume4\Windows\System32\combase.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a6a40000 'C:\WINDOWS\system32\rsaenh.dll'
2850.3584: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8a8390000 'C:\WINDOWS\System32\crypt32.dll'
2850.3584: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 0) fWinVerifyTrust=1 for '\Device\HarddiskVolume4\Windows\System32\winmmbase.dll'
2850.3584: Fatal error:
2850.3584: supR3HardenedMainGetTrustedMain: LoadLibrary "C:\Program Files\Oracle\VirtualBox/VirtualBox.dll" failed, rc=1790
26cc.2038: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1256 ms, the end);
2e04.325c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2859 ms, the end);


How do I address this?

I am doing an sfc scan at the moment, but I suspect it won't cure this problem.....
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Failed to open a session for the virtual machine

Post by socratis »

Partial logs are anything but useful. Especially the end part... ;)
frimton wrote:Malwarebytes or Kaspersky
Uninstall them. Both of them. Then install each one separately and see who's responsible for the failure. See also if you can add an exception to *not* scan anything VirtualBox related.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
frimton
Posts: 4
Joined: 16. Oct 2017, 12:08

Re: Failed to open a session for the virtual machine

Post by frimton »

I did attach the full log in my original posting.

The SFC did show some corrupted files but was unable to correct them.
I suppose my next step will be to attempt a restore to previous state.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Failed to open a session for the virtual machine

Post by socratis »

frimton wrote:The SFC did show some corrupted files but was unable to correct them.
Start in safe mode. Open the Command Prompt with right-click, Run-as-Administrator. Then run "sfc /scannow".
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply