Forum Discussion
Windows 11 23H2 → 25H2 in-place upgrade fails in SAFE_OS / MIGRATE_DATA
The steps outlined by SumtDhiman did work allowing me to upgrade from 23H2 to 25H2. However, once the upgrade was complete, I began to do normal check and installs of Win11 updates. They worked for a couple of iterations, then 25H2 crashed. The system would not boot after that. I wound up restoring with my drive from a good 23H2 backup. My 23H2 has tpm.sys at 10.0.22621.6274.. On another PC with 25H2, tpm.sys is at 10.0.26100.7705. Should I have manually updated tpm.sys to a 25H2 flavor immediately after the upgrade and before any new Win updates are installed?
The Microsoft Devs I've been in communication with have said they are still investigating the issue and have not yet found a clear solution, but have acknowledged that this is a wide-spread issue that appears during the Migration and SafeOS phase of the upgrade, specifically when attempting a migration from 23H2 to 25H2. When I looked it up, it turns out 25H2 has changed the way certain optional components are made available/installed, while other components are outright stripped from the image that are trying to be migrated from 23H2, causing failures/errors. 24H2 did not make these changes, so I am able to upgrade to 24H2 just fine, while then installing the small 25H2 enablement package in my final task sequence step/reboot. This seems to be the only solution at this time. A jump to 25H2 works at random but isn't reliable and seems unstable in the backend/payload migration process. Shame on the MS Devs for releasing this build without proper testing.
