Unable to headless start and detachable start

[threeFatCat]

I've been reading some of the old posts here and decided to post now. I'm currently running Windows 11 Insider Preview in Dev channel Version 22H2 (OS Build 25131.100).

I know the dev channel is unstable but I just want someone to confirm if this is really an issue with the current OS version. I can Normal start using the latest version.

I also did try the test build v6.1.35 Test Build 151573 | Win11 25131 | Works from VirtualBox success reports on Windows Insider builds, since it says the report "Works", but I couldn't even run in Normal mode from the test build. Here I attached the logs from the regular latest version of VM and the test build.

P.S. the test build log is labeled with VBoxHardening_buildr151573.

VBoxHardening.zip

(3.32 KiB) Downloaded 371 times

VBoxHardening_buildr151573.zip

(4.6 KiB) Downloaded 352 times

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[threeFatCat]

Isn't the VBoxHardening.log is just the same? I followed the steps, weird that when I hit save from the dialog no file is getting saved in my chosen location, I also tried different location. I just copied the content instead in a notepad and created a zip.

VBox.zip

(3.29 KiB) Downloaded 369 times

[mpack]

The hardening log is for hardening problems, and it doesn't contain everything we might like to know.

And... you provided the hardening log again, which is not the log I asked for.

[threeFatCat]

Oh sorry, maybe I'm doing it wrong. What I did, I'm in the manager > right clicked the box I was trying to bootup > then the context shows Settings.. etc. Show Log CTRL+L, chose it > Log viewers shows up.

Do I supposed to right click somewhere else?

Screenshot 2022-06-04 143805 (1).png (63.96 KiB) Viewed 14148 times

[threeFatCat]

Okay I got it now. There is no VBox.log created when trying to boot in Headless or Detachable that has an issue. I tried to boot at Normal mode, and the VBox.log was generated. Here it is.

VBox.zip

(32.8 KiB) Downloaded 372 times

[mpack]

No Hyper-v, that's good.

I would increase VM RAM to 2048MB, and increase graphics RAM to 64MB. Yes, I'm aware that you want to create a headless VM, but AFAIK it still has a (hidden) virtual graphics display which is subject to failure if it doesn't have enough RAM.

[threeFatCat]

I just increased it now, but still did the same thing.

Code: Select all

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Actually I was able to use the virtualbox in the previous build. I'm using it for work. This Windows 11 build and the previous build before this is when it all started that I cant boot up in headless mode. Is there any other possible issue you can find in the log? Thank you.

[multiOS]

A couple of things from the Log:

Code: Select all

00:00:38.628843 VMMDev: Guest Additions information report: Version 6.1.22 r144080 '6.1.22'

Code: Select all

00:00:50.422395 VMMDev: Guest Log: vboxsf: SHFL_FN_MAP_FOLDER failed for 'tmp_vagrant-puppet_modules-9569fdbdb9d3837be802788694c37002': share not found
00:00:50.422579 VMMDev: Guest Log: vboxsf: SHFL_FN_MAP_FOLDER failed for '/vagrant': share not found

Perhaps updating the Guest Additions to match the VirtualBox 6.1.34 you have installed release might help.

Vagrant isn't supported on this Forum so you might also want to ask on Vagrant Forums.

[threeFatCat]

A couple of things from the Log:

Code: Select all

00:00:38.628843 VMMDev: Guest Additions information report: Version 6.1.22 r144080 '6.1.22'

Code: Select all

00:00:50.422395 VMMDev: Guest Log: vboxsf: SHFL_FN_MAP_FOLDER failed for 'tmp_vagrant-puppet_modules-9569fdbdb9d3837be802788694c37002': share not found
00:00:50.422579 VMMDev: Guest Log: vboxsf: SHFL_FN_MAP_FOLDER failed for '/vagrant': share not found

Perhaps updating the Guest Additions to match the VirtualBox 6.1.34 you have installed release might help.

Vagrant isn't supported on this Forum so you might also want to ask on Vagrant Forums.

Do you think it has something to do with vagrant even I'm booting directly from the Virtual box Manager GUI? Okay, I'll check if I need to update anything with vagrant. I just wonder though, it work perfectly fine in my other laptop running Windows 11 with different build but it's under Beta channel and not the Dev channel, and it looks like it doesn't say anything in the log that it's an OS issue. Weird. Anyway, thanks.

[multiOS]

Not sure, but it will do no harm to upgrade Guest Additions to the the matching 6.1.34 version, as that might resolve the shared folder issue.

Of course. Windows Insider builds have been known to disrupt a variety of third party software installations; especially with software where requires driver installation/close 'integration' with the OS; and 'major' Windows updates may frequently require the full re-installation of software such as VirtualBox to ensure that its drivers are correctly installed/working.

[dpavle]

Any updates on this topic?

I am experiencing the same issue on the latest Windows 11 Insider build 25206 (Dev channel). Tried reinstalling VirtualBox as an administrator and rebooting to no avail.

I'm attaching my logs below

[scottgus1]

The VM shut down 4 seconds after starting to boot:

00:00:11.359965 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:15.028079 Changing the VM state from 'RUNNING' to 'SUSPENDING'

Something is wrong with the Windows files:

910.1728: Error (rc=-5607):
910.1728: supHardenedWinVerifyProcess failed with Unknown Status -5607 (0xffffea19): ntdll.dll: SizeOfImage (0x219000) isn't close enough to the mapping size (0x21b000)

I'm not sure what the cause is, though.

[dpavle]

Something is wrong with the Windows files:

I ran sfc /scannow, didn't find any errors.

[Timka21213]

Any updates on this topic?

I am experiencing the same issue on the latest Windows 11 Insider build 25206 (Dev channel). Tried reinstalling VirtualBox as an administrator and rebooting to no avail.

I'm attaching my logs below

I have the same problem with
Edition Windows 11 Pro Insider Preview
Version 22H2
Installed on ‎20.‎10.‎2022
OS build 25227.1010
Serial number PF33AA59
Experience Windows Feature Experience Pack 1000.25227.1010.0


3604.b3cc: VBoxHeadless.exe: Differences in section #8 (.rsrc) between file and memory:
3604.b3cc: 00007ff69e2a25f8 / 0x01125f8: 00 != 50
3604.b3cc: 00007ff69e2a25f9 / 0x01125f9: 00 != 41
3604.b3cc: 00007ff69e2a25fa / 0x01125fa: 00 != 44
3604.b3cc: 00007ff69e2a25fb / 0x01125fb: 00 != 44
3604.b3cc: 00007ff69e2a25fc / 0x01125fc: 00 != 49
3604.b3cc: 00007ff69e2a25fd / 0x01125fd: 00 != 4e
3604.b3cc: 00007ff69e2a25fe / 0x01125fe: 00 != 47
3604.b3cc: 00007ff69e2a25ff / 0x01125ff: 00 != 58
3604.b3cc: Restored 0xa08 bytes of original file content at 00007ff69e2a25f8
3604.b3cc: Error (rc=-5607):
3604.b3cc: ntdll.dll: SizeOfImage (0x219000) isn't close enough to the mapping size (0x21b000)
3604.b3cc: Error (rc=-5607):
3604.b3cc: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x219000) isn't close enough to the mapping size (0x21b000)
3604.b3cc: Error -5607 in supR3HardNtChildPurify! (enmWhat=5)
3604.b3cc: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x219000) isn't close enough to the mapping size (0x21b000)