Windows 11 kicked me out of WIP on Windows 11.

Guess we both having bad day. Just started clean again, using 22454 ISO. This time using firmware. Responded fine, after I pointed ISO location in Settings. Forgot first time, so nothing was happening using CD option. Update with 22454 works, not 22458 without bypass. Not sure if that was typo on version.

This is all new to me, you mentioned free of encryption. Using encryption leaves key info in the .vmsd file. Maybe that had to be cleared out within that txt file as well.

Legacy partial vmsd:

.encoding = "windows-1252"

snapshot.lastUID = "2"

snapshot.current = "2"

snapshot0.uid = "1"

snapshot0.filename = "Win 11-Snapshot1.vmsn"

snapshot0.displayName = "Base"

snapshot0.description = "22000.132"

snapshot0.createTimeHigh = "379734"

snapshot0.createTimeLow = "-256695560"

snapshot0.numDisks = "1"

snapshot0.disk0.fileName = "Win 11.vmdk"

snapshot0.disk0.node = "scsi0:0"

snapshot.numSnapshots = "2"

snapshot.mru0.uid = "2"

UEFI with encryption vmsd:

.encoding = "windows-1252"

encryption.keySafe = "vmware:key/list/(pair/(null/%3cVMWARE%2dEMPTYSTRING%3e,HMAC%2dSHA%2d1,DguMVba1p4PE4maN9Rh4eCu6SwBBncJFqZjTRs8udn%2f20wVN0vsH5%2bdF7AlToXbcJtOWOInXsviPDc65R9zbBRD2oo7%2bX0GOU3Xj941ztnZETgiarI5%2bCsIsj9Z8kT2LjPllypwQmls%2bVV3cSV3moehqaC0%3d))"

encryption.data = "noL9mo1jQdDtpcgIubkwZZZGGTkc5/lgOfi9sCSj4cBPVktFocqn6DeopzzC4X2gA2u4giuAl6k3/jycezfwq+kpT6j7MT1jGMm4xLRGCLYBqIIW"

Think I may call it a night, start fresh tomorrow. Not been a good day.

Now I wish I knew which files to save for the Hyper-V VM in case I need to go through this again. ?? 😉

Hi fg,

Johnny posted which files you need to save, it was last week I think.

Hi Sibro,

Just got something weird with my activation. for VM Hyper-V.

It did not like the key, I said my hardware was changed recently and it made me login the account and pick the machine I'm using,

It reactivated it.

Now I wish I knew which files to save for the Hyper-V VM in case I need to go through this again. ?? 😉

The S/N returned by the Hyper-V Virtual Machine is quite long, completely different format than the real machine, 26 digits long :

Microsoft Windows [Version 10.0.22458.1000]

(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>wmic bios get serialnumber

SerialNumber

xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx

C:\Windows\system32>

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. 😁

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.