Win 11 Boot And Upgrade FiX KiT (v5.1f Released!!!)

I down loaded the tool twice and couldn't unzip it both times. Don't know if you need a password or what???
So used Rufus (MBR and NTFS) to make a win 10 install usb and took install.esd off the usb - replaced it with install.wim off the W 11 iso.
My old I5-3450 @ 3.10 is humming along w/o issues. UTube - How to INSTALL Windows 11 Error FREE on ANY PC - TECH YES CITY.

 

What I ended doing was this:
Took build 22449 used the kit with option 2
Then used WINRAR to unrar it to the flash drive.
Then booted from the flash drive and did a clean install on another drive.

Ran fine and now have the Channels in the Insider but can't use anything but the preview channel.
Tells me here that my hardware won't work with the other channels.

So, I will get the new builds from UUP and get the updates for 22449 from Windows Update..

 

Easiest way to bypass TPM and other check is to install build 22449 to an external SSD Drive as Windows to Go using Rufus. Tested it on 3 non TPM computers and it worked like a charm.

 

Indeed, there is not a big difference between your original script and my first update; I changed the way to get the FIX value and rearranged the script by using IF Else block structure to eliminate goto statement; the exit /b are changed to goto cleanup (sometimes goto statements are useful!) and the original device/folder are restored by the popd statement.
The later version of the script introduces powershell statements invoked after the FIX value is provided by the user's choice. The GUI lets the user navigate to select the W11 and W10 ISOs located on his/her system. The full pathes of the ISOs are provided as the contents of the temp\w10 and temp\w11 files (this allows the communication between powershell and cmd). After creation of these two files, control is returned after the powershell call to process the remaining cmd statements. The tests for the existence of the W10 and w11 ISOs is suppressed because they are selected by the powershell GUI.

 

I think RPO trying take over your tool
Don't let him. go to fight.

 

I was able to find a reg edit file that changes you to the DEV Channel. On Build 22449 I am on the DEV channel, and on the 22000.176 I have no channels.
Think that is because I used option 1 in the kit and put the Windows 10 boot there instead of Option 2 that is all Windows 11.

 

Is this what you want??

 

This is from Build 22000.176
And this is the key:

 

This is what mine shows..

 

Keep in mind I did an upgrade from Windows 10 to 11. Not a clean install like I did on another drive with 22449.1000..

 

i did option 1 and did an upgrade to my Windows 10 to Windows 11.
I did option 2 and did a clean install of build 22449.1000 to an entirely different drive.

The 22449 build I tweaked the registry to go back to the DEV channel.
however, you have the screenshot from my 22000.176 upgrade. Can't even sign up for the insider program due to the error ..
I copied the key from 22449 to 22000 to see if it would work. No go..
When I rebooted the 22000 build it put back the original key. This is the screenshot I have posted..

Hope this helps with your question.....

PS: And all the screenshots posted are from the Windows 10 to 11upgrade with build 22000.176.

 

Then the question becomes, What happened during the upgrade that caused Build 22000.176 to kick me out of the Insider Program and won't let me back in, where when I did a clean install on another physical drive with Build 22449.1000 I AM in the Insider Program. I just had to change the registry key to the Dev Channel????

 

If you are right, then what should I do???
According to the Windows update history, The first Windows 11 Build I installed was 10.22000.51.
Is that the problem? I should have installed 22000.1 first???