There were a lot of morons keeping installing the mum files only to get the 19045 shown and some even claimed some appx files worked only when the 22H2 was shown in Enterprise 2021 LTSC, now waiting for those who installed the 25H2 EP on 2024 LTSC to get busted
Updated the OP of the ESU thread with the latest info: https://forums.mydigitallife.net/th...options-activation-and-troubleshooting.89665/
Yes , But I updated 21H2 LTSC using WU normal way worked for me. Only the download of the new update file was very slow. Net.framework as usual.
I've got November 2025 update working fine on IoT LTSC version bumped to 22H2 with *.mum patching. I've installed CU manually by downloading it from MS Catalog. I've not tested same thing for Windows 11 LTSC to bump it to 25H2.
I have a valid license for Windows 11 Home, but is it worthwhile IOT LTSC, I guess updates until 2032, are not the same as a normal retail product, as latest Win 10 22H2 which has ended October 2024, there are two versions LTSC version IOT and Enterprise, is there any difference between them when installing them stock, like stock features?
Code: - Windows 10 non LTSC can still get 3 years of updates on WU when using the MAS/TSForge Business ESU - IoT Enterorise 2021 LTSC is supported till 2032 but for manual updates integration you need the Bypass X ESU suppressor (or simply use W10UI) - Enterprise 2021 LTSC is supported till 2027 and the updates need the same handling as with IoT Enterprise 2021 LTSC - For 2021 LTSC WU will still offer and install all updates without any ESY suppressor needed Added this info to the Windows 10 1904x Updates Overview!
Why on earth would you want to do that? It is not supported and will only show a 5 were a 4 should be shown, nothing more.
It's just of aesthetics reasons, nothing major. Maybe some apps in future will check for exact Windows build number, I'm not sure (besides that 22H2 is based on same 1904x core built at the end of 2019) but it shouldn't do that. I know that people here said that it's useless and I understand. Download 22H2 Enablement Package and extract it with expand command in Command Prompt. Here is a code to apply package with CMD (save this code in *.cmd extension). Code: @echo off Dism /Online /Add-Package /PackagePath:"microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum" Dism /Online /Add-Package /PackagePath:"microsoft-windows-22h2enablement-payload-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum" pause If you don't want to waste your time, here is an extracted package with CMD file in attachment (it's 64-bit version, I can make for 32-bit aswell and edit this post). Run batch as an Administrator.
Can someone do me a favor and check if Group Policy Editor (gpedit.msc) is working with the latest update. I tried running it on two systems and I am getting an endless loop of errors.