It sounds like your VM config was presenting a COU or TPM config that the upgrade wasn’t comfortable with. If your new machine presented acceptable configs to a brand new VM, then making a new VM and feeding it the old .vhdx would be the same as pulling a storage device and putting it in a new motherboard that was win 11 compliant. After a reboot to install new drivers it probably would have upgraded happily.
Hmm, the only barrier to upgrading was that the i5 processor wasn’t supported, no complaints about TPM/motherboard compatibility and a fresh install worked fine on the exact same hardware. Oh well, it’s done anyway.
It sounds like your VM config was presenting a COU or TPM config that the upgrade wasn’t comfortable with. If your new machine presented acceptable configs to a brand new VM, then making a new VM and feeding it the old .vhdx would be the same as pulling a storage device and putting it in a new motherboard that was win 11 compliant. After a reboot to install new drivers it probably would have upgraded happily.
Hmm, the only barrier to upgrading was that the i5 processor wasn’t supported, no complaints about TPM/motherboard compatibility and a fresh install worked fine on the exact same hardware. Oh well, it’s done anyway.