KB5012170 fails to install on Win11 host

Hi,


had the same problem on my windows boxes but server 2019-2022.
I fixed it with a reset of the secure boot keys.

Go into th UEFI Shell when the VM starts then Device Manager -> Secure Boot Configuration -> Reset Secure Boot Keys -> Save and continue booting.

Instruction obviously with no warranty because don't know what other things it effects but for me it worked - so make a backup first.

Greetz
Very Thanks. This was the trick :D
 
  • Like
Reactions: fluxX04
Thanks for the infos. Also got 3 Win10 VMs with OVMF that won't allow me to install that update for weeks now.
 
Resolved the issue here on a Windows Server 2019: install of KB5012170 failed at 99%. Then I solved the problem this way:
  1. Poweroff Windows server 2019 VM
  2. Detach EFI disk
  3. Add a new one EFI DISK with "Pre-Enrolled Keys"
  4. Boot VM
  5. Start Windows Update
  6. Install pending update
The update installed successfully.
Thanks to everybody!
Since PVE 7.2-11 the procedure doesn't work anymore: if I substitute the EFI disk, Windows VM do not boot anymore, with "Guest has not initialized the display (yet)" on console. Old UEFI disk does not permit to install Windows updates.
Does anybody know a solution?
 
Since PVE 7.2-11 the procedure doesn't work anymore: if I substitute the EFI disk, Windows VM do not boot anymore, with "Guest has not initialized the display (yet)" on console. Old UEFI disk does not permit to install Windows updates.
Does anybody know a solution?
Disable Mem Hotplug. Had the same situation.
 
  • Like
Reactions: macpip
Disable Mem Hotplug. Had the same situation.
Thank you @fireon, but there was no memory hotplug.
Hotplug was activated just for Network, Disk and USB. I got the same issue on many servers, and no solution at the moment.
 
Last edited:
Please post one vmconfig.
Here it is:
Code:
## Windows Server 2019 Standard Ita
#__________________
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 8192
bios: ovmf
boot: c
bootdisk: scsi1
cores: 8
efidisk0: local-zfs:vm-110-disk-0,size=128K
hotplug: disk,network,usb,memory,cpu
machine: q35
memory: 12288
name: xxxSServer01
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: PreCambioUefi
protection: 1
sata0: local:iso/virtio-win-0.1.221.iso,media=cdrom,size=519030K
sata1: none,media=cdrom
scsi0: local-zfs:vm-110-disk-1,discard=on,iothread=1,size=100G,ssd=1
scsi1: local-zfs:vm-110-disk-2,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=726e13c1-b3bd-40dd-acb8-c687df6d643e
sockets: 1
startup: order=10,up=180,down=360
vga: qxl
vmgenid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

[PRe_Reinstall_Virtio]
#PRe_Reinstall_Virtio
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 8192
bios: ovmf
boot: c
bootdisk: scsi1
cores: 8
efidisk0: local-zfs:vm-110-disk-0,size=128K
hotplug: disk,network,usb,memory,cpu
machine: q35
memory: 12288
name: xxxServer01
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
protection: 1
runningcpu: kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-q35-5.1+pve0
sata0: local:iso/virtio-win-0.1.215-2.iso,media=cdrom,size=528322K
sata1: none,media=cdrom
scsi0: local-zfs:vm-110-disk-1,discard=on,iothread=1,size=100G,ssd=1
scsi1: local-zfs:vm-110-disk-2,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
snaptime: 1664391564
sockets: 1
startup: order=10,up=180,down=360
vga: qxl
vmgenid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
vmstate: local-zfs:vm-110-state-PRe_Reinstall_Virtio

[PreCambioUefi]
#Pre Cambio Uefi con enrolled keys
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 8192
bios: ovmf
boot: c
bootdisk: scsi1
cores: 8
efidisk0: local-zfs:vm-110-disk-0,size=128K
hotplug: disk,network,usb,memory,cpu
machine: q35
memory: 12288
name: xxxServer01
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: Pre_Agg
protection: 1
sata0: local:iso/virtio-win-0.1.221.iso,media=cdrom,size=519030K
sata1: none,media=cdrom
scsi0: local-zfs:vm-110-disk-1,discard=on,iothread=1,size=100G,ssd=1
scsi1: local-zfs:vm-110-disk-2,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
snaptime: 1664400098
sockets: 1
startup: order=10,up=180,down=360
vga: qxl
vmgenid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

[Pre_Agg]
#Pre Agg Win
#Virtio 0.1.221 OK
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 8192
bios: ovmf
boot: c
bootdisk: scsi1
cores: 8
efidisk0: local-zfs:vm-110-disk-0,size=128K
hotplug: disk,network,usb,memory,cpu
machine: q35
memory: 12288
name: xxxServer01
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: PRe_Reinstall_Virtio
protection: 1
runningcpu: kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep
runningmachine: pc-q35-5.1+pve0
sata0: local:iso/virtio-win-0.1.221.iso,media=cdrom,size=519030K
sata1: none,media=cdrom
scsi0: local-zfs:vm-110-disk-1,discard=on,iothread=1,size=100G,ssd=1
scsi1: local-zfs:vm-110-disk-2,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
snaptime: 1664393783
sockets: 1
startup: order=10,up=180,down=360
vga: qxl
vmgenid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
vmstate: local-zfs:vm-110-state-Pre_Agg
 
Thank you. I see on your config memory hotplug is activated on all snapshots.
I'm really sorry and beg your and forum pardon, I should have been blind for a while (or erroneously have been looking to other VM). Sure: that VM has hotplug memory !!!!
Sorry again, and thank you!
 
Looks like pre-enrolled keys also helps with KB5018410. Now are all 3 Win10 VMs up to date again. Tried to update them a couple of times over the last few months but it always failed.
 
Last edited:
Your EFI-Disk must have "Pre-Enrolled Keys" enabled.
Thanks, that's what fixed the issue for me.
stop the VM, remove current efi drive and create a new one.
Pre-Enrolled Keys are enable by default
 
  • Like
Reactions: ITT
We just saw this issue with Windows Server 2022 and the most recent version of PVE (updated to be sure).

The VM would not boot with the memory hotplug enabled. It would get to "guest has not initialized the display (yet)" and hang.

Disabling the memory hot plug and it booted.

During testing, we found it would boot with the memory hotplug enabled on a different node.

The difference between the nodes was the CPU. It would not boot on the Westmere CPU but would boot on the Sandy Bridge node with memory hotplug enabled.
 
  • Like
Reactions: macpip

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!