virtualbox.org

Host:windows 10 x64
virtualbox version: 5.0.10
Some time ago, I created two VMs, windows 7 and ubuntu 15.10, on virtualbox 5.0.10, they all worked smoothly. but today, when I started any of them, the virtualbox told me the virtual machine was failed to be opened.

the first popup message:
Error relaunching VirtualBox VM process:5
Command line:'60eaff78-4bdd-042d-2e72-669728efd737-suplid-3rdchild --comment Ubuntu 15 --startvm 3a4ee6cd-d86d-4fb2-900d-c966c78993ae --no-startvm-errormsgbox "--sup-hardening-log=c:\users\future\virtualbox vms\ubuntu15\logs\vboxhardening.log" ' (rc=-104)
where: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104)
-Invalid（malformed）file/path name.

after I click the OK butten, a second popup message apeared:
Failed to open a session for the virtual machine Ubuntu15.
Details
The virtual machine 'Ubuntu15' has terminated unexpectedly during startup with exit code 1. more details may be available in 'C:\users\future\virtualbox vms\ubuntu15\logs\vboxhardening.log

Resul Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

And yet the hardening log is strangely absent from this discussion... Zip it, and attach the zip here. I won't discuss two VMs, so just pick one.

As a test, you can also try disabling your host AV, especially if it's Avira.

mpack wrote:And yet the hardening log is strangely absent from this discussion... Zip it, and attach the zip here. I won't discuss two VMs, so just pick one.

As a test, you can also try disabling your host AV, especially if it's Avira.

I am at work now，I will upload the log file when I get home. because this issue occurred on my home pc.
A strange phenomenon，the same OS（win10x64），same av（eset 9.0），same version of virtualbox（5.10），but the different computer，virtualbox works well on the computer in my office and my laptop.

here is my log file.

tell you a good message,I have dealt with this issue successfully. I installed a third-party tools software to clean my windows OS, including the temperary files and registy etc. then I tried to install virtualbox again and I was surprised to find that the vms could be started again.