virtualbox.org

Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737 -suplib-3rdchild --
comment WinXP - -startvm b8215d6g-8ddI 4bfa-9dbf-5bI 8659454f2 --no-
startvm-errormsgbox --sup-hardening-log=D:\VirtualBoxVMs\WinXP\Logs\VBoxHardening.log'(rc=-104)
Please try reinstalling VirtualBox.
where: supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) -
Invalid (malformed) file/path name. [/i]

Then on clicking OK, I get message:

Failed to open a session for the virtual machine WinXP.
The virtual machine 'WinXP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBoxVMs\WinXP\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


I HAVE NO ANTIVIRUS!! PLEASE HELP!!

Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left and the next tab's logs (vbox.log and hardening.log), zip the log files, and post the zip file, using the forum's Upload Attachment tab.

scottgus1 wrote:Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left and the next tab's logs (vbox.log and hardening.log), zip the log files, and post the zip file, using the forum's Upload Attachment tab.

Hello! Here is the log link hence I could not upload/save the file as it would keep disappearing.
ht t ps:/ / pastebin.c om/ Lpkp1FRu (remove the spaces)

By the way i'm not sure if this might be the issue or not, but I switched the file location from my C drive to my D drive. Since my C drive storage is full.

Your hardening log has a ExitCode=0x1. See Diagnosing VirtualBox Hardening Issues, posts 3 and 4. The possible causes could be web-safe security tools, HP ProtectTools, IBM Trusteer Rapport, other such nanny software. The log doesn't tell us what is the problem, you'll have to guess. Plain vanilla Windows 10 with built-in Defender AV and nothing else has no problem running Virtualbox (as long as Hyper-V is not enabled; this log doesn't tell us if it is or not).

Moving 'the file location' to the D drive may or may not cause trouble, depending on what file it was. There's a few hundred thousand files on a Windows PC...