shutdown completed！ when i created win11 last

C:\Users\rj>docker logs 599b67b2d3f6
❯ Starting OmniParser Windows for Docker v0.00...
❯ For support visit https://github.com/microsoft/OmniParser
❯ CPU: Intel Core TM i5 8400 | RAM: 10/12 GB | DISK: 149 GB (v9fs) | KERNEL: 5.15.167.4-microsoft-standard-WSL2...

❯ Extracting local ISO image...
❯ Detecting version from ISO image...
❯ Detected: Windows 11 Enterprise (Evaluation)
❯ Adding drivers to image...
❯ Adding OEM folder to image...
❯ Adding win11x64-enterprise-eval.xml for automatic installation...
❯ Building Windows 11 image...

C:\Users\rj>docker logs -f 599b67b2d3f6
❯ Starting OmniParser Windows for Docker v0.00...
❯ For support visit https://github.com/microsoft/OmniParser
❯ CPU: Intel Core TM i5 8400 | RAM: 10/12 GB | DISK: 149 GB (v9fs) | KERNEL: 5.15.167.4-microsoft-standard-WSL2...

❯ Extracting local ISO image...
❯ Detecting version from ISO image...
❯ Detected: Windows 11 Enterprise (Evaluation)
❯ Adding drivers to image...
❯ Adding OEM folder to image...
❯ Adding win11x64-enterprise-eval.xml for automatic installation...
❯ Building Windows 11 image...
❯ Creating a 20G growable disk image in raw format...
❯ Warning: unexpected clocksource: hyperv_clocksource_tsc_page
❯ Booting OmniParser Windows using QEMU v9.1.1...
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
❯ Windows has started successfully. You can directly view the VM at http://localhost:8006/vnc.html?view_only=1&autoconnect=1&resize=scale. Wait until setup is complete before interacting manually.
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,C57D8DC8-018E-4F4F-8C10-CCB13D35B14B,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
❯ Shutdown completed!

C:\Users\rj>

Start by reproducing the issue with the shown Docker image and commands, then inspect the QEMU boot sequence around the Windows Boot Manager messages and the final “Shutdown completed!” line. Done means identifying the cause of the immediate shutdown and verifying the expected Windows VM behavior after setup.