Receiving E_FAIL (0x80004005) error when starting VM on Windows 10 Host

[CAndrzejczyk]

Hello,

I'm receiving this error when starting any virtual machine on my Windows 10 host.

Code: Select all

Failed to open a session for the virtual machine S2012R2.

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

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

From browsing these forums for a while I've gathered that this is a hardening error and have tried the steps that people have recommended. So far I've tried:

-Reinstalling VirtualBox with "Run as..." and admin credentials.
-Running an sfc /scannow
-Updating my Graphics drivers
-Searched for any potentially conflicting software - I seem to have none.
-Made sure Hyper-V was disabled/Made sure virtualization was enabled in BIOS.

None of the above have helped me. Attached is my hardening log. Please help.

[ArturoA]

I am facing the same error:

The virtual machine 'Win-7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\Workdir\VM\Win-7\Logs\VBoxHardening.log'.

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

The weird thing is my vm was working fine a couple of days ago, yesterday my computer was updated to Windows 10 version 1803, could this be the root cause for the error?

Please help.

[socratis]

Anyone running the "Trusteer" software? It had an update on 1/Jun/2018 that caused all sorts of issues, and it's kind of difficult to detect...

[mpack]

That is not the same error. The OP has exit code 0xC0000005, the other is exit code 1. The former is a third party DLL crash, the latter is a hardening error, possibly due to what looks like an ancient (Vista era) copy of Avast AV. I would delete this and revert to Windows Defender, which is built into the Win10 host.

Most error messages will include some common words, like "Error". That doesn't make them the same. You need to look at what it says.

Also read FAQ: Diagnosing VirtualBox Hardening Issues.

[CAndrzejczyk]

Not sure if this is directed at me or the other poster but:

I'm not running AVAST on this machine. I've already read the Hardening Issue FAQ, and as it suggested for my error code I attempted to update my graphics driver. Still having the exact same error though.

[mpack]

My post was directed at the user who believed he had the same error, i.e. ArturoA. As I said, the two scenarios are clearly not the same.

[ArturoA]

I have both Truster and Avast, and they were enabled and running a couple of days ago when my VM was executed the last time, I disabled both but my vm still has the issue, the only difference is my Windows 10 was updated, after that my VM started crashing.

[andyp73]

I have both Truster and Avast, and they were enabled and running a couple of days ago when my VM was executed the last time, I disabled both but my vm still has the issue

Sometimes (actually most of the times) disabling is not enough, you need to uninstall the antivirus.

If by "Truster" you mean IBM's "Trusteer Rapport" then there was an update to it at the beginning of June that breaks VirtualBox. They are aware of it and hopefully will be fixing it soon.

-Andy.

[althetaff]

I have both Truster and Avast, and they were enabled and running a couple of days ago when my VM was executed the last time, I disabled both but my vm still has the issue, the only difference is my Windows 10 was updated, after that my VM started crashing.

Disabling Trusteer didn't work for me. Once I uninstalled it my VMs worked again so uninstall it and try again.

[benhuynh70x7]

turn off the Core isolation Memory integrity; turn off all Hyper-V feature.

1). turn off Core isolation. 2). turn off memory integrity
Settings/Update & Security/Device security/Core isolation

you cannot turn off from here, have to edit the registry

run DOS< (CMD) as Administrator

>regedit

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Enable DWORD

0=off
1=on

exit and reboot computer

[mpack]

I was hoping it would quickly pass, but it looks like I need to call a halt to discussion of ArturoA's problems here. If your post does not concern CAndrzejczyk's question then please do not post it here. It is not fair to hijack the OPs topic for a discussion after it has already been pointed out that the problem is not the same. Any more posts which do not directly address CAndrzejczyk's problem will be deleted.

[CAndrzejczyk]

turn off the Core isolation Memory integrity; turn off all Hyper-V feature.

1). turn off Core isolation. 2). turn off memory integrity
Settings/Update & Security/Device security/Core isolation

you cannot turn off from here, have to edit the registry

run DOS< (CMD) as Administrator

>regedit

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Enable DWORD

0=off
1=on

exit and reboot computer

Neither of these are applicable to my machine.

I was hoping it would quickly pass, but it looks like I need to call a halt to discussion of ArturoA's problems here. If your post does not concern CAndrzejczyk's question then please do not post it here. It is not fair to hijack the OPs topic for a discussion after it has already been pointed out that the problem is not the same. Any more posts which do not directly address CAndrzejczyk's problem will be deleted.

Thank you.

[mpack]

@CAndrzejczyk: As a concrete suggestion for you, I suggest that you start by uninstalling "Cylance Protect" (search for that phrase in these forums to see why), and let us see where that takes us.

[CAndrzejczyk]

@CAndrzejczyk: As a concrete suggestion for you, I suggest that you start by uninstalling "Cylance Protect" (search for that phrase in these forums to see why), and let us see where that takes us.

I don't have that software installed.

[andyp73]

I don't have that software installed.

The VBoxHardening.log file you attached to your original post seems to indicate differently:

20.1ff0: supR3HardenedWinFindAdversaries: 0x8000
20.1ff0: \SystemRoot\System32\drivers\cyprotectdrv64.sys:
20.1ff0:     CreationTime:    2018-05-23T19:59:24.414394000Z
20.1ff0:     LastWriteTime:   2018-05-23T20:02:57.062035800Z
20.1ff0:     ChangeTime:      2018-06-07T19:27:44.221211100Z
20.1ff0:     FileAttributes:  0x20
20.1ff0:     Size:            0x31c18
20.1ff0:     NT Headers:      0x100
20.1ff0:     Timestamp:       0x5a999742
20.1ff0:     Machine:         0x8664 - amd64
20.1ff0:     Timestamp:       0x5a999742
20.1ff0:     Image Version:   6.1
20.1ff0:     SizeOfImage:     0x132000 (1253376)
20.1ff0:     Resource Dir:    0x130000 LB 0x2f0
20.1ff0:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
20.1ff0:     [Raw version resource data: 0x130060 LB 0x28c, codepage 0x0 (reserved 0x0)]
20.1ff0:     ProductName:     CylancePROTECT
20.1ff0:     ProductVersion:  2.0.1480.21
20.1ff0:     FileVersion:     2.0.1480.21
20.1ff0:     FileDescription: Cylance Protect Driver

-Andy.