Solved In place upgrade Windows 11 v 24H2 build 26058.1100 to 26063.1

1.Download insider preview Windows 11 Pro v24H2 build 26063.1 from uupdump. net
2. Prepare bootable usb of Windows 11 v 24H2 build 26063.1from link Install Windows 11 v 23H2 on unsupported pc without using command prompt by using bootable usb prepared manually within current Windows OS.
2.I have attatched bypass11.zip and images of upgradation in my pc.
3. Please read the above said post and prepare a bootable usb of Windows 11 v 24H2 build 26063.1
4. This bootable usb works well for installation and in place upgradation.
5. To safely update from within current Windows, right click on file Quick_11_iso_esd_wim_TPM_toggle to run as administrator. This adds send to option to iso in context menu. It means that if we right click on the iso downloaded from uupdump. net, it gives send to Quick_11_iso_esd_wim_TPM_toggle. This patches the downloaded Windows 11 iso.
6. Alternatively we can drag and drop the iso on file Quick_11_iso_esd_wim_TPM_toggle, this patches TPM. But to make bootable usb to clean install , file auto must be run as administrator, from within current Windows running on pc.
7. Then mount the patched iso on virtual drive. Explore, run setup.
8. To clean install from bios, keep usb as first boot device.
9. Thank you all for reading this post.
10. Upgradation did not erase anything on my pc. All previous data on OS partition are safe. All user files are safe.

I have tried your script but it assumes ISO is for the server, and SETUP.EXE prompts for Server ID.
Here is paste from your script:


#:: TPM patch via InstallationType Server
$typeC = '<INSTALLATIONTYPE>Client'; $typeS = '<INSTALLATIONTYPE>Server'
$block = 1048576; $chunk = 2097152; $count = [uint64]([IO.FileInfo]$input).Length / $chunk - 1
$bytes = new-object "Byte[]" ($chunk); $begin = [uint64]0; $final = [uint64]0; $limit = [uint64]0
function tochars {return [Text.Encoding]::GetEncoding(28591).GetString([Text.Encoding]::Unicode.GetBytes($args[0]))}
$find1 = tochars "</INSTALLATIONTYPE>"; $find2 = tochars "</WIM>"; $cli = tochars $typeC; $srv = tochars $typeS

mlivshin said:

I have tried your script but it assumes ISO is for the server, and SETUP.EXE prompts for Server ID.
Here is paste from your script:


#:: TPM patch via InstallationType Server
$typeC = '<INSTALLATIONTYPE>Client'; $typeS = '<INSTALLATIONTYPE>Server'
$block = 1048576; $chunk = 2097152; $count = [uint64]([IO.FileInfo]$input).Length / $chunk - 1
$bytes = new-object "Byte[]" ($chunk); $begin = [uint64]0; $final = [uint64]0; $limit = [uint64]0
function tochars {return [Text.Encoding]::GetEncoding(28591).GetString([Text.Encoding]::Unicode.GetBytes($args[0]))}
$find1 = tochars "</INSTALLATIONTYPE>"; $find2 = tochars "</WIM>"; $cli = tochars $typeC; $srv = tochars $typeS

Click to expand...

Hello @mlivshin,
1. Download windows 11 insider preview iso from uupdump.net
2. Though installation shows server title, it installs Windows 11 Pro.
3. This is well known tool by Ave Yo from github, the link is GitHub - AveYo/MediaCreationTool.bat: Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2!
4. I have used this media creation tool, but never have been prompted to input server ID.
5. Download code> zip file.
6. Hope this solves the issue.
7. Thanks.

Hmm.. I wanted to do the upgrade from 23H2 Build 26040.1000 but it either BSOD, or script converts to Server (I verified it few times, direct ISO, mounted and executed SETUP.EXE installing Windows 11, and after running the script, SETUP.EXE attempts to install Server and prompts for the ID. This is my experience so far. I have tried at least three different options attempts, and redownloaded ISO from UUPDUMP.NET three times.

mlivshin said:

Hmm.. I wanted to do the upgrade from 23H2 Build 26040.1000 but it either BSOD, or script converts to Server (I verified it few times, direct ISO, mounted and executed SETUP.EXE installing Windows 11, and after running the script, SETUP.EXE attempts to install Server and prompts for the ID. This is my experience so far. I have tried at least three different options attempts, and redownloaded ISO from UUPDUMP.NET three times.

Click to expand...

May I know the sequence of your steps?
This tool is perfectly working for 24H2.
Before running the tool directly first patch the iso as said in steps 5 and 6 in post #1. You can adopt any one method once. Second click removes the patch. Please see the message on screen which stays for 5 seconds.
If clicked twice original iso remains without patch.
Please have a look at step 2 in post#1
I studied this tool many times then followed the on screen meassge.

I have tried both, Step 5 and Step 6. Both steps successfully patch ISO removing TPM check.,
I then mount ISO with Windows File Explorer, and from the virtual D: drive run SETUP.EXE.
This has been standard all along.
However, when I run SETUP, after ISO has been patched, instead of WINDOWS 11 and attempts to install WINDOWS SERVER and prompts for the ID.

mlivshin said:

I have tried both, Step 5 and Step 6. Both steps successfully patch ISO removing TPM check.,
I then mount ISO with Windows File Explorer, and from the virtual D: drive run SETUP.EXE.
This has been standard all along.
However, when I run SETUP, after ISO has been patched, instead of WINDOWS 11 and attempts to install WINDOWS SERVER and prompts for the ID.

Click to expand...

Try running auto as administrator.
Try any one patch methods, only once.
Do you get the message "Patched"?
By running "auto" as administrator, the process of upgradation should start immediately, without any prompts. But it is safe for data on pc.

same thing, it turns ISO into SERVER .. see the contents of the script. There is nothing to indicate there to patch WINDOWS 11.
Only Server:
#:: Can force either patch or undo via second commandline parameter: 1 to patch 0 to undo
if (1 -eq $env:2) {$toggle = 1} elseif (0 -eq $env:2) {$toggle = 0} else {$toggle = 2}

#:: Verify extension is .iso .esd or .wim
$input = get-item -lit $env:1; $invalid = '.iso','.esd','.wim' -notcontains $input.Extension
if ($invalid) {write-host "`n Input is not a iso / esd / wim file ...`n" -fore Yellow; return }
try {[io.file]::OpenWrite($input).close()} catch {write-host "`n ERROR! $input read-only or in use ...`n" -fore Red; return }

#:: TPM patch via InstallationType Server
$typeC = '<INSTALLATIONTYPE>Client'; $typeS = '<INSTALLATIONTYPE>Server'
$block = 1048576; $chunk = 2097152; $count = [uint64]([IO.FileInfo]$input).Length / $chunk - 1
$bytes = new-object "Byte[]" ($chunk); $begin = [uint64]0; $final = [uint64]0; $limit = [uint64]0
function tochars {return [Text.Encoding]::GetEncoding(28591).GetString([Text.Encoding]::Unicode.GetBytes($args[0]))}
$find1 = tochars "</INSTALLATIONTYPE>"; $find2 = tochars "</WIM>"; $cli = tochars $typeC; $srv = tochars $typeS

running one more time, will let you know how it goes tomorrow.
If this is not going to work, I will switch to the other thread, also created by you, with few additional details, and follow up to that one step by step.
It is 10:30PM here, so I would rather do this tomorrow :)

mlivshin said:

running one more time, will let you know how it goes tomorrow.
If this is not going to work, I will switch to the other thread, also created by you, with few additional details, and follow up to that one step by step.
It is 10:30PM here, so I would rather do this tomorrow :)

Click to expand...

It is product key, not server key.
Enter the valid key of Windows 11 pro, home or any other edition installed in your pc.
Or boot from disk prepared by above mentioned methods and install on old os. It puts all your data in windows.old folder.
Here you can skip product key of windows 11.
Believe nothing will be lost.
Both methods are working very well.
Simply copy iso and file Quick_11_iso_esd_wim_TPM_toggle on desktop.
Drag iso and drop on file, once and see the meassge.
Then mount this patched iso on virtual drive. Run setup as administrator.
Input or skip product key.
Input language, keyboard.
It searches for disks.
Select disk /partition you wish to install this patched os onto.
Installtion starts in blue background in % mode.
Reboot the pc, after 100% completion.
Working of this tool is
One click installs patch
Second click removes patch
Third click again installs patch.
This is iso I downloaded from uupdump.net for Windows 11Pro 26063.1.240216-1326.GE_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US

More research on this tool:-
1. Right click on file Quick_11_iso_esd_wim_TPM_toggle to run as administrator. This adds send to option to iso in context menu. Then right click iso>show more options>Send to>Quick_11_iso_esd_wim_TPM_toggle, on this left click once. The result is TPM patch added. Again if we repeat this (upto left click on Quick_11_iso_esd_wim_TPM_toggle) TPM patch is removed. We again have to repeat this to add TPM patch.
The same is true when iso is dragged and dropped on file Quick_11_iso_esd_wim_TPM_toggle. Second drag and drop removes the TPM patch and third time drag and drop adds TPM Patch.
All time the message is displayed.
2. Create partition of size 80 gb on drive. Mount patched iso from step one(any one either Send to OR Drag and Drop method should be followed)
3. Run setup as administrator from mounted iso. After setup reaches search disk stage, select newly created partition. Installation starts. On each restart during installation select this newly created partition in boot menu display as first boot, till installation is completed. All this is done from within current Windows. This will be newly added to boot menu entry. Thus one more OS 24H2. This is good for those who do not want to change old windows in pc.
3. Upgradation is more likely in same version from one build to new build if tried in the running windows by mounting patched iso.
4. Boot Disk is recommended to upgrade from 23H2 to 24H2, from BIOS.
There is no data loss. All files and folders are safe.
5. Messages should be watched while applying patch.

Thanks.

Wouldn't it be a lot easier to change your insider level to Canary and let Windows Update do the work?

markw51 said:

Wouldn't it be a lot easier to change your insider level to Canary and let Windows Update do the work?

Click to expand...

We are doing these for unsupported pc. I have done this on i3 processor. Insider preview os can not be installed on my pc without patching downloaded iso.
Thanks @markw51.

markw51 said:

Wouldn't it be a lot easier to change your insider level to Canary and let Windows Update do the work?

Click to expand...

Ramesh Sharma said:

We are doing these for unsupported pc. I have done this on i3 processor. Insider preview os can not be installed on my pc without patching downloaded iso.

Click to expand...

Install the release build of 23H2, the workarounds for that are easy (use the appraiserres one, or Rufus).

Then switch to your chosen Insider channel with oflineinsiderenroll script.

For Windows Update to successfully upgrade an unsupported device to Canary or Dev 26000 series builds use the Skip_TPM_Check_on_Dynamic_Update.cmd script.

It's been explained to you before, all that's needed is a reg tweak on the upgrade host.
reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup" /v "AllowUpgradesWithUnsupportedTPMOrCPU" /t REG_DWORD /d 1 /f

Thanks @Bree
Thanks @garlin
I have tried all other tricks to bypass hardware requirements to install 24H2 on unsupported pc.
Bypass 11by Ave Yo works correctly.

Summary
My special thanks to VIP Members @garlin, @Bree, @markw51, @mlivshin and guests who are reading this thread.
I studied the tool bypass11 by Ave Yo and found that all suggestions from VIP Members are grouped in this single tool.Any single trick does not remove the error message while installing/upgrading to windows 24H2. It keeps dispaying one or two missing hardware requirements.
As there is no documentation on preparing boot disk using this tool, I spent a few hours and finally got the way to prepare boot disk to install/upgrade to 24H2. Hence posted here the details.
Just rename the install.wim to install26058.wim and paste new install.wim from mounted iso of build 26063.1 in sources folder of bootable disk in NTFS partition.Thus you can have an installation of wanted build of Windows 11v 24H2 on your pc. There is no data loss in my case and should not be in anybody's case.
My only aim is to install 24H2 on unsupported pc, which applies to more than 70% of windows users, as long as possible without reversing back to Windows 10 or just keep purchasing new hardware again and again. I like Windows 7, 8.1,10 very much.
I have been Windows user right from MSDOS 6.22, Windows 3.11, then windows 95, windows 98, windows xp, windows me. Basically I am a windows admirer.
As we know this tool is downloaded from github.I recommend preparing bootable disk, as mentioned above, to upgrade from 23H2 to 24H2, doing so does not show BSOD.
It has been bypassing hardware requirements to install 21H2, then 22H2, 23H2 and now 24H2.
Thanks to all.

After using the tools from Ave Yo to bypass the Requirements and change my Insider level to the Canary channel,
Windows Update finally let me update from 23H2 (22635.3212) to 24H2 (26063.1).

The update installs correctly, but after the first reboot i get faced with this error message:
"BOOTMGR Image is corrupt. The system cannot boot."

So the system basically becomes unbootable, despite using these methods.


Only way to get back into Windows after that is to follow this guide here:


I basically have to break/delete the boot folder and BOOTMGR on purpose,
and then repair it as shown in that video.

Repairing the BOOTMGR does work, and i can get back into Windows 11 again.
However, it automatically reverts back to 23H2 (instead of 24H2).

I have done this twice now, with the same result.

The computer is running MBR and not UEFI if it matters
(system specs are listed under System Two).


Is this some kind of new block Microsoft has added for unsupported hardware?

Only block i am aware of is the PopCnt/SSE4.2 requirement (which my CPU does support).

SuperConker said:

After using the tools from Ave Yo to bypass the Requirements and change my Insider level to the Canary channel,
Windows Update finally let me update from 23H2 (22635.3212) to 24H2 (26063.1).

The update installs correctly, but after the first reboot i get faced with this error message:
"BOOTMGR Image is corrupt. The system cannot boot."

So the system basically becomes unbootable, despite using these methods.


Only way to get back into Windows after that is to follow this guide here:

I basically have to break/delete the boot folder and BOOTMGR on purpose,
and then repair it as shown in that video.

Repairing the BOOTMGR does work, and i can get back into Windows 11 again.
However, it automatically reverts back to 23H2 (instead of 24H2).

I have done this twice now, with the same result.

The computer is running MBR and not UEFI if it matters
(system specs are listed under System Two).


Is this some kind of new block Microsoft has added for unsupported hardware?

Only block i am aware of is the PopCnt/SSE4.2 requirement (which my CPU does support).

Click to expand...

Hello @SuperConker,
Did you use boot disk?
It is prepared in such a manner that it is perfect for both, BIOS and UEFI systems.
Now I am upgrading Windows 11 Pro v23H2 build 22631.3155 to insider preview Windows 11 Pro v24H2 build 260063.1 from desktop by mounting patched iso and running setup. exe as administrator.
I am deliberately upgrading from desktop to see the result.
I will post the result after some time, but soon.
Installation is going on 25%....
pc restarted..... 30%....54%...60%... 73%
pc restarted.. 95%..
showing "just a moment".. with spinning circle....
pc restarted... Asking for country.. India.. US.. skip another keyboard..
Connecting internet.. Next.. Checking for updates...
Name the device... Just a moment....
pc restarted....Boot menu.. Selected new one to complete installation...
Just a moment... Setup for personal use... sign in.. entered Microsoft account and password... Create pin.. Pin created... Next.. Next.. Accept... Setup as a new pc.... Getting things ready for you.... Skip... Skipping phone... Only save files to this pc... Accept.....and finally..