VM update from Server 2022 to Server 2025

[MisterDeeds]

Dear all

I am trying to upgrade a server from Server 2022 to Server 2025 using Inplace Upgrade. To do this, I insert the ISO and go through the setup. In the end, however, the VM restarts and the following error appears:

0xC1900101 – 0x40017
The installation failed in the SECOND_BOOT phase with an error during the BOOT operation.



This would be the configuration of the VM:

agent: 1,fstrim_cloned_disks=1
bios: ovmf
boot: order=ide2;scsi0
cores: 4
cpu: host
efidisk0: Tnas01-Vm:112/vm-112-disk-0.raw,efitype=4m,pre-enrolled-keys=1,size=528K
ide2: Tnas01-Iso:iso/server_2025_26100.1.240331-1435.GE_RELEASE_SERVER_X64FRE_EN-US.ISO,media=cdrom,size=5110888K
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=8.1.2,ctime=1702735584
name: SrvPrt01
net0: virtio=BC:24:11:7B:35:64,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win11
scsi0: Tnas01-Vm:112/vm-112-disk-1.raw,discard=on,iothread=1,size=40G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=16d12cd0-5920-483b-87a2-6231d8b2844f
sockets: 1
tags: Win2022
tpmstate0: Tnas01-Vm:112/vm-112-disk-2.raw,size=4M,version=v2.0
vmgenid: 159880a5-6d94-411b-8eed-9fc6be68b3f8

I have also installed the latest VirtIO tools (0.1.262)

Does anyone have an idea how I can solve this?

Many thanks and best regards

 

[itNGO]

Try clean install.... inplace Upgrades are not recommended. Even Microsoft itself says, clean install is recommended....
btw.. this has not really to do with PVE....

Else here is the error-code list from MS. It is the same for 22 to 25...
0xC1900101 – 0x40017 - https://learn.microsoft.com/de-de/t...vers/windows-10-upgrade-resolution-procedures

 

[MisterDeeds]

Try clean install.... inplace Upgrades are not recommended. Even Microsoft itself says, clean install is recommended....
btw.. this has not really to do with PVE....

Else here is the error-code list from MS. It is the same for 22 to 25...
0xC1900101 – 0x40017 - https://learn.microsoft.com/de-de/t...vers/windows-10-upgrade-resolution-procedures

Thank you for your answer!

Unfortunately, a new installation is not an option for us. We have about 50 systems which we would have to completely reinstall, so only the Inplace Upgrade is an option for us.

Ans thanks for the link. That is very interesting that Microsoft attributes the error to Citrix VDA. We have and have never used Citrix Apps. Interestingly, the identical error appears for all servers 2022 in the entire cluster.

Has anyone else had this problem?

 

[itNGO]

I think the problem is already known. Inplace Upgrades sometimes fail at second reboot.... I guess you have to wait until Microsoft provides a fix.,
In a german blog someone reported about this issue.
https://www.borncity.com/blog/2024/10/17/probleme-mit-windows-11-24h2-windows-server-2025/

HP ProLiant Microserver Gen10 Plus v2
An HP ProLiant Microserver Gen10 Plus v2 with Windows Server 2022 caused problems. Cedric wrote to me that he could not perform an inplace upgrade from Windows Server 2022 to Windows Server 2025 even after many attempts. The update process always aborts after the second start, and then the changes are undone by the inplace upgrade.

At first it was probably due to the graphics driver, the reader wrote. But even after that, the upgrade always aborts at the same point, although Cedric has tried everything (SFC, DISM, current BIOS, current ILO, current drivers, etc.).

The logs say something about a filter driver, which is probably used for symlinks, as the cause of the error. But the reader is not using this. Only services for a file server such as DFS are running there.

In comparison, the reader was able to upgrade a file server at another location with DFS etc. without any problems. Cedric suggests that, in his opinion, it must be the microserver itself.

When upgrading to a domain controller to 2025, there was an RPC error on the first attempt. A second attempt was then successful.

Older servers such as ProLiant DL380 Gen9, on the other hand, could be upgraded from Windows Server 2022 to Windows Server 2025 without any problems.

Translated with www.DeepL.com/Translator (free version)

 

[MisterDeeds]

I think the problem is already known. Inplace Upgrades sometimes fail at second reboot.... I guess you have to wait until Microsoft provides a fix.,
In a german blog someone reported about this issue.
https://www.borncity.com/blog/2024/10/17/probleme-mit-windows-11-24h2-windows-server-2025/

Hi and thanks for the answer and the link.

I have now tested it on 6 different PVE clusters and the error is identical everywhere. It may be due to the VirtIO drivers. But the only thing to do is to wait for a patch from Microsoft...

Thanks anyway and best regards