In place upgrade of Windows 11 Pro from v24H2 os build 26100.2033 to v25H2 os build 26200.6584 by an installer on github.

Hello everyone,

With reference to the link https://github.com/tips2fix/Tips2Fi.../1.0.2/Tips2Fix-Windows11-Installer-1.0.2.zip , I just downloaded the zip file from this link and extracted it to folder. I downloaded Windows 11 v 25H2 iso from official website of Microsoft and used the installer to upgrade on my laptop unsupported for Windows 11. The v24H2 os build 26100.2033 of Windows 11 was already bypassed by WIM TOOLS by @hsehestedt. I just used first of three options which the code offers before upgrade. I used first option which is fast upgrade without any registry changes. Thanks @Tips2Fix. The activation status was same as it was for v24h2. (Activated with digital license linked to Microsoft Account) Please note that I have not run Windows Update before executing the installer by Tips2Fix.

Device name DESKTOP-A9ODV2T
Processor Intel(R) Core(TM) i3-5015U CPU @ 2.10GHz (2.10 GHz)
Installed RAM 6.00 GB
Device ID 39A62263-7A28-40E4-8ACD-953938DDD8F1
Product ID 00330-81487-43919-AA794
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro
Version 25H2
Installed on ‎10/‎10/‎2025
OS build 26200.6584
Experience Windows Feature Experience Pack 1000.26100.234.0

I have attached the image showing winver herewith , please see.
(The desktop background wallpaper is manually downloaded, was not with upgradation.)
Thanks for reading and sharing your valuable time.

This takes 3 seconds and a reboot...

26100.2033 is 24H2 GA (October 2024). It's unpatched. Nobody should be running this 24H2 version by now, unless you disabled WU and skipped every single Monthly Update.

To convert 24H2 to 25H2 is a straightforward process. You allow WU to install September 2025 (or later), and add the Enablement Package.

You wouldn't need to perform an in-place upgrade unless 24H2 was older than September. While this may have been a learning exercise, it's unrealistic to assume an user would need to create a 25H2 ISO when they're already on 24H2. The upgrade process works without an ISO.

Thanks @garlin. Is upgradation from v24H2 to v25H2 on unsuppored hardware is a matter of Windows Update only? in place upgradation may not be necessary for v24H2 as you suggested but what about checking of hardware during upgrade if ISO is to be used? Will the upgrade continue on my laptop without installer from github, I used, if I want to use iso of v25H2 to upgrade from v24H2 already bypassed by WIMTOOLS?

If you have already installed 24H2 on unsupported HW, WU will continue to install Monthly Updates. It doesn't bother to check for support when it installs the Monthly security updates. Unsupported PC's won't be offered the Enablement Package (because it's a Feature Update).

But you can script downloading the MSU, and installing it.

The same thing that happened for 22H2 -> 23H2. Unsupported PC's got the Monthly Updates, but no offer for the 23H2 EP.

The EP is a trivially small package since it's only setting internal variables to unlock new features already hidden inside 24H2's later Monthly Updates. That's why installation takes a few seconds, and then you restart Windows for new changes to take effect,

Thank you very much @garlin for above script. This script is an automation batch file intended to upgrade a Windows 11 system from version 24H2 to 25H2 using the enablement package KB5054156, but only if conditions are suitable for a smooth update.The script checks the installed Windows 11 build number and cumulative update state, determines if the system is eligible for the 25H2 enablement package, and automates the download and installation of the relevant update.
Just adding pause in above script before exit /b 0 in both places and in the last in cmd file...
I am attaching the result of above script after having saved as upgrade-w11-25h2.cmd and upgrade-w11-25h2.ps1(converted to powershell script with the help of Perplexity AI)

After running cmd as administrator

Exiting. Windows is already W11 25H2.
Press any key to continue . . .

When Run with Powershell

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Installing PowerShell on Windows - PowerShell

PS C:\WINDOWS\system32> powershell.exe -ExecutionPolicy Bypass -File "C:\Users\RAMESH SHARMA\Desktop\upgrade-w11-25h2.ps1"
Exiting. Windows is already W11 25H2.
PS C:\WINDOWS\system32>

Thanks again @garlin and everyone.

Update
Hello everyone,
Are Windows 11 v24H2 os builds 26100.1882 and 26100.2033 of same level upgrades?
Using above tool , without running windows updates automatically or manually,without applying enablement package, I could in place upgrade from Windows 11 v24H2 26100.1882 to Windows 11 v25H2 os build 26200.6584
Images attached herewith ,
Thanks.

26200 is simply an updated 26100 build (later than .5074) with the 25H2 EP installed. Removing EP from 26200 reverts it back to a 26100 build of the same update version.

26100.1882 and 26100.2033 are both lower update versions than 26100.6584/26200.6584.

To upgrade them, you have two options:
1. Apply the August 2025 Preview (or later) 24H2 update to them first. Then apply the 25H2 EP to convert 24H2->25H2.
2. Directly run an in-place upgrade using a 26200.6584 install image.

If you're writing an upgrade script, the best method is to query the UBR number.

When UBR >= 5074, then apply the EP. The user can run WU to upgrade 25H2 to a current CU if they like.

Otherwise if UBR is too low (.1882 and .2033) then an in-place upgrade to 26200.6584 is faster since the install image has everything in one pass.