How many times do i need to tell people i don't care what you do, stop addressing me with this nonsense. Me, and some people who really know, can't advise to install it on LTSC. Just love MSFT for this freeking nonsense. And it are the same people cluttering MDL with the update,mum crap with 2021 LTSC.
You are a real special one, aren't you? Enjoy your 2 in 26200... stop inlcuding me with this nonsense.
Well, for now I will enjoy the 2...but in the future I will probably also enjoy when some apps and/or games will start requiring some 25H2 exclusive feature they will add/unlock later and I will be fully compatible without clean installing or full upgrading to another Win11 edition only for those. Anyway, I just replied to the user stating there were issues with latest CU (and to your reaction to it): there were none actually, at least by just installing it via Windows Update and not manually from the catalog. Actually any CU after manually installing public 25H2 EP installed fine with no errors, no dism/sfc corruptions etc, so you may still call it "Frankenstein builds" or whatever, but the reality is that it worked and it's officially supported at the same time and those are just facts. Also everyone is free to try whatever they want as long as they know what they're doing (and are also prepared to restore from backups), so I don't get the rage against it. Relax.
And you think that features will activate according to the 2? No, they follow Product Policies, and will most probably not work on LTSC 2024, no matter the number.
I specifically said that technically it was NOT a frankenbuild because the morons at MSFT included the LTSC apllicability, don't twist my words. You quoted me, not only the user to whom you replied to. As said, feel free to do whatever you want, like when some here were cluttering and trolling with the update.mum crap whit 2021 LTSC. LTSC is made to never receive feature updates, besides that 24H2 and 25H2 are announced to get the same features. With 2021 LTSC now people are reporting they get an end of service message, who knows what they were doing, like the 19041 reconstruction or maybe using the update.mum stuff to get their 19045 showing in 2021 LTSC. Another mistake by MSFT: https://forums.mydigitallife.net/posts/1893411
I'm pretty sure sure they will, as even on LTSC 2024 I already got Dolby Vision support and the same features not strictly related to LTSC but that General 24H2 received over time. Same thing will be for 25H2. I think for MS LTSC just means "real" feature upgrades won't be offered (so no full in-place upgrades to newer major builds) but 25H2 was not that, so they probably just allowed it for whom installed it manually and that's it.
Exactly, and currently it does not offer it through Windows Update. I don't get why so many people want to push an enablement package onto LTSC that does absolutely nothing. If you really want to use 25H2 so bad, just use a non-LTSC version of Windows 11.
I completely agree. If you apply an enablement package to an LTSC, it is no longer an LTSC in a sense. What's the point of changing the cosmetic edition name?
What I'm wondering is why LTSC was chosen. If NPD481 is required, LTSC is not an option to begin with.
I understand that choosing LTSC is important because it prioritizes stability. However, if you switch to 25H2, wouldn't that be the exact opposite of the reason you chose LTSC? Am I understanding this incorrectly? I'm not very good at English, so I'm worried if I'm getting my point across properly.
with the 25H2 EP you are getting the latest NDP481 and a higher build number you are not getting big new 25H2 features thanks to Product Policies, so it's still LTSC 24H2 in terms of features you may need higher build number if some weird software is hardcoded to check build 26200 only once again: it will stay LTSC even with 25H2 EP installed, as of now it's officially allowed and no issues have been found
The idiots from Microsoft don't update article MSKB 894199 on the support.microsoft.com. Last update - July 2025. WTF??? ======