VM update from Server 2022 to Server 2025

M

MisterDeeds

Active Member
Nov 11, 2021
142
32
33
34
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.

1729000398461.png

This would be the configuration of the VM:
Code: 
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
 
  • Like
Reactions: Johannes S
itNGO said:
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
Click to expand...
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?
 
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)
Click to expand...
 
itNGO said:
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/
Click to expand...
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
 
mbosma said:
Does it work if you change the OS disk to IDE?
If so, after the upgrade you could add another disk as virtio-scsi, install the drivers and change your OS disk back to virtio-scsi.
Click to expand...
The system cannot be started after the hard disk is changed to IDE, blue screen error code Error code: 0x000000f
Switch to safe mode and restart to enter the system, but the installation of win11 still fails:
We've set your PC back to the way it was right before you started installing Windows 11.
0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation
 
Last edited:
dorayy said:
Vmware already has a solution. I wonder if proxmox has any way to deal with it?
https://knowledge.broadcom.com/external/article/318260/guest-os-inplace-upgrade-to-windows-serv.html
Click to expand...

For upgrading to Windows Server 2022, make sure guest network is connected while performing guest OS in-place upgrade, or take the following steps which also apply to upgrading to Windows 11:​


So change your NIC before upgrade to something that is always there. like Intel E2000 and try again... might be worth a try...
 
itNGO said:

For upgrading to Windows Server 2022, make sure guest network is connected while performing guest OS in-place upgrade, or take the following steps which also apply to upgrading to Windows 11:​


So change your NIC before upgrade to something that is always there. like Intel E2000 and try again... might be worth a try...
Click to expand...
It's still the same failure error. My solution is to export the virtual machine backup to vmware and migrate the mirror image back to proxmox after upgrading.

I hope there is a good solution.
 
Hi

In my case, it worked like this. I had to change the hard disk to SATA. Plus enlarge the partition to at least 65GB. If this is smaller, an error message appears during the upgrade asking you to free up disk space, even though there is actually enough free space... After the update, the hard disk can be reset to SCSI. Many thanks for the tip @mbosma

1730888319858.png
If a blue screen appears after the hard disk is mounted as SCSI again, this can be resolved using the following instructions.
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000kAWeCAM
 
Last edited:
  • Like
Reactions: mbosma
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back