Windows 11 Development Environment guest fails to load. Hangs at "Windows Boot Manager"

[dave_a]

Host: Mac OS Ventura 13.4.1
VirtualBox: 7.0.8
Virtual Machine Link: developer(dot)microsoft(dot)com/en-us/windows/downloads/virtual-machines/
(specifially WinDev2306Eval.VirtualBox.zip )

I've downloaded a Windows 11 development environment (rather than the .iso, tools, sdks, etc. individually) , but am unable to get the VM to launch. After extracting the .zip, I can import the VM without issue, but when I attempt to launch it will stop at the attached screen with the message "BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(xxxxxxxxxx) /\EFI\Microsoft\Boot\bootmgfw.efi"

VirtualBox_WinDev2306Eval_17_07_2023_12_27_12.png (13.35 KiB) Viewed 10786 times

The log file was rather large, so I've split it up sequentially into 3 separate files. Apologies if this is an improper approach. I was having trouble pinpointing what exactly might be the error.

Thanks

[scottgus1]

Zipped logs almost always fit. However, before you post the zip, did you use Open Core Legacy Patcher to get Ventura on your Mac? If so, Virtualbox on Ventura is incompatible with OCLP.

If you're not using OCLP, you're not apparently using an M1/M2 Mac, so please zip the log and post it.

[dave_a]

.zip attached. Thank you for the recommendation.

Machine is 2.3 GHz 8-Core Intel Core i9 circa 2019

[fth0]

Your problems should be fixed in the VirtualBox test builds 7.0.9r157071 and newer. For details, see 21596.

If you aren't in a hurry, VirtualBox 7.0.10 also contains the bugfix and is expected around 2023-07-18, which is nearby.

[dave_a]

Thank you!

[dave_a]

I have updated to Virtualbox 7.0.10, deleted the previous VM, imported the appliance again, and am getting the same result. It appears to freeze on the attached screenshot. I let the VM run for ~30 minutes before shutting it down.

[fth0]

The VM got much farther than you think. After the start, it rebooted somewhere during the graphics initialization, and after this second start, the (old 7.0.8 ) Guest Additions were started completely, and "only" the display was missing. Is the guest OS configured to auto-login?

Start the VM, let it "hang" for ~10 minutes, then try a few things that normally change the display resolution: In the VM window's menu, try View > Virtual Screen 1 > Resize to 1600x900. Use the Host key + F to switch between windowed mode and full-screen mode. Try your own ideas. Provide a (zipped) VBox.log file and a description what you've tried.

[dave_a]

- Started in scaled mode
- waited ~10 minutes
- took a screenshot (attached)
- resized window by dragging
- took a screenshot (attached)
- switched to full screen
- took a screenshot (didn't attach- there's no difference between the 3 screenshots, only included two to note the timestamp difference)
- tried seamless mode (disappeared from view)
- tried scaled mode
- tried auto resize
- tried to resize to 1024x768
- upgraded guest additions

In a nutshell, I tried a variety of resizing and view modes. At one point, I believe I saw the edge of what appeared to be a windows desktop, but it flaked out. I powered off the VM, started it again, but it was more of the same.

[fth0]

Looks like you forgot the (zipped) VBox.log file corresponding to your description. I can read much more from that than from your screenshots.

[wisetoad]

Any luck on this one? I have the same problem. Running Version 7.0.10 r158379 (Qt5.15.2) with WinDev2308Eval...

[Stainer]

I have the same issue with Version 7.0.12 r159484 (Qt5.15.2)

I am trying to attach my logs but it says the file is too large

[scottgus1]

Try zipping the log.

[Stainer]

Thanks Scott.

Zipping worked

[mpack]

One relevant log is plenty - and is all I looked at.

RAM is being vastly over-committed.

00:00:01.428141 Host RAM: 16384MB (16.0GB) total, 4826MB (4.7GB) available
...
00:00:01.528324 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8.0 GiB)

You need to free up a lot of host RAM, and even then I would not allocate more than 4096MB to a VM on this host.

CPU is being over-committed too. Your host has 4 physical cores, so don't allocate more than 2 to a VM.

[Stainer]

Thanks mpack