Solved Windows 11 Insider System Expelled from Program

Have a Windows pro system that was created as a Hyper-V type one system (MBR boot) and was originally on the W10 insider program. I upgraded? it to W11 insider as soon as that program started. All was fine until the last update, then I got this message -



The specs for this system are here -


Since this is a VM, I can easily revert back to W10 using an earlier checkpoint. When my other 11 Insider in the DEV channel went to build 22458, this one was "kicked out". I assumed that this or something similar would happen based on all of the warnings M.S. has issued.

Latest info from Microsoft is that, when using Hyper-V, Windows 11 VMs need to be set up as Generation 2. Not having used Hyper-V for a long time I'm not sure if it's possible to convert an existing VM from Generation 1 to 2, or if reinstallation is necessary.

LeLibran said:

Latest info from Microsoft is that, when using Hyper-V, Windows 11 VMs need to be set up as Generation 2. Not having used Hyper-V for a long time I'm not sure if it's possible to convert an existing VM from Generation 1 to 2, or if reinstallation is necessary.

Click to expand...

Agreed. This particular system was created as a gen 1 when I first got involved with Hyper-V. Don't remember why a gen 1, maybe just beginner's ignorance. Anyway it doesn't matter. I just wanted to see what would happen to it, what with all of the incompatibility warnings from M. S. I still have an 11 system in the beta flight and one in the dev flight.
edit
I think there is a warning when setting a Hyper-V VM the selected generation CAN NOT be changed. When it is no longer useful as an 11 Insider, I'll just revert back to 10.

If it's of any interest, I've found a brief guide here: Convert Hyper-V virtual machines from generation 1 to 2

@LeLibran - Interesting article, but it is actually only converting the drive from MBR to GPT. It goes on to say -

Quote:

Transferring VHDs to new VMs ^​

Since it is not possible to convert a Gen 1 VM to a Gen 2, you must now create a new Type 2 virtual machine and connect the VHDs to it.

End Quote:

​

Good info though, Thanks
Gary