Error on trying to run VM in headless mode.

[UnclWish]

Host: Windows 10 Pro x64 Quest: Windows XP x32

All going norm. VM works and launches. Problem is error when attempt to launch VM in headless mode.

Error: Не удалось открыть сессию для виртуальной машины VWXP. The virtual machine 'VWXP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\VWXP\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005) Компонент: MachineWrap Интерфейс: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}

[Socratis]

Please read really carefully the following FAQ: ​Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas.

[UnclWish]

I read that FAQ before open a ticket... But I didn't find any possible reason for this bug. Windows 10 x64 Pro licensed, it's new installed, after that it was installed only few programs for work, MS Office, archiver. AntiVirus is standard Windows 10 Defender... It's very strange that VM starts in normal mode and working. Issue is running headless mode only.

[Socratis]

Do you have 2D/3D enabled? Can you disable it and see if it starts? You're the 2nd person to mention something like that, and I'd like to see if it's the same root cause...

[UnclWish]

2D/3D is set "Enabled" as it was by default during creating VM. I try to disable it, but it can take some time to check. I wrote later about results...

[Socratis]

In that case, a core dump is sort of required. Read the wiki:Core_dump "Creating core dumps to help analyze VirtualBox crashes", and in particular the "Minidumps on Windows" section. Then put the dump file in a public visible server and post the link to the dump. Someone will be there to take a look...

[Socratis]

Another headless case started in the forums: ​Cannot start any VM as "headless" or "detachable". I asked the OP to comment here so we can try and see if there's a pattern...

[Laurent Marechal]

I have the same issue too. I cannot start any VM as "headless" or "detachable". They all start fine as "normal"

Setup : Windows 10 64bits v1709 (build 16299.371) VirtualBox 5.2.8 and previous versions

First seen when using Vagrant, but can be reproduced with the VB GUI every time.

Vagrant:

Command: ["startvm", "d76a8651-0c76-4476-992d-2a0b428be0ee", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'XXXXXXXXX_1524231251008_66154' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'XXXXXXXXXXX_1524231251008_66154\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

GUI:

Failed to open a session for the virtual machine XXXXXXXXXXX_1524231251008_66154.
The virtual machine 'XXXXXXXXXXX_1524231251008_66154' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'XXXXXXXXXXX_1524231251008_66154\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Last few line from the log:

108c.3454: Calling main()
108c.3454: SUPR3HardenedMain: pszProgName=VBoxHeadless fFlags=0x0
108c.3454: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox'
108c.3454: '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VBoxHeadless.exe' has no imports
108c.3454: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VBoxHeadless.exe)
108c.3454: SUPR3HardenedMain: Respawn #2
108c.3454: Error (rc=-5640):
108c.3454: More than one thread in process
108c.3454: Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1)
108c.3454: More than one thread in process
4128.3cf8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 31 ms, the end);

Failing VM can be old ones or new ones, Windows or Linux.

The same system was working fine for month (with multiple version of VB). The latest changes were:

1. I had to install Symantec AV in place of MS AV. During the test I removed it and reverted to the previous config, with no changes.
2. I had to install "Forcepoint DLP Endpoint"/Websense. It cannot be removed or disabled, but it's flagged as "not scanning"anything (they said...).
3. There was some push of Windows 10 updates

An other user got the same setup and have no issues, but he did not got the W10 update pushed to him yet.

I went through the hardening post with no result.

• disable, remove the AV (Symantec), with no effect.
• replaced AV with MS's one
• totally remove and reinstall virtualbox
• check that hyper-V is not installed/enabled (including nic/bce/registry check)
• VM is a new one, so was never powered-up. Same happen with old VM that were powered down and working before.
• Reboot
• sfc /scannow report no problems
• checked the vboxdrv is running
• changing the vboxdrv to start on-demand and not at startup
• disable 2D/3D acceleration
• ran a procmon but did not saw anything jumping to my eyes

After changing the driver to start on-demand, I tried to start one, I got the same result, but I noticed the drivers did not even start, so it seems it it not reach the point to start the VM at all.

I'm not sure how to create the dump. As there is no application crash/bsod, it just stops with an error when running the commands. Unless adding a breakpoint in the debugger at that specific time, the dump might just get "clean"

Added log file VBoxHardening_lmarecha.log

[jappi]

I have the same issue too.

Error Symptom 2: Error code 0xC0000005

Setup: VM 5.2.8 Windows 10 pro x64

Quest: Windows 7 x64

tried to do everything about what you wrote above + reinstalled my graphics card drivers

Added log file VBoxHardening_jappi.log

[UnclWish]

jappi, your VM starts with normal mode? Issue is only when try to start in headless mode?

[jappi]

Replying to UnclWish:

jappi, your VM starts with normal mode? Issue is only when try to start in headless mode?

normal mode works excellently. Yes, issue only when try to start in headless mode

[UnclWish]

Interesting, what unites us?

[UnclWish]

Does anyone tried new version? Issue is still here?

[Socratis]

UnclWish, what about you? Did *you* try it?

[UnclWish]

Replying to socratis:

UnclWish, what about you? Did *you* try it?

No, computer is in use by client now. No time to check. I temporary maked headless mode on VMWare Player via minimized starting and hiding window to tray by 3rd tool.

[jappi]

with the new version the bug is gone

[UnclWish]

Replying to jappi:

with the new version the bug is gone

Really? It's food, if it so. Sorry for offtopic, but how to force by default to do chosen action to VM when host is power off? Usually if try to close VM window, he ask what to do - Power off, suspend, etc. It's need to didn't asking...

[Socratis]

@UnclWish

Please go to the forums for generic questions that have nothing to do with the ticket. That's why they're called "forums", because it's the place for discussions like that. A ticket should not have "off-topic" questions.

Plus, there is always the manual:

• 9.20.8 Action when terminating the VM,
• 9.20.9 Default action when terminating the VM.

[UnclWish]

Replying to socratis:

@UnclWish

Please go to the forums for generic questions that have nothing to do with the ticket. That's why they're called "forums", because it's the place for discussions like that. A ticket should not have "off-topic" questions.

Plus, there is always the manual:

• 9.20.8 Action when terminating the VM,
• 9.20.9 Default action when terminating the VM.

I'm sorry for that. Thanks for links. I'll check it all.

[Socratis]

Replying to UnclWish:

1st I need to check in new version - is the bug is gone or not...

Please let us know, because just today I had ​another report for VBoxHeadless crashing (on OSX). Starting headless from within the VirtualBox Manager, worked. Bizarre...

[jdang]

Yes, for Windows7 Enterprise, I still have the same problem with VirtualBox-5.2.28 and VirtualBox-5.2.30. Can run in normal mode but not headless.

Looks like CANNOT run in any mode for VirtualBox-6.0.8-130520.

Any solution to this problem?

Jdang

[T4nkcommander]

I am experiencing this bug after updating to 6.1.36. Is there a solution? All of my VMs - including newly created ones - are experiencing this issue.

[Klaus Espenlaub]

There's no chance we can help without getting log files (and the last ones were attached to this ticket 4 years ago). We need at least VBoxHardening.log and VBox.log* from the Logs subdirectory of the VM folder.