Opened 3 months ago
Closed 6 weeks ago
#22162 closed defect (fixed)
WIndows hosts based on W11 24H2 cannot start headless or detachable VM's [Fixed in SVN]
| Reported by: | Michel Godfroid | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox-7.0.20 |
| Keywords: | hardening detachable headless | Cc: | |
| Guest type: | all | Host type: | Windows |
Description (last modified by )
This has already been reported in the forums (https://forums.virtualbox.org/viewtopic.php?p=547751#p547751) As 24H2 release is approaching, this will potentially affect a lot of users, and has the potential to stop any vagrant flows. (note that 24H2 has already been released to OEMS for imaging new systems). Summary: The headless executable hardening detects ntdll differently from the 'normal' foreground program. Excerpt from the vboxhardening log: ed4.afa8: Error (rc=-5607): ed4.afa8: ntdll.dll: SizeOfImage (0x263000) isn't close enough to the mapping size (0x266000) ed4.afa8: Error (rc=-5607): ed4.afa8: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x263000) isn't close enough to the mapping size (0x266000) ed4.afa8: Error -5607 in supR3HardNtChildPurify! (enmWhat=5) ed4.afa8: supHardenedWinVerifyProcess failed with -5607: ntdll.dll: SizeOfImage (0x263000) isn't close enough to the mapping size (0x266000) 6ca4.35c4: Terminating the normal way: rcExit=0
Tested with Windows build 26100.1591 (and previous 24H2 builds) and tested with vbox 7.0.20 tested with vbox 7.0.21 (build 164462) tested with vbox 7.1.0_BETA2 (build 164697)
Change History (6)
comment:1 by , 3 months ago
| Description: | modified (diff) |
|---|
comment:2 by , 7 weeks ago
follow-up: 5 comment:3 by , 7 weeks ago
I'm working on a fix. Hope to have something that work early next week.
comment:4 by , 7 weeks ago
| Summary: | WIndows hosts based on W11 24H2 cannot start headless or detachable VM's → WIndows hosts based on W11 24H2 cannot start headless or detachable VM's [Fixed in SVN] |
|---|
comment:5 by , 7 weeks ago
comment:6 by , 6 weeks ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Hi guys,
We just released VirtualBox 7.0.22 and 7.1.4. The issue should be fixed in this release. You can give it a try on Downloads page.
There are a number of reports on the forum that have been added for this bug:
https://forums.virtualbox.org/viewtopic.php?t=112454
https://forums.virtualbox.org/viewtopic.php?t=111705
https://forums.virtualbox.org/viewtopic.php?t=112503
I've had the same issue since Windows 11 24H2 update has installed, as have all the other Virtualbox users on Windows 11 at our offices.
Here is my VBoxHardening.log