Failed to open a session for the virtual machine

[sinancetinkaya]

* Failed to open a session for the virtual machine Arch.

The virtual machine 'Arch' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'H:\FTP\VirtualBox VMs\Arch\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} I have tried 4.3.26, 4.3.28 and latest beta 5.0 RC1. I don't have KB3004394 installed. To be sure, I have installed KB3024777 as well I can't start any VM at all.

[bird]

CreateProcessW fails with ERROR_ACCESS_DENIED (5), same as #14873. No immediate clue yet.

[okomarov]

I am on: OS Name Microsoft Windows 7 Enterprise Version 6.1.7601 Service Pack 1 Build 7601

If I install VirtualBox (5.1.24 or 5.0.40 or 4.3.40) and launch the VM, it works (see VBox.log, attached).

After I restart the laptop, and try to srtat the VM, I get the following error:

---

VirtualBox - Error In supR3HardenedWinReSpawn

---

Error relaunching VirtualBox VM process: 5 Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment lubuntu --startvm 416e702c-7f80-4dad-b0ba-9f485bdb75de --no-startvm-errormsgbox "--sup-hardening-log=C:\Users\Oleg\VirtualBox VMs\lubuntu\Logs\VBoxHardening.log"' (rc=-104)

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.

---

OK

---

Failed to open a session for the virtual machine lubuntu.

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

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

See the attached VBoxHardening.log.

[Kgops]

I am also experiencing this Error

"Error relaunching VirtualBox VM process: 5 Command line: .....

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name."

This chapped after upgrading to the latest version of Windows 10 on my Host machine. is there a Solution to resolve this, as i am on the latest version of VirtualBox_5.2.12 Please help

[Kgops]

I am also experiencing this Error

"Error relaunching VirtualBox VM process: 5 Command line: .....

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name."

This chapped after upgrading to the latest version of Windows 10 on my Host machine. is there a Solution to resolve this, as i am on the latest version of VirtualBox_5.2.12

[Socratis]

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...

If you recently updated your Trusteer software, it's a known problem with Trusteer.

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums. 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 most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

[fth0]

Replying to bird:

CreateProcessW fails with ERROR_ACCESS_DENIED (5), same as #14873. No immediate clue yet.

I've seen several cases like this one in the forums, where the hardening log is not showing any adversary before or during the failing CreateProcessW call. Wouldn't it be useful to additionally output g_wszSupLibHardenedExePath as part of the fatal message? ;)