Windows 11 Enterprise/IoT Enterprise (N) LTSC 2024 (24H2 / 26100.x) vs Microsoft Windows 11 IoT Enterprise [10.0.26300.9457], Version 26H2. the only main difference they have is in terms of long term updates support. the LTSC supports till October 2034; 26H2 through October 9, 2029. they share the same number of Microsoft apps, both have removable-package capabilities. LTSC doesn't get feature updates and IOT one gets feature updates? what are the main differences in both other than what i already mentioned of course.
Incorrect, the LTSC one doesn't have the apps. IoT Enterprise Non ltsc is just normal Enterprise with the difference that the IoT Enterprise doesn't enforce the windows 11 system requirements like secureboot and tpm2.0.
Thanks for all your efforts but I'm having a tough time keeping up. I must of missed something fundamentally as my understanding of running Windows-11-enterprise-iot-enterprise-ltsc-2024-24h2 was that it wouldn't require any updates (other than security patches), at least until the next iteration of it => sometime in 2027. I'm trying to understand the benefit to installing updates, rather than just doing so and hoping for the best. I've been running Windows-11-enterprise-iot-enterprise-ltsc-2024-24h2 on my Main Box since March and it's been rock solid. (I also put it on a couple of laptops where it performs great.) There are a few things I had to install as it's pretty lean as my daily Operating System. Now I see folks installing Windows Update KB5121794 - to go to 26H2 Build; but I don't understand what that would bring to the user experience. Can you point me to an explanation? Similarly, should I assume these Hotfixes are application related to specific software packages, or do you recommend all users of Windows-11-enterprise-iot-enterprise-ltsc-2024-24h2 install them. Just trying to understand the impact before making any changes. I'm learning every day. Thanks for the assist.
Incorrect, Enterprise has less bloatware compared to Pro verison, and the fact you can use policy to enforce and debloat ent alot better than pro, make ENT much better candidate than pro edition. Debloated Ent edition comes neck to neck with 24h2 in terms of bloatware and performance.
Enterprise is a virtual edition based on Pro, what less, for f**k sake i have to really use the term "bloatware", are we talking about, the stuff that should disappear when we do the license switch. Where do i say that Pro is better? Read again...
i was comparing LTSC with non LTSC, and i remember saying they come neck to neck in terms of bloatware, that's what i meant, and for f**k sake the LTSC is also a virtual edition not a separate branch, its just enterprise with less bloatware
What do you mean, the Apps? I do not like them, either, but the term bloatware is now used inflationary. LTSC IS a different branch and not a virtual Edition. You cannot make LTSC out of non-LTSC (and vice versa) by entering a different product key. More so, if LTSC was a virtual Edition, every branch would have it. The only virtual Edition thing with LTSC is that Ent LTSC and IoT Ent LTSC can be switched between by a product key. But it always stays LTSC.
Gents, as I mentioned above "my understanding of running Windows-11-enterprise-iot-enterprise-ltsc-2024-24h2 was that it wouldn't require any updates (other than security patches), at least until the next iteration of it => sometime in 2027." Can someone explain what these numerous patches are adding in simple terms that a typical user can understand? Also, as in the YouTube posted above, they install an update to get Windows-11-enterprise-iot-enterprise-ltsc-2024 to 26H2 but don't do a good job explaining why, or what it does in any detail other than saying it makes it "up to date". Is that so other programs can utilize the changes in base code, or just for improved system security => or both? Please advise.
That is wright you can convert from IOT LTSC or LTSC Edition to any other Edition without installing windows But you can't convert from any other Edition to LTSC or IOT LTSC except new installation
When a very specific edition is discussed then use the very specific full name, including or leaving out the LTSC part makes all the difference, specially when there are 2 very similar editions. And still the term debloat is being incorrectly used, and for LTSC there is no need for any crappyfying tools. We already discussed the use of the 26H2 EP in LTSC editions, the edition that never will get real or fake feature upgrades (MSFT likes to call it updates). LTSC is not really acknowledged by MSFT when it comes to non business users because officially nobody outside the (iirc) OEM customers are eligable for the license.
They will never acknowledge officially. Yet they know of people like me who see it as a last resort to escape the WaaS mayhem. It should be a legitimate option for every customer to decide if they want flowing or fixed releases. Surprise, the penguins have it already.