Updating Windows 10 VM to 22H2 causes boot loop

Apr 26, 2020
30
0
11
58
Hi All, I wondered if anyone can shed a little light on a problem I have. I have a Windows 10 VM with Spice drivers and virtual nic passthrough working perfectly. When I try to update it with the 22H2 update, everything seems to be ok until I reboot. Then I get a BSOD error 0xc000021a and another reboot an attempted 'Automatic repair' which fails. I think it has something to do with the Spice SCSI as if go to a command prompt inside the repair utility it cannot find any partitions. I can overcome this by doing a 'drvload d:\vioscsi\w10\amd64\vioscsi.inf' which will load the driver and then let me see the contents of c: drive. Changing the disk bus to sata or ide does not seem to help and I can find no way to get past this. Luckily, I have backups so can restore to a pre-update state but cannot get pas this.

Running pve 7.3.3 with all the latest updates and 0.1.225 of the virtio drivers.

Does anyone have any ideas?
 
I had to remove the EFI disk and add a new one with enabled pre-enrolled keys to update my Win10 VMs to 22H2. Otherwise they failed too when rebooting after the update install.
 
Last edited:
I have the same problem with Win2012r2 and Win10. Check system disk after update leads to crash system partition. I’m worried, because have many virtual
machine with windows.
 
same here, proxmox 7.3 up-to-date, windows 10 pro 22h2. suddenly stopped working. stuck on a fix boot loop. i'm considering going back to proxmox 6.4. it seems to be kernel related. my vm has [host] processor. i'm trying other options for the processor, like qemu64 and kvm64 with no luck so far. still trapped in the boot loop. the host has a ryzen 5600G.
 
same here, proxmox 7.3 up-to-date, windows 10 pro 22h2. suddenly stopped working. stuck on a fix boot loop. i'm considering going back to proxmox 6.4. it seems to be kernel related. my vm has [host] processor. i'm trying other options for the processor, like qemu64 and kvm64 with no luck so far. still trapped in the boot loop. the host has a ryzen 5600G.
have you read/try post #2 ?!
 
agent: 1
balloon: 1024
bios: ovmf
boot: order=scsi0
cores: 2
cpu: host
efidisk0: samsung_evo_860:vm-100-disk-2,efitype=4m,pre-enrolled-keys=1,size=4M
machine: pc-q35-6.2
memory: 7168
meta: creation-qemu=6.2.0,ctime=1662863549
name: vm-guardia
net0: virtio=6A:96:64:CB:74:38,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: samsung_evo_860:vm-100-disk-1,cache=writeback,size=160G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=c791068e-9742-46f9-b90e-0e3d91c6e335
sockets: 1
vga: virtio
vmgenid: c763d9a3-3a7b-4b98-98bd-0d651458bdf5

root@pve0:/etc/pve/nodes/pve0/qemu-server# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-2
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve1
 
as a side note, i've been able to restore a backup from a few days ago, on other pve...so, i'm wondering if the problem is coming from f...$#%-up windows update. damn.
 
i never do any update and all do work perfectly fine. Windows chicago was quite the best and so win7sp2. Of course hosting or having a direct vm open on internet alone is not best, but a firewall should be in place well ahead anyway.
 

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!