Windows 11 kicked me out of WIP on Windows 11.

""BypassSecureBootCheck"=dword:00000001" in LabConfig key does not bypass with 22449.

Ended up using the ISO for in-place upgrade. Had to copy the setup files to SSD and rename the Sources dll file to .bak to get it to upgrade. This non-compliant laptop is running 22449.

Hi Johnny, hope you enjoyed your movies.

dword should be just 1 without zeros. I also ended up using an ISO to update the Raspberry, all ok.

After 3 failed attempts the Laptop was struck by the taskbar fiasco, restore .168 backup, waited a bit and finally updated to 22449, is the only amd64 device I have left on Dev

Yes, the dword value is 1, that is how you have to put it if using in a *.reg file I suppose. I like the simple one click and all registry values get entered in one shot. I will try again next week build with what you suggest. That value still changes it 1. Not a coder, that was the way I got them.

The movie was great escape, not sure how many times I've seen it. Love the part with Steve McQueen on the motorcycle. That boy could ride.

Did get the taskbar fiasco on one Beta vm. Ended up clean installing in that one. Didn't see the fix till after it was done. That vm still had a base snapshot of 21390, it was due.

Enjoy your long weekend, definitely not going to waste it in here. Winter comes fast in Canada. lol

Cheers!

Suggest for you to hop on the VMware or Hyper-V bandwagon. The virtual machine is Legacy on 10 yr old Legacy desktop, an i7 2600.

Hi Johnny,

I installed Beta Build 22000.132 on Hyper-V. UEFI install.

I don't know where to go from here. I have a couple of questions to you.

1. How to activate the VM install ? Do I need a new Windows 10/8/7 product key ? I had a HP notebook. It had a product key on the sticker. Can I use that ? The notebook has no longer the pre-installed Windows build on it. Not used.
2. Can I use my Microsoft account info here in VM as well ?

If you have opinions on above questions, I appreciate your opinions.

Regards

Hi suat,

Not sure about the HP product key, probably not due to mismatch hardware, wouldn't hurt to try.

I'm 100% sure you can still use a Windows 7 key and upgrade straight to Windows 11 on a VM or a PC.

https://answers.microsoft.com/en-us/insider/forum/all/upgrading-windows-7-to-windows-11-insider-preview/70bf973c-88ea-45b6-bbe7-95978a5957d6

Later tonight when watching movies, will see what happens with the non-compliant laptop using that script if it takes through WU.

Hi Sibro,

WU did come through with the upgrade using script. Once it checked PC, blocked due to no TPM, CPU and Secure Boot were listed. I could bypass the TPM and CPU in different HKEY_LOCAL_MACHINE key but could not get around the Secure Boot yet with WU. Have to work on this one, MS changed something here.

""BypassSecureBootCheck"=dword:00000001" in LabConfig key does not bypass with 22449.

Ended up using the ISO for in-place upgrade. Had to copy the setup files to SSD and rename the Sources dll file to .bak to get it to upgrade. This non-compliant laptop is running 22449.

Hi Johnny, hope you enjoyed your movies.

dword should be just 1 without zeros. I also ended up using an ISO to update the Raspberry, all ok.

After 3 failed attempts the Laptop was struck by the taskbar fiasco, restore .168 backup, waited a bit and finally updated to 22449, is the only amd64 device I have left on Dev

Later tonight when watching movies, will see what happens with the non-compliant laptop using that script if it takes through WU.

Hi Sibro,

WU did come through with the upgrade using script. Once it checked PC, blocked due to no TPM, CPU and Secure Boot were listed. I could bypass the TPM and CPU in different HKEY_LOCAL_MACHINE key but could not get around the Secure Boot yet with WU. Have to work on this one, MS changed something here.

""BypassSecureBootCheck"=dword:00000001" in LabConfig key does not bypass with 22449.

Ended up using the ISO for in-place upgrade. Had to copy the setup files to SSD and rename the Sources dll file to .bak to get it to upgrade. This non-compliant laptop is running 22449.

Suggest for you to hop on the VMware or Hyper-V bandwagon. The virtual machine is Legacy on 10 yr old Legacy desktop, an i7 2600.

Hi Johnny,

I installed Beta Build 22000.132 on Hyper-V. UEFI install.

I don't know where to go from here. I have a couple of questions to you.

1. How to activate the VM install ? Do I need a new Windows 10/8/7 product key ? I had a HP notebook. It had a product key on the sticker. Can I use that ? The notebook has no longer the pre-installed Windows build on it. Not used.
2. Can I use my Microsoft account info here in VM as well ?

If you have opinions on above questions, I appreciate your opinions.

Regards