Forum Discussion
Solved
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.
SetupDi...
- 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
Good morning,
I managed to do an in-place migration from 2022 to 2025 by modifying the boot store:
Bcdedit /set flightsigning on
Preview certificates are not the same as RTMs.
Sincerely
Hi Luc, the flight signing is enabled. We are looking at a different issue as Michael outlined in the posting above.