[DISCUSSION] Windows 11 Enterprise/IoT Enterprise (N) LTSC 2024 (24H2 / 26100.x)

Discussion in 'Windows 11' started by Enthousiast, Apr 26, 2024.

Tags:
Page 151 of 187
  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3001 Enthousiast, Aug 29, 2025 (OP)
    https://forums.mydigitallife.net/posts/1888276

    Added DU for SafeOS and DU for Sources!!!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3002 Enthousiast, Aug 29, 2025 (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. maur0

    maur0 MDL Senior Member

    Aug 3, 2012
    479
    252
    10
    #3003 maur0, Aug 29, 2025
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. P40L0

    P40L0 MDL Senior Member

    Jul 14, 2009
    495
    294
    10
    #3004 P40L0, Aug 30, 2025
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3005 Enthousiast, Aug 30, 2025
    Last edited: Aug 30, 2025
    (OP)
    The EP apllicability list mentions EnterpriseS (= 2024 LTSC) but it is not sure it will get updates when applied on it.
    Code:
          <assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerAzureStackHCICorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterNanoEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerTurbineCorEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerTurbineEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-UtilityVMEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-WinPE-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-WinVOSEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-WNCEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    The 22H2 applicability list does not list (IoT)EnterpriseS, so all can happen, although that would break the purpose of running a LTSC version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. P40L0

    P40L0 MDL Senior Member

    Jul 14, 2009
    495
    294
    10
    #3006 P40L0, Aug 30, 2025
    I definitely won't manually mess up with it unless I have 100% confirmation that future Windows Updates will still be offered also for IoT
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3007 Enthousiast, Aug 30, 2025 (OP)
    We can simply wait till the 25H2 goes GA/Retail Channel.

    The list mentions it so it is possible.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. iamaHUN

    iamaHUN MDL Member

    Jun 6, 2018
    122
    190
    10
    #3008 iamaHUN, Aug 30, 2025
    This enablement package is still the dev channel one which is a few months old now. The displayName in the update.mum says "Feature Enablement for Dev Channel Preview Update (KB5054156)" and the version is 26100.5503.1.1, so I think MS will/should release a new enablement package (which may not support LTSC).
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3009 Enthousiast, Aug 30, 2025 (OP)
    The current one has EnterpriseS in the applicability list* and there should be a new one for the retail channel, we will know when it appears.

    * https://forums.mydigitallife.net/posts/1888353
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. maur0

    maur0 MDL Senior Member

    Aug 3, 2012
    479
    252
    10
    #3010 maur0, Aug 30, 2025
    I was also in doubt if there will be future updates in LTSC after 25h2 hehe since LTSC doesn't officially have 25h2
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. ngr.hd

    ngr.hd MDL Novice

    Apr 6, 2014
    46
    11
    0
    #3011 ngr.hd, Aug 30, 2025
    Is 25H2 not going to be the next LTSC for W11?
     
  12. Mooniversal

    Mooniversal MDL Junior Member

    Jul 9, 2020
    89
    52
    0
    #3012 Mooniversal, Aug 30, 2025
    No. 24H2 is the last LTSC release. There won't be an official 25H2 release by Microsoft. Maybe next year they'll release 26H2 LTSC. But not this year.
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3013 Enthousiast, Aug 30, 2025 (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. egyptian hak

    egyptian hak MDL Senior Member

    Aug 21, 2009
    304
    79
    10
    #3014 egyptian hak, Aug 30, 2025
    But can we use 25H2 Enable Package to get LTSC 25H2
     
  15. P40L0

    P40L0 MDL Senior Member

    Jul 14, 2009
    495
    294
    10
    #3015 P40L0, Aug 30, 2025
    I wouldn't do it manually or you may break future Windows Updates for it.

    Wait for official GA. If it will be offered also for LTSC or IoT, otherwise keep it as is.
     
  16. Andrew1968

    Andrew1968 MDL Member

    Nov 3, 2024
    149
    163
    10
    #3016 Andrew1968, Aug 30, 2025
    I'm sure It wouldn't be offered (via WU), genuine (IoT) LTSC should remain 24H2.
     
  17. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    8,076
    10,299
    270
    #3017 Carlos Detweiller, Aug 31, 2025
    Display-only (just a Registry entry), the update itself means Jack for LTSC, as the actual features are blocked via ProductPolicies.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. maur0

    maur0 MDL Senior Member

    Aug 3, 2012
    479
    252
    10
    #3018 maur0, Aug 31, 2025
    The question is, after I install 25h2 in LTSC, will the system update normally on patch days because the tar with 25h2 won't confuse the system when running WinUpdate? Will it work with the common LTSC updates?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. P40L0

    P40L0 MDL Senior Member

    Jul 14, 2009
    495
    294
    10
    #3019 P40L0, Aug 31, 2025
    That's the point: I think it could create issues, at least on IoT Enterprise LTSC
     
  20. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,944
    450
    #3020 Enthousiast, Aug 31, 2025 (OP)
    I have mentioned it a few times already, to know that for sure we'll have to wait till the next LCU is released, i would not install the 25H2 EP on LTSC on my main systems, only to test in a (virtual) test environment.

    And i have said 100s of times before, LTSC should and did never get feature upgrades, that was one of the main purposes of LTSC..

    The confusion now is because the applicability list mentions EnterpriseS, it never did on Windows 10 EP's.

    All 26xx0 updates are in fact 26100 updates, only the small EP makes the difference.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Page 151 of 187