Forum Discussion
ISSUE - FIXED - Hyper-V VM In-Place Upgrade (IPU) WS 2022 to WS 2025 b26063 fails
Host: WS b26052
VM: WS 2022 20348.2227
Target OS: WS 2025 26063.1000
IPU, dynamic update enabled
Flightsigining: on
Error: Rollback after upgrade online phase on first reboot.
SetupDiag: processing rule: FindRollbackFailure.
.....
Error: SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Cleanup external drivers after installation
Error = 0xC1900101-0x20017
LogEntry:
Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.
SetupDiag found 1 matching issue.
Any ideas? Quite unusual for Hyper-V VMs.
- Update on this investigation:
The Windows Boot team looked over logs from my repro and noticed that the upgrade sequence depends on creating a large (500MB) RAM disk and that ramdisk creation is failing due to not enough memory. Since the documented recommendation for Windows Server with Desktop Experience is 2GB, I turned off Dynamic Memory and set the RAM to 2048 GB.
This resolved the issue for me - in-place upgrade now succeeds.
Karl, can you please see if that same mitigation works for you?
If so, I can follow up with the MSLab owners to see if they can change the memory configuration.
Thanks,
Michael
17 Replies
- Hi Luc, the flight signing is enabled. We are looking at a different issue as Michael outlined in the posting above.
installed a fresh VM and will try to reproduce it.
So far when continuing the setup after enable flighting. setup comes up with the "Ready to Install Windows 11"- This is creepy - this is way too much "client creep into server OS"...
MSBernsteinMicrosoft
Hi, Karl,
This is quite odd - we do Server 2022 -> Server 2025 upgrades often in our automation. So, I'd like to figure out what is different.
A few clarifying questions:
1. What generation is the VM?
2. How many GB of RAM? (Doubtful it matters, just checking)
3. Where are you getting the WS2022 image?
4. And from where are you getting the WS2025 image to upgrade to?
I'd like to avoid coming back and saying, "well, I couldn't reproduce it."
Same result. Does WS 2025 require (v)TPM? From techcommunity answer I understood that's only on later HW but not for VMs.
So I have now:
- enabled vTPM and VBS / Core Isolation on the VM. This didn't change a thing.
- The procedure is a as follows:
- online phase of the setup runs well until VM restart
- Then there's a short shutdown (about 3 seconds) -
- NO applying phase during shutdown and no applying phase during startup
- The old OS get's immediately booted on first reboot. You do not even see the "rollback" to the old version
- bcdedit will have a leftover entry from setup
This behaviour is very strange, I am open for further diags if you like. Thanks for your time!
This one seems to be very reproducible.
The host OS is now WS b26063 but no change from b26053 when I first posted it.
