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.
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
MSBernstein
Microsoft
MicrosoftUpdate 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
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
Hi MSBernstein this did the trick.
But only for GUI. Core again fails way before as outlined in a previous reply.
for GUI we seem to have a new issue when dynamic memory is enabled.
The extra mile would be if this is 2025 specific or even happened before. It is very common to have dynamic memory enabled. And it is set to 512 min / 512 startup mem here.
It would be great if setup could check this when checking the requirements or we have a more transparence error message when it fails.
edit: another test with dynamic memory on, showed that dynamic memory itself is not the issue.
Using dynamic memory with 1 GB startup memory, 512 GB min memory works fine with the upgrade, so it is certainly the startup memory that should be 1 GB or more.
