Starting Win11 was permamently loading

[tkzsfqwnjaom]

Created Win11 virtual machine in vbox 7.0.12, all settings are default, i only added for loading from iso, on loading it tells me that "press any key etc...", i press key and then vbox loading that forever, no any changes, what can i do???

[mpack]

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.

[tkzsfqwnjaom]

logs here

[mpack]

I don't see much wrong with the VM config, though I would reduce the CPU allocation to 2 cores.

I see that the VM is located on drive D. What technology is drive D? E.g. is it an 2nd internal drive, USB SSD, USB thumb drive, network drive etc?

I also note that you seem to be booting from an ISO and the ISO name is "25982.1000.231020-1353.RS_PRERELEASE_CLIENTMULTI_X64FRE_EN-US.ISO". Note the word "prerelease". Aka unstable. You mentioned nothing about this in your post. Where did this ISO come from?

[tkzsfqwnjaom]

2 cores gives same result.

d: drive is ssd.

it comes from ms, original release, and whatever 22621 loads the same.

ps: win10 are loads sucessfull, no permanent VB logo loading, all win versions loads success except win11, i think there is in VB problem and its support of win11

[mpack]

i think there is in VB problem and its support of win11

I don't recall seeing any other reports of that. Did you have to use any of the compatibility tricks to get Win11 to install?

[fth0]

00:00:05.348756 EFI: VBoxDbg> loadimage64 'cdboot.efi' 0x10000000 LB 0x129000
[...]
00:00:10.604800 GIM: HyperV: Guest indicates a fatal condition! P0=0x5c P1=0x110 P2=0x5250631 P3=0x14 P4=0xffffffffc0000001
00:00:10.604820 GIMHv: BugCheck 5c {110, 5250631, 14, ffffffffc0000001}
00:00:10.604820 HAL_INITIALIZATION_FAILED
[...]
00:05:01.439542 /Public/Storage/AHCI0/Port1/BytesRead 502894592 bytes

FWIW, ~500 MB have been read from the ISO file, and the guest OS had an early BSOD of type HAL_INITIALIZATION_FAILED.

While the VM is not running, please open a Windows Command Prompt with normal user privileges and execute the following commands:

Code: Select all

cd "C:\Program Files\Oracle\VirtualBox"
VBoxManage modifyvm "win11" --hpet on

Please report back if that solved your problem!

PS: @mpack: FYI: Klaus asked me this week if I perhaps knew why the latest Windows 11 Insider Previews crash with HAL_INITIALIZATION_FAILED when VirtualBox doesn't provide the HPET to the VM. This information seems to come in handy now.

[tkzsfqwnjaom]

thanks fth0, high precision event timer was solved my problem, and i think in next release it good to enable hpet for all win11 virtual machines...

[fth0]

Thanks for reporting back!