I make so many mistakes, how can i do better? Oh wait, i post the facts... and the facts seem to be very confusing with MSFT these days.
That's not his mistake, but Microsoft's. He was merely stating facts. EnterpriseS and IoTEnterpriseS are on the applicability list of 25H2 EP. We don't know why. And, everyone is fully responsible for one's own doing. Edit: Too late.
I was posting previously that a same situation was happening to Win 10 LTSC 2021 during Win 10 transition from 21H2 to 22H2... Someone could tell me if 22H2 EP contained EnterpriseS, IoTEnterpriseS SKU? Did someone here try to integrate 22H2 EP in Win 10 (IoT) Enterprise LTSC 2021? I did succesfully and it means 22H2 EP has a such SKU. As far as I remember MS then didn't publsh any info about a such kind of integration and I'm sure they will say nothing at all now... This is an elementary logic... After all, MS did always say that LTSC 2021 is always 21H2 and in 2024 they were saying that LTSC 2024 is always 24H2...
It was not present in 2021 LTSC, it was (IS) present in 2024 LTSC applicability list. Yes, several "people" fudded the board with their "install the mum" crap to have 2021 LTSC show 19045. The 22H2 EP was not applicable. It all was discussed before up to some bans.... and now we are back to that nonsense.
Have no idea... I'm not so old yet and don't have the Parkinson's disease so far, I remember exactly that I was succesfully installing 22H2 EP on Win 10 IoT LTSC 2021 and later re-installed OS.
Until Microsoft makes an official statement or the 25H2 enablement patch gets official release, nobody knows for sure.
Maybe I'm wrong. It was my nephew's old gaming laptop, It's gone long ago. As far as I remember it originally came with Windows 10 Pro... Anyway I don't think it's that important. That's just it...MS hasn't yet shouted from the every rooftop that the EP is applicable to LTSC 2024 and should be installed, and I'm sure they won't do that. In any case I stand by my opinion. It was a stupid action to advertise an integration of EP 25H2 into (IoT) LTSC 2024 and now try to help revert it. Many less experienced users just won't be able to do that, especially with non-IoT LTSC on unsupported HW, and will be forced to reinstall their OS'.
Windows 11 23H2 still have WordPad binary for that. If you are using Windows 11 24H2 or later already, WordPad is no longer available in that image. For my method installing back in, we need to find the Windows 11 22H2/23H2 Features on Demand image file, mount the image or extract the files to a folder, then use the command below to install the WordPad back to the image. Note that the x64 and arm64 have different FoD image file make sure you are picking the right one to be installed. dism /online /add-capability /CapabilityName:Microsoft.Windows.WordPad~~~~0.0.1.0 /source: (Path to mounted or extracted folder) /LimitAccess
If EnterpriseS and IoT EnterpriseS are on the applicability list even in the official/public EP it only means you can safely update them to 25H2 (if you want of course)
If someone hadn't advertised here compatibility of 25H2 EP with Win 11 (IoT) LTSC, I'm sure no one in this thread would have thought of integrating this package into the LTSC edition... I also find a lot of stuff or info in internet, sometimes I post something here or somewhere else but before that I try to filter the information, understand what it might lead to.
@Andrew1968 There is no point of beating around the bush. Instead, let's talk about some relevant shenanigans by Microsoft which were eventually discovered by the tinkering communities like us. Case 1: Microsoft never marketed consumer Enterprise SKUs for OEM preinstallation, but you can find valid OEM:SLP ranges in the Windows 7 Enterprise pkeyconfig. As a result, you can actually offline activate it with a valid SLIC-cert combo. Case 2: First introduced with Windows 8, Core(/CoreSingleLanguage/CoreCountrySpecific) and ProMWC SKUs don't officially support KMS activation. With that said, Microsoft did offer official GVLK for those SKUs via product.ini, and albeit you can't activate them against a real KMS server, any little KMS server emulator will happily activate them. Case 3: The ServerRdsh SKU was only meant for Azure, and specialized in-premises deployment, but it is often "exploited" by Windows aficionados for its server-esque features such as multiple RDP sessions. The list just goes on, but the moral of this discussion is there are often easter eggs found in the domain of software development, and Microsoft is certainly not an exception to this trend. But keep in mind that these are different from brute-frankenbuilding without any inner knowledge. Hence, installing the unpacked 19045 EP on Windows 10 (IoT) Enterprise LTSC 2021 just for the sake of a cosmetic change makes no actual sense. However, the 26200 EP does come with support for Windows 11 (IoT) Enterprise LTSC 2024 for now, and only time will tell how Microsoft is planning to take things forward from this point. So it's just better to wait and see, period.
That's exactly what I keep on sayin'... Maybe MS accidentally included LTSC in the 25H2 support list but that doesn't mean that 25H2 EP should be manually integrated in. Moreover, as far as I know, the 25H2 version hasn't been officially announced yet (or just announced - I don't follow this topic very closely), and MS may still make some adjustments.
New pic is not new, we already installed the 25H2 on LTSC months ago and it is not advised to do so, although it can be offically applied but: - LTSC never got any feature updates (upgrades) in the past and most likely won't get any in the future, else they brake most of the LTSC main feature. - The 25H2 Ep does not do anything - 24H2 and 25H2 are said to get the same features. Info: https://forums.mydigitallife.net/posts/1890049
Patch Tuesday is going to be interesting. If 25H2 gets offered in Windows Update to LTSC 2024 users, it's just going to add even more confusion. As for users forcing the 22H2 enablement package on LTSC 2021, be prepared to remove the package in November when you try to update Windows. There's a good chance Windows Update will look for an ESU license because you're using 22H2.