Why didn't installing Win10 image on Win11 system work?

[Robert P]

I got a new system specifically for gaming with much more robust specs than my old Win10 rig. This new one came with Win11, to avoid downloading gigs and gigs of game files via my pokey 10 megabit DSL connection I was going to try and save time reinstalling the games that are on my older Win10 system by taking a Macrium image of the Win10 system and putting it on the new system and upgrading that to Win11 since it has a supported CPU.

Fortunately I had the foresight to make a Macrium image of the new system drive in case things didn't go as hoped - and they didn't.

Used a Macrium restore disc, and the Win10 Macrium image installed but wouldn't boot to the desktop, it kept booting to the UEFI/BIOS.

Fortunately the image I saved of the Win11 system reinstalled without a problem but obviously I've run into a barrier of awareness - any insights as to why this didn't work?

The one positive thing I got out of it is seeing how fast things go on this new system - the data transfer from the USB drive over the USB-C connection is screaming fast compared to USB-2. The Macrium install takes a fraction of the time.

Thanks

 

[beers]

Was your previous install reliant on CSM or legacy BIOS where you have a UEFI only environment now?

W10 and up are a bit better with transplants but it gets tricky between MBR/GPT and BIOS/UEFI

 

[Robert P]

Was your previous install reliant on CSM or legacy BIOS where you have a UEFI only environment now?

W10 and up are a bit better with transplants but it gets tricky between MBR/GPT and BIOS/UEFI

If by legacy BIOS you mean something like this that's what my Win10 rig uses.

 

[Firewatcher]

If it is a System Image you are trying to restore, it will only restore to the same machine (System) it came from, regardless of which OS you are using. Explains why the new Syatem Image restored without hitch, beacuse it came from the new machine.
Pete