Failed to open a session for the virtual machine

[slattdog]

Fresh install of Windows 10. Fresh install of VB 5.1.2 Created a default Ubuntu x64 VM using Ubuntu 16.04 .iso When I try to start the VM I get the following error:

Failed to open a session for the virtual machine Xerus.

The virtual machine 'Xerus' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\brad\VirtualBox VMs\Xerus\Logs\VBoxHardening.log'.

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

I have created a default Win7 VM and get the same result when trying to start it.

[Sachin]

I am having the same issue: Host: Windows 7 Entprise, x64 Guest: OEL 6.5 x64 The virtual machine 'SampleAppv506p' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\xxxx\VirtualBox VMs\SampleAppv506p\Logs\VBoxHardening.log'.

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

---

[Sachin]

file add by Sachin -

[Conan76]

I've got same problem with version superior 5.0.20 r106931

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine ...

Virtual machines are save on network (NAS Synology DS1813) but mounted on (Core i7 3820 / 16Go) Problem present with tested with Shared network

DS1813\MachinesVirtuelles Or mounted network drive V:\ (
DS1813\MachinesVirtuelles)

Tested with existing virtual machine (Win7 X64 / Visual Studio 2015) and same on new machine creation.

Thanks for help.

[Ityer]

Running a headless start and then showing works for me

[dexter1988]

Help me!!!

[Frank Mehnert]

Please reopen if still relevant with VBox 5.1.22.

[AnchoDotto]

Started happening to me on 5.1.20, still happening after installing 5.1.22.

Attaching VBoxHardening.log for reference.

Thanks a lot.

[DAC_]

Happens for me still after moving up to 5.1.26 r117224 (Qt5.6.2). Happens only for one of my VMs. Started happening after I moved the VM folder to a different machine. Log attached.

[DAC_]

I recant the "Happens only for one of my VMs.". Something changed on my machine & now all attempts to start VMs fail (even ones I just created).

[Socratis]

Two lines before the end of VBoxHardening.5.log, you can see this:

2ee4.3390: Fatal error:
2ee4.3390: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\WINDOWS\System32\SHELL32.dll' / '\??\C:\WINDOWS\System32\SHELL32.dll': 0xc0000190

• Do you have any custom themes installed?
• Try to run "sfc /scannow" from an elevated Command Prompt.
• Please read the following FAQ: ​Diagnosing VirtualBox Hardening Issues.

[Raven7886]

I had the same error after some Windows 10 Updates...... Update Virtual Box.. Just download Latest and greatest and install... Boom! Works.

[rkaiser0324]

I confirm what Raven7886 said. I did a bunch of Windows 10 updates today, for the first time since 9/1/17, and got this error upon launching my VM. So it was something in that batch.

Updating to VirtualBox v5.1.30 fixed it.

[schelian]

Raven7886 & rkaiser0324's solution worked for me. Previously had 5.1.22.

[malcolm]

I'm still having this problem on 5.2.22 r126460(Qt5.6.2) -Any help troubleshooting this would be helpful and appreciated.

Failed to open a session for the virtual machine ubuntu-18.04-desktop-amd64.

The virtual machine 'ubuntu-18.04-desktop-amd64' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\DefaultMachineFolder\ubuntu-18.04-desktop-amd64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

[Socratis]

malcolm
t's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

For example, this is a Hardening issue. This is not a bug and someone from the developers has to deal with it and close it as "Invalid".

Which they should have done the moment it was reopened, 16 months ago... ;)

[morgan412]

VBOX Log

[morgan412]

i am having same error i am on vbox 5.1.0 this is the code. Failed to open a session for the virtual machine Windows 95 Test.

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

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

[Socratis]

@morgan412

Just out of curiosity, did you read the post just right above yours? The last post before you posted?

2060.37f8: Log file opened: 5.1.0r108711 g_hStartupLog=0000000000000068 g_uNtVerCombined=0xa042ee00

In your case, you're using a way too old of a VirtualBox version. Please update to the latest before testing it again.

[Azhang]

Log from Azhang Jan 17,2019

[Azhang]

@socratis,

I've upgraded to vbox 6.0.0, problem is still there. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976} Sorry I don't understand your comment "someone from the developers has to deal with it and close it as "Invalid".". log is attached.

[Socratis]

@Azhang

What I'm saying is that it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid", because you have a "Hardening Issue".

Please read really carefully the following FAQ: ​Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement as to which program might be responsible...