Trouble finding W10 21H2 ISO

Hellbovine said:
Version 22H2 can be used with my guides, and most of the tweaks will still work. The main reason I chose 21H2 is because 22H2 had too many bugs, and after 6 months there's still plenty of issues remaining for Microsoft to fix. 21H2 on the other hand is stable, had no major known issues, and is also what LTSC 2021 uses, so it was a good version to use as a base.

Version 21H2 reaching end of life doesn't really matter until popular 3rd party software starts dropping support for it, but that will be years from now and by then the guides will likely use a newer build anyway. There are other reasons for not using 22H2, but those are more complex:
Besides all the officially known issues, when I tested 22H2 I discovered an undocumented task scheduler bug (link1) that renders the 22H2 build currently hosted on Microsoft's website too broken to be usable, if you do not install the updates that were released later. The main problem is that many of us hardcore tweaking enthusiasts pause/disable/uninstall Windows Update, because it can install ads, bloat, resets tweaks to defaults, restores uninstalled components, and adds new bugs as we've seen with 22H2.

Microsoft does not refresh their website with updated ISO builds, except for once per year, so we are forced to wait until 23H2 releases to download that (if it isn't buggy) and stick with an older version like 21H2 in the meantime. Even then, Microsoft recently announced that 23H2 will not be available for Windows 10, so all we can do is hope they still release an updated build at the end of this year, at the same version.

I don't know how I want to address all of this yet, because I had already settled on just waiting for 23H2 to update the guides, but now that's uncertain. There's a lot of options available to address this 22H2 task scheduler bug, but I haven't worked through them and evaluated which approach is best, within the premise of an easy-to-use guide. I'm open to suggestions on how to address this in the guide, but it has to be clean, simple, and easy for inexperienced users to follow.

To summarize, Microsoft is really screwing up this year:
- 22H2 on both Windows 10 and Windows 11 was too buggy to release and still has issues
- Microsoft is blocking people from downloading older Windows 10/11 versions right now
- Windows 10 will not get a 23H2 update (link2) which means newer builds may not be posted
- The new SecureBoot exploit (link3) will take months to address and will affect the future
- Older Windows (W7) are no longer an option, because they can't run popular software now
- Windows 11 in my testing had lower performance in some areas, and higher DPC latency
- Windows 11 is actively evolving which makes it buggier/unstable, and more work to tweak
Click to expand...
Greetings Hellbovine garlin
At this time - do you still suggest using 21H2 over 22H2 for Windows 10?
 
20H2 thru 22H2 are considered the same family of Windows releases. They all get the same kernel updates, the only major differences are changes in the UI interface and later versions of included apps. There's no real performance differences, or later optimizations.

LTSC versions are currently in vogue in the gaming world, mostly because they're boring and predictable in terms of changes. But as a matter of principle, you have to pick a stable version to base LTSC/LTSB from. LTSC 2021 is forked off 21H2.

Most W10 releases have reached, or are close to EOL (End of Life), so there's nothing further to expect other than security fixes.

Considering this family is very similar, and basically EOL'ed; there's not much difference picking one over another except for user features. LTSC 2021 will last the longest, based on availability of future updates (but those will be security-only).
 
sbz said:
At this time - do you still suggest using 21H2 over 22H2 for Windows 10?
Click to expand...
This thread was caused by the buggy launch of 22H2, so I advocated for 21H2 until it was fixed. Since these bugs weren't the result of new bloatware, I wasn't concerned about 22H2 being awful forever, it was just a matter of waiting for Microsoft to resolve the issues, which took more than 6 months.

I've tested the newer W10 22H2_V1 ISO and I think it's more refined than 21H2. It's okay to use 21H2 or the latest 22H2 ISO release with my guides, as I've noticed only a handful of tweaks need updating, and nothing major is harmed while the guides wait to be revised.
 
Last edited:
Thank you both for your prompt and comprehensive answers. As well as everything else you've contributed. I appreciate it ! And Happy 4th if you're American!
 
FWIW -- @ today's date, the 21H2 download still works as per the instructions in the opening post.

That said, I decided to go for 22H2 latest in the end.
 
punjig said:
Not trying to downplay MCTWrapper or any other method, just trying to put more info out there. Also, if anyone knows why this info might be incorrect, Please let me know as I am in the middle of this ntLite upgrade from a Win 7 System.

I a NTLite Newbie (NOT a tech Newbie). I know I'm late to the party but I found a 21H2 download from Internet Archive / Way-back Machine and the Hash checks out to be a Legit MS Download. I used the following information that I will copy/paste below. I followed the original posters source plus dug a little myself to verify MS Hash. Like I said, the Hash checks out but do your own research into this. It is a SLOW download, took about 20min. (But I'm from the dial-up days, so I don't mind the wait).


Scource of Origainal Post (not trying to break rules if link is not allowed, just trying to give all info for reader to research yourself):
https://superuser.com/questions/1790347/rufus-and-previous-windows-10-versions

Rufus doesn't have their own hosting for those ISO downloads, they always pull it from the official releases download links. Since Microsoft recently decided to remove their official download links for past versions of Windows, Rufus also doesn't have them anymore.
The best way to download now an ISO for Windows 10 21H2 would be to find somewhere online that has the ISO to download (there are links for it all over) and once downloaded verify the file hash that it's indeed the untouched ISO of Windows 10 21H2.
Good Luck Everyone.

Mod Note: Sharing links to non-official ISO sources is against forum rules.
Click to expand...
English users. THIS is hands-down the easiest approach for "Windows 10 21H2 x64"! Just use Internet Download Manager (what I use) or something of the likes to expedite the download from The Internet Archive.

That being said...@abbodi86 is a legend! I love the tools he's released over the many years. A true hero!
 
Jim said:
English users. THIS is hands-down the easiest approach for "Windows 10 21H2 x64"! Just use Internet Download Manager (what I use) or something of the likes to expedite the download from The Internet Archive.

That being said...@abbodi86 is a legend! I love the tools he's released over the many years. A true hero!
Click to expand...
Another script that's available (based on abbodi's work) is:
PowerShell GUI for Downloading Windows 10/11 ESD images - W10_11aria2ESD.ps1

This script downloads an official ISO (using aria2c for faster downloads), and run's abbodi's ESD decrypter to output a finished ISO. Typically the first and last ISO builds of every Windows release is provided, going back to W10 19041.
 
  • Like
Reactions: Jim
garlin said:
Another script that's available (based on abbodi's work) is:
PowerShell GUI for Downloading Windows 10/11 ESD images - W10_11aria2ESD.ps1

This script downloads an official ISO (using aria2c for faster downloads), and run's abbodi's ESD decrypter to output a finished ISO. Typically the first and last ISO builds of every Windows release is provided, going back to W10 19041.
Click to expand...
For clarification. Does the PowerShell script accomplish the same as the Win(bat)/Mac/Linux scripts on uupdump?

Edit: i mainly ask because I’m currently downloading the latest Win10 21H2 Pro with all 4 “conversion options” selected.
 
No, but UUP dump serves a different purpose. It's more so you can "shop around" for specific builds. Some users have a very specific requirement that they're not allowed to use non-official ISO sources. This definitely excludes UUP dump.

MCT and UUP dump both suffer from the same problem, due to the way they re-assemble an ISO from individual UUP files, they will never match a known hash value from a published MS ISO. It's like 99.98% close, but not an exact match.

UUP dump also has some basic image customization features in the build script. Mostly for users who don't use a modding toolkit or app like NTLite to prepare their images. Different tools for different requirements.
 
  • Like
Reactions: Jim
garlin said:
No, but UUP dump serves a different purpose. It's more so you can "shop around" for specific builds. Some users have a very specific requirement that they're not allowed to use non-official ISO sources. This definitely excludes UUP dump.

MCT and UUP dump both suffer from the same problem, due to the way they re-assemble an ISO from individual UUP files, they will never match a known hash value from a published MS ISO. It's like 99.98% close, but not an exact match.

UUP dump also has some basic image customization features in the build script. Mostly for users who don't use a modding toolkit or app like NTLite to prepare their images. Different tools for different requirements.
Click to expand...
That explanation was superb! I’ve always tried to do my research and acquire the latest official ISO build of the version I seek. Then apply my updates through NTLite. That being said, it seems as if I should utilize the PS script you compiled to acquire my build. Goes hand in hand with my usual goal and progress. Albeit, if I understand correctly, uupdump would essentially be a completely up-to-date ISO out of the gate? Just wouldn’t match any checksums to official ISO releases. Which I would imagine the official ISO releases are not 100% up to date? (They would require slipstreaming some or all of the updates that uupdump applies?)
 
The myth of UUP dump constantly grows without users understanding what features are incredible, and which parts are really mundane.

UUP dump's devs have reverse-engineered a way to assemble a complete ISO from UUP files, or update files normally provided by WU. The dumbed-down explanation is they pretend to be a Windows machine and submit an update request to MS, and wait for a list of changes to be provided. Using tons of proprietary parsing, they collect a list of UUP files to build a baseline image, typically a .1 build image.

The rest is less exciting. To reach a specific build number within that Windows branch, they determine the KB update that brings you up to that kernel level. UUP dump downloads the right set of KB updates, that when applied results in that version.

When you ask for 26100.3323 versus 26100.2605, both scripts start by building a baseline 26100.1 and either apply KB5052093 (.3323) or KB5048667 (.2605) on top.

One shortcut is to keep a previously created baseline image, and just download the required KB files by clicking on UUP dump's list of included KB updates (without going through the whole build process). Apply the new list of KB's to your master .1 copy. Repeat every time a new build is released.

UUP dump can now "debloat" Apps and Edge by skipping those individual packages. When the ISO is assembled, those features were never there to begin with. For a non-technical user, it's practically magic since the website is easy to navigate.
 
Wow! That explanation leaves me damn near speechless! Amazing!! I can’t thank you enough for that concise post. This is a petty question to ask in response to your perfect reply. I did notice that omitting edge was an option. If I were to toggle that in the ini file, does that also prevent “legacy” edge from being installed as well? It’s been documented that it’s removal breaks compatibility with something(s).
 
Edge (Chromium) and Edge (legacy) are two entirely different products. For the most part, you need to keep Edge (legacy) because that's where the IE11 compatibility engine resides.

Edge (Chromium) can be skipped using the .ini file, it's provided as hidden Edge.wim inside the CU.
Edge (legacy) is buried in the ISO as one of the assembled components.

The baffling problem is the ZIP file for some reason doesn't include the ReadMe.html. It's only downloaded after you start the script.

  • SkipEdge

    Skip adding Microsoft Edge Chromium
    Set option to 1 : Do not add Edge.wim for Windows 11 build 26052 and later
    Set option to 1 : Do not integrate Edge with Cumulative Update for Windows 10
    Set option to 2 : Skip Edge with Cumulative Update for Windows 10 via alternative workaround (may not work)

    This option works only with option AddUpdates=1 (Integrate).
Click to expand...
 
  • Like
Reactions: Jim
garlin said:
Edge (Chromium) and Edge (legacy) are two entirely different products. For the most part, you need to keep Edge (legacy) because that's where the IE11 compatibility engine resides.

Edge (Chromium) can be skipped using the .ini file, it's provided as hidden Edge.wim inside the CU.
Edge (legacy) is buried in the ISO as one of the assembled components.

The baffling problem is UUP's ZIP file for some reason doesn't include the ReadMe.html. It's only downloaded after you start the script.
Click to expand...
Excellent! I will read the entire readme. Your prompt replies and helpful insight has expedited my strides on this endeavor. Others will surely find your replies useful. Thank you so much.

(I know my profile says new user but I am not. I was active with the community prior to nuhi switching to a “forum”. Roughly a decade ago. The community is thriving. Makes me happy to know users like yourself are in it for the long haul. Thanks again dude. I greatly appreciate your shared knowledge)
 
garlin said:
I'll save you the work of Steps 1. thru 3B.
Code: 
C:\Users\GARLIN\Downloads\MediaTools>MCTWrapper.bat
Please specify a MCT version:
W11_24H2
W11_23H2
W11_22H2
W11_21H2
W10_22H2
W10_21H2
W10_21H1
W10_20H2
W10_2004
W10_1909
W10_1903
W10_1809
W10_1803
Code: 
MCTWrapper.bat W10_21H2
MCTWrapper.bat W10_21H2 /Retail /MediaLangCode en-US /MediaArch x64 /MediaEdition Enterprise

This script downloads the right MediaCreationTool.exe (if the file isn't found), and runs self-hosted. You can pass along MCT command line options to skip any language, architecture and edition prompts. Multiple copies of MCT can exist side by side, because the script knows where to find the correct products.cab.

If you're asked for a product key, use one of the generic KMS client keys. Key Management Services (KMS) client activation and product keys
From the above example, Enterprise edition requires NPPR9-FWDCX-D2C8J-H872K-2YT43.

Create a local ISO file (since you're going to use NTLite to edit the image). Continue to Step 3G.

UPDATE 2023-07-21: MS removed 1803's MCT, switched to the Internet Archive's copy
UPDATE 2023-11-16: Added 23H2
UPDATE 2023-12-21: Updated 23H2 (22631.2861)
UPDATE 2024-10-02: Updated 24H2 (26100.1742)
UPDATE 2025-06-25: Updated 24H2 (26100.4349)
Click to expand...
How to use that codes? assuming I start from scratch, I haven't downloaded anything or created folders, nothing, then, how do I use what you mention?
How do I choose which MCT to download in CMD?
And even more importantly, once I've chosen the MCT I want through CMD, how do I use it to choose to download any Windows 10 or Windows 11 version?
Sorry, but I have no experience in this and I need some guidance.
 
You can choose the Windows edition, by specifying it on the command line:
Code: 
MCTWrapper.bat W10_22H2

MCTWrapper.bat W11_21H2

MCTWrapper.bat W11_24H2

If you provide any additional command-line options, they're passed on to MCT as if you typed "MediaCreationTool.exe /.." MCT has some undocumented line options for specifying the Retail vs Business ISO, your base language, machine architecture, or specific edition.

Those are entirely optional. If they're not provided, then MediaCreationTool runs as it normally does. The script's role is to download the right MCT file so you end up with the desired Windows release.
 
You must log in or register to reply here.
Back
Top