Windows 11 kicked me out of WIP on Windows 11.

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

Files in folder C:\ProgramData\Microsoft\Windows\Hyper-V are those to keep in safe.

Change Hyper-V Virtual Machines Default Folder in Windows 10 | Tutorials (tenforums.com)

You can use Hyper-V export and import functions. (Export copy files to selected folder/disk, not move.)

How to Import and Export Hyper-V VMs with PowerShell (adamtheautomator.com)

Hi Pauli,

I think I'm done playing with VM for now, the whole thing is quite messy.

Tried VMware and Hyper-V, not a fan of either one.

I may go through the exercise again if I'm getting bored and have nothing else better to do, but the more I use VM on PCs the less I like it. 😒

Thanks for the links, I'll save those for next time.

Cheers.

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

Files in folder C:\ProgramData\Microsoft\Windows\Hyper-V are those to keep in safe.

Change Hyper-V Virtual Machines Default Folder in Windows 10 | Tutorials (tenforums.com)

You can use Hyper-V export and import functions. (Export copy files to selected folder/disk, not move.)

How to Import and Export Hyper-V VMs with PowerShell (adamtheautomator.com)

Not sure why it worked for me and not for you, is your host yellow zone? meaning CPU is the only non-compliant item?

Have a good one, thanks for all your input.

My current Host is like 10 yrs old, i7 2600 thus the CPU issue for me. Be all good on new system.

@fg,

The files representing the VM's "hardware" for the Windows 10 digital license are the .VMCX .VMGS and .VMRS files, plus an empty folder by the same name as the 3 files

Regards,

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.

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

I guess you didn't see my edit:

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

Not sure why it worked for me and not for you, is your host yellow zone? meaning CPU is the only non-compliant item?

Have a good one, thanks for all your input.

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.