I have Windows 11 24H2 Host OS and installed latest virtual box (VirtualBox-7.2.0-170228-Win) with extension pack.I am trying to install Windows 11 24H2 as guest OS, after I setup new VM and power it up it is just stuck at black screen and not procedding further.
Attached my vbox log zip file and screenshot of guest vm,Please help to fix the issue
It may be that you are also suffering with extreme VM slow down:
00:00:12.091457 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:12.106605 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:12.106625 NEM: info: Found optional import WinHvPlatform.dll!WHvResumePartitionTime.
00:00:12.106627 NEM: info: Found optional import WinHvPlatform.dll!WHvSuspendPartitionTime.
00:00:12.106629 NEM: info: Found optional import WinHvPlatform.dll!WHvRequestInterrupt.
00:00:12.106631 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorXsaveState.
00:00:12.106632 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorXsaveState.
00:00:12.106634 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorState.
00:00:12.106636 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorState.
00:00:12.106637 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorInterruptControllerState.
00:00:12.106639 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorInterruptControllerState.
00:00:12.106641 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorInterruptControllerState2.
00:00:12.106643 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorInterruptControllerState2.
00:00:12.106646 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:12.106650 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:12.106862 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
...
00:00:12.108269 PGM: Enabling NEM mode
00:00:12.108403 NEM:
00:00:12.108403 NEM: NEMR3Init: Snail execution mode is active!
00:00:12.108403 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:12.108404 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:12.108404 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:12.108404 NEM: consider the consequences of disabling these features.
00:00:12.108404 NEM:
00:00:12.108442 CPUM: No hardware-virtualization capability detected
It may be that you are also suffering with extreme VM slow down:
00:00:12.091457 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:12.106605 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:12.106625 NEM: info: Found optional import WinHvPlatform.dll!WHvResumePartitionTime.
00:00:12.106627 NEM: info: Found optional import WinHvPlatform.dll!WHvSuspendPartitionTime.
00:00:12.106629 NEM: info: Found optional import WinHvPlatform.dll!WHvRequestInterrupt.
00:00:12.106631 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorXsaveState.
00:00:12.106632 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorXsaveState.
00:00:12.106634 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorState.
00:00:12.106636 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorState.
00:00:12.106637 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorInterruptControllerState.
00:00:12.106639 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorInterruptControllerState.
00:00:12.106641 NEM: info: Found optional import WinHvPlatform.dll!WHvGetVirtualProcessorInterruptControllerState2.
00:00:12.106643 NEM: info: Found optional import WinHvPlatform.dll!WHvSetVirtualProcessorInterruptControllerState2.
00:00:12.106646 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:12.106650 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:12.106862 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
...
00:00:12.108269 PGM: Enabling NEM mode
00:00:12.108403 NEM:
00:00:12.108403 NEM: NEMR3Init: Snail execution mode is active!
00:00:12.108403 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:12.108404 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:12.108404 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:12.108404 NEM: consider the consequences of disabling these features.
00:00:12.108404 NEM:
00:00:12.108442 CPUM: No hardware-virtualization capability detected
How to resolve this issue?I am still not able to install Guest OS in virtualbox
We have the same problems with virtual box 7.2.0 and the black screen with Windows 11 24H2 VM and Host.
After downgrading to 7.1.12 all is working again.
After some testing i could also get Virtual Box 7.2.0 running with Windows 11 24H2 Machines. But therefore Virtualization-Based Security must be completely deactivated....
This bug must be fixed!
Last edited by Youtox on 2. Sep 2025, 14:44, edited 1 time in total.
Problem fixed with setting up the virtual machine with another CPU Core then 2. There seems to be a bug with 24H2 and 2 CPU Cores. With 3 or 4 CPU Cores all is working fine
I can confirm the exact same bug.
I upgraded to 7.2.0 today and booting a known good Win11 VM on 7.2.0 gave a hang at a black screen. The VM worked fine on 7.1.12.
Changed the cores to 3 (from 2) and now everything works fine.
Attached are the log files from the two cases.
I came across this thread while trying to find a solution when my Windows 11 25H2 and 23H2 VMs began hanging (black screen) on startup after upgrading from 7.2.4 to 7.2.6 on a Windows 11 23H2 host PC.
Changing the number of CPUs from 2 to 3 fixed this for me.
Can confirm this bug still exists
i7-14700 - HP Pro 400 G9
Blank Screen on UEFI, won't boot or POST, reformatted my PC still nothing, tried every bloody configuration of disabling Hyper V, disabling virtualisation in BIOS, everything that these forums say, everything that AI Suggested, still nothing.
Changed the CPU form 2 to 3, BOOM works first try.
@VirtualBox...fix this bug please, its gone on long enough