Win11 VM stuck on 22H2

B

Boerny41

Member
Aug 19, 2022
16
2
8
Hi,

I've got a Win11 VM that I'm unable to update. It got initially installed with "host" cpu type, but I've tried "x86-64-v2-AES".
I do not get an "CPU not supported" message, but rather windows just tells me that my PC currently doesn't support a newer version and that they will offer it automatically once it does, when trying to install 24H2 manually.

I've tried to run the win11 update assistant and health check, neither did anything.

Code: 
agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0
cores: 6
cpu: x86-64-v2-AES
efidisk0: local-zfs:vm-102-disk-3,efitype=4m,size=1M
hotplug: 0
localtime: 0
machine: q35
memory: 8192
meta: creation-qemu=8.0.2,ctime=1692452778
name: Win11
net0: virtio=E6:63:D3:A2:FB:25,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: other
parent: beforeUpdate
scsi0: local-zfs:vm-102-disk-1,cache=writeback,discard=on,iothread=1,size=80G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=70508298-a833-456f-8022-cb244a24c89d
sockets: 1
tablet: 0
tpmstate0: local-zfs:vm-102-disk-2,size=4M,version=v2.0
vmgenid: 2c5355ca-2eef-48e8-b5e8-89aec0e446fc
 

Attachments

  • Screenshot 2025-02-08 012814.png
    Screenshot 2025-02-08 012814.png
    186.8 KB · Views: 7
PC health / integrity check says that the VM fully supports Win11, but the installation assistant still gives the error on both CPU types.
 
It's an AMD Ryzen 5 PRO 4650G

Here is also a screenshot of WhyNotWin11 and the PC health tool, both say that everything is fine.
 

Attachments

  • 2025-02-08 23_36_01-win11vm - Remotedesktopverbindung.png
    2025-02-08 23_36_01-win11vm - Remotedesktopverbindung.png
    170.3 KB · Views: 5
I've also tried the steps below and while I got 23H2 installed this way, I'm now stuck on 23H2 in the same way I was stuck before on 22H2. Trying to install 24H2 still gives the error message from the initial post.

(1. 2. & 3. worked, 4. is the health check that is good, 5. fails for me)
E

Post in thread 'Win11 VMs stuck on 22h2'

I saw that thread, but it wasn't the same in our case because we have the problem already since 22h2.
In any case, the "solution" (/etc/pve/virtual-guest/cpu-models.conf) doesn't work.

In the meantime I found another solution - that actually works for me:
  1. make sure the VM is using the 'x86-64-v2-AES' CPU type
  2. use this file to update from 22h2 to 23h2
  3. install all available updates - this will take you to the latest state of 23h2
  4. download and install this file, and run the PC Health Check
  5. download and run this file to upgrade to 24h2 (this upgrade will...
  • Like
 
Last edited:
I was still running VirtIO 240 and updated to 266 now. Win11 installation assistant is currently running, but it usually takes an hour or two, so I'll probably report back tomorrow.

Normal Windows updates still didn't find anything. I guess even if the update assistant now works, I'll then be stuck on 24H2 with the normal update service remaining broken. Windows 11 is just annoying...
 
I've decided to wait, but still not luck. The Windows11-Installation-Assistant still gives the same error message after updating to VirtIO266 (latest).
 
You must log in or register to reply here.
Top Bottom