Windows 11 fails to boot shortly after installation

lazynooblet

Member
Jan 23, 2021
22
7
8
I've seen a few similar threads on this, but haven't got a solution that works for me yet.

I have a new host Proxmox host, and what I used to do before is now failing.

I am using Proxmox to test Windows 11 Autopilot builds. The Autopilot build doesn't do much fancy things, but it does join the device to Intune and enable Bitlocker. Windows 11 24H2 installs from ISO fine, it gets picked up by Autopilot during OOBE and I eventually get to a working desktop. However if I shutdown/reboot, on next boot the primary volume will be "RAW", causing "Automatic Startup Repair" to kick in and fail.

I am not passing through any hardware, its a simple Win11 capable VM.

Using the Win11 pre-boot recovery UI, I open command prompt and diskpart shows as "unknown", and chkdsk compalins it can't work on RAW devices

1736339066447.png

My process has been
  1. Create Win11 VM
  2. Add Win11 24H2 iso
  3. Add Virtio iso (in this case virtio-win-0.1.266.iso)
  4. Boot and install Win11
  5. At first OOBE, create snapshot
  6. Press SHIFT+ALT+F3 to boot into Audit mode
  7. Install virtio drivers and guest tool
  8. Reseal and boot back into OOBE
  9. New snapshot
  10. Enrol onto Autopilot using Get-WindowsAutopilotInfo.ps1 -Online
  11. Complete OOBE, Autopilot then takes over
  12. Eventually get to desktop, confirm device has enrolled correctly
  13. Bitlocker is Fully encrypted
  14. Reboot to test

However after the reboot, I will get the "Automatic Startup Repair" issue, with a broken volume.

I have tried so far to fix a broken VM

  1. Adding ",hidden=1" to the cpu type
  2. Using x86-64-v2-AES as cpu type
  3. Using display driver Virtio-GPU
  4. Disabling secure boot in VM bios
  5. Switching from Virtio to SATA
  6. Adding to VM args: -cpu Cooperlake,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,+vmx
As I type, I am now trying again with x86-64-v2-AES as cpu type from the very beginning.
Edit: Build using x86-64-v2-AES CPU has same issue on first reboot.
Edit: Disabled bitlocker prior to reboot, same issue
Edit: Recreating VM using E1000 NIC and SATA disk, no virtio drivers, and an Autopilot build survives reboots. This fits my purpose, I don't carte about performance. But I'll look into this more and do more testing if I receive any updates here.


Any ideas/suggestions welcome.

Code:
agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0
cores: 2
cpu: x86-64-v2-AES
efidisk0: local-nvme:vm-150100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
machine: pc-q35-9.0
memory: 8192
meta: creation-qemu=9.0.2,ctime=1733157349
name: win11.client
net0: virtio=BC:24:11:8B:7B:65,bridge=vmbr0,tag=50
numa: 1
ostype: win11
parent: enrolled_on_intune
scsi0: local-nvme:vm-150100-disk-2,discard=on,iothread=1,size=61G
scsihw: virtio-scsi-single
smbios1: uuid=e3e39be2-3f25-475b-8da1-4b7b5b76f190,serial=VEVTVFZNMDE=,base64=1
sockets: 1
tpmstate0: local-nvme:vm-150100-disk-1,size=4M,version=v2.0
vmgenid: 0e088cc2-e876-4631-8c13-b972bc9d72c9

Code:
# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-5-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Code:
Processor Information
        Socket Designation: CPU1
        Type: Central Processor
        Family: Xeon
        Manufacturer: Intel
        ID: 57 06 05 00 FF FB EB BF
        Signature: Type 0, Family 6, Model 85, Stepping 7
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                APIC (On-chip APIC hardware supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
                CLFSH (CLFLUSH instruction supported)
                DS (Debug store)
                ACPI (ACPI supported)
                MMX (MMX technology supported)
                FXSR (FXSAVE and FXSTOR instructions supported)
                SSE (Streaming SIMD extensions)
                SSE2 (Streaming SIMD extensions 2)
                SS (Self-snoop)
                HTT (Multi-threading)
                TM (Thermal monitor supported)
                PBE (Pending break enabled)
        Version: Intel(R) Xeon(R) Gold 6234 CPU @ 3.30GHz
        Voltage: 1.8 V
        External Clock: 10400 MHz
        Max Speed: 4000 MHz
        Current Speed: 3300 MHz
        Status: Populated, Enabled
        Upgrade: Socket LGA2011
        L1 Cache Handle: 0x0700
        L2 Cache Handle: 0x0701
        L3 Cache Handle: 0x0702
        Serial Number: Not Specified
        Asset Tag: Not Specified
        Part Number: Not Specified
        Core Count: 8
        Core Enabled: 8
        Thread Count: 16
        Characteristics:
                64-bit capable
                Multi-Core
                Hardware Thread
                Execute Protection
                Enhanced Virtualization
                Power/Performance Control
 

Attachments

  • 1736339049723.png
    1736339049723.png
    42 KB · Views: 0
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!