Windows 11 kicked me out of WIP on Windows 11.

Guess that's why they call it Player, a stripped down version.

Today appears to not be a good day. The clean install went perfect. This second vm, set a base snapshot of 22000.132 offline. Went to upgrade 22458 offline, complained about CPU not meeting requirement. One of those days....lol.

Edit: Using same 2nd vm and ISO, did clean install after snapshot. That went through without concern.

Appears will have to play the game till I move these vm's to the new system. Build 22458 does not do CPU check on clean install, it sure does on upgrade. Suspect next week going to be interesting when others do not have compliant CPU's doing an upgrade. The adventure continues.

Hi Sibro,

Worked like a charm. Appreciated. Guess never paid close enough attention as this was never an issue prior. Always something new to learn. Cheers!

Created a new vm, copied over 3 small files from activated vm. Retained activation after clean install:

No problem, glad you made it.

Which files are those that should be copied?

The second vm gave me issues. I copied .nvram, .vmx and .vmxf. Not positive which one would hold that info. perhaps down the road can play with this. Maybe only one or two of them is needed.

First one went smooth. This one, first mistake was having snapshots on original vm prior to copying over. Cleared those. Think we have to copy the 3 files prior to Encryption. This one took me several tries to get going. Thought I did exactly same as before. Appears to be a certain combination of events, encrypt, copy, de-encrypt, set bios again, encrypt, not sure.

Went through a lot of back and forth, it finally proceeded. Think I need a Canadian Gummy right now.

Hi Johnny,

I'm using this VM for Beta channel testing, I didn't need to enable TPM, I did it to experiment. Now it won't boot to firmware anymore (please check yours).

Not sure what to do or how to star over without losing activation. I could install Windows 7 again and start from scratch, but I'd like to save this one if possible.

Any suggestions?

Hi Johnny,

Fine here with Clean Install of 22458.1000 on Hyper-V set for Generation 2 and TPM enabled in the Virtual machine.

No need to encrypt the Virtual Machine either.

The host is the old Legacy BIOS MSI GT70 Laptop.

Just another experiment for me, I'm not really a fan of VM on PCs.

PC Health check results in the bottom picture, as expected processor is flagged red, but no red message on Windows insider page.

The clean install put this VM directly on Development, I just had to link the account as asked.

👍

As expected, here are the results of PC Health Check,, showing red for thr processor even if no red or yellow message on the insider page.:

I'm using this VM for Beta channel testing, I didn't need to enable TPM, I did it to experiment. Now it won't boot to firmware anymore (please check yours).

Not sure what to do or how to star over without losing activation. I could install Windows 7 again and start from scratch, but I'd like to save this one if possible.

Any suggestions?

The question would be did you start a new vm, or reuse an existing one that was previously activated. If new vm, was it activated prior to issue. This going to fall under old rules, if it ever was activated, it will remain so.

I have not used the firmware method since trying it that one day. Still using the restart from working vm. Perhaps, if this machine was activated, start a new vm, copy the 3 files over, play around with the settings. It should just boot from mounted image as new install.

Not sure if you seen previous post, the clean install of 22458 works, not an upgrade from 22000.132 without bypassing CPU. Starting fresh in same vm with 22454 and then will upgrade. Positive it will catch CPU not meeting requirements. Seems the install is not checking CPU requirements on clean install, but does on upgrade.

I'm using this VM for Beta channel testing, I didn't need to enable TPM, I did it to experiment. Now it won't boot to firmware anymore (please check yours).

Not sure what to do or how to star over without losing activation. I could install Windows 7 again and start from scratch, but I'd like to save this one if possible.

Any suggestions?

The question would be did you start a new vm, or reuse an existing one that was previously activated. If new vm, was it activated prior to issue. This going to fall under old rules, if it ever was activated, it will remain so.

I have not used the firmware method since trying it that one day. Still using the restart from working vm. Perhaps, if this machine was activated, start a new vm, copy the 3 files over, play around with the settings. It should just boot from mounted image as new install.

Not sure if you seen previous post, the clean install of 22458 works, not an upgrade from 22000.132 without bypassing CPU. Starting fresh in same vm with 22454 and then will upgrade. Positive it will catch CPU not meeting requirements. Seems the install is not checking CPU requirements on clean install, but does on upgrade.

I'm using the same activated VM that didn't have TPM enable before yesterday. I enabled TPM and I as said earlier, I was able to start the update from 22000.184 to 22454 without any problem, but I didn't update (screenshot on page 7 of main thread). I could have if I wanted to though, no tricks or hacks needed.

This activated VM is now free of TMP and encryption, but cannot boot to firmware anymore as it used to. So, how do I boot from virtual cd-rom in case I want to clean install and keep activation?

Never mind, I lost it, it's gone. I must have done something wrong. I'll start a new one from scratch.

Thanks for the info.

ok not lost after all, found a previous copy and I'm back pre-TPM, boot to firmware is working again. 😁