VirtualBox 6.0.2 E_FAIL (0x80004005)

[MyNameIsBob]

I have recently decided to update from VirtualBox 5.2 to the latest version (6.0) and now whenever I try to start a virtual machine it says:

Code: Select all

Failed to open a session for the virtual machine Windows 10.

The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\staples155\appdata\roaming\Windows 10\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Before making this post I looked around the forum and a lot of people recommended checking This FAQ
I tried all the steps on there but none of them worked. I have attached a zipped copy of the hardening log and an image of the error.

[socratis]

'C:\Users\staples155\appdata\roaming\Windows 10\Logs\VBoxHardening.log'

Do you maybe have an explanation on how you ended up having the VM in the AppData directory? This is highly unusual...

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

I would start by uninstalling Kaspersky and Malware Bytes:

95b8.724c: \SystemRoot\System32\drivers\klflt.sys:
95b8.724c: \SystemRoot\System32\drivers\klif.sys:
95b8.724c: \SystemRoot\System32\drivers\klkbdflt.sys:
95b8.724c: \SystemRoot\System32\drivers\klmouflt.sys:
95b8.724c: \SystemRoot\System32\drivers\kneps.sys:
95b8.724c: \SystemRoot\System32\drivers\MBAMSwissArmy.sys:

[MyNameIsBob]

Hello,

First of all, I have no idea how the VM got to AppData. I used the normal VirtualBox installer and I didn't change anything.
Second, I don't have Kaspersky or Malwarebytes installed, I have uninstalled that software a long time ago since I use Bitdefender now. I also tried disabling Bitdefender and starting the VM but it still gave the same error.

Edit: I have deleted those DLLs since I didn't have Kaspersky or Malwarebytes installed and I still get the same error.

[socratis]

I also tried disabling Bitdefender

Uninstall, don't disable. Even after uninstalling, some things do NOT get uninstalled, and they're still running as you saw. I didn't know that you had Kaspersky or MalwareBytes uninstalled, they were loaded.

I have deleted those DLLs ... I still get the same error.

A new ZIPPED VBoxHardening.log would help...

[MyNameIsBob]

Hello,

I have attached a new zipped hardening log below.

[AKR]

I have two hosts PC (first) and a laptop (second). On both Windows 10 1809 and KIS 2019, and a similar set of software.
On the second (laptop), everything works fine after upgrading from 5.x to 6.x.
But on the first (PC), all virtuals do not start. It gives the same error.
Log file VBoxHardening.log in the attachment.

VBoxHardening.log

(24.72 KiB) Downloaded 413 times

Please help me understand what is the reason.

[andyp73]

Please help me understand what is the reason.

I would start with Kaspersky as it is listed in the known adversaries. It would have helped if you had posted the same log file from the working host then we could have compared.

-Andy.

[oppiman]

same here, VBox does not like the Trend Micro AV dlls.

hardening log showed several TrendMicro dlls as "adversaries"

I have excluded
VirtualBoxVM.exe
VboxSVC.exe
VBoxSDS.exe
VirtualBox.exe
from "Behavior Monitoring".

This fixed the issue.

[mpack]

What? Someone who actually did some research, read one of the zillion identical forum reports and went ahead and fixed the problem themselves? I'm shocked to the core!

[MyNameIsBob]

I still need help.

[TKV]

I had the same error, and it seems stupid but I started it with decoupled window and it worked.
use google translate for this

[socratis]

but I started it with decoupled window and it worked

What does that even mean, can you give some more details?

use google translate for this

For what? Translate which part exactly?

[daz]

I fixed the issue by downloading the VB and selecting "repair" option.