1. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,734
    7,646
    210
    It may install the EP, but the EP certainly explicitly excludes the LTSC license from applicability. That gets it stuck in a loop.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,918
    150
    The other way around, is not IoT/LTSC explicitly excluded, it's everything else explicitly included

    Code:
     <package identifier="KB5015684" applicabilityEvaluation="deep" releaseType="Update" restart="required">
        <mum2:customInformation Version="10.0.19041.1799" xmlns:mum2="urn:schemas-microsoft-com:asm.v3" PackageFormat="PSFX" />
        <parent buildCompare="EQ" integrate="separate" disposition="detect">
          <assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-PPIProEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ServerAzureCorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ServerDatacenterACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ServerDatacenterNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ServerStandardACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ServerStandardNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-UtilityVMEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-WinPE-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
        </parent>
        <installerAssembly name="Microsoft-Windows-ServicingStack" version="10.0.19041.153" language="neutral" processorArchitecture="amd64" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" />
        <update name="5015684-4_neutral_PACKAGE">
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
  4. liam2

    liam2 MDL Junior Member

    Jun 23, 2009
    96
    22
    0
    Hi, does anyone have this problem too?

    I can install original LTSC 2021 ISO with no problems on 3 computers.
    But after applying any new dynamic update for sources to the ISO, installation fails with:
    "a media driver your computer needs is missing"
    The same happens on a VirtualBox machine.

    Then I tested LTSC 2019 ISO and last dynamic update I applyed (2020-07) works fine, but with the newest ones, installation fails with the same message.

    Does anyone know why this happens?
     
  5. javaspain

    javaspain MDL Member

    Jul 29, 2009
    216
    114
    10
    Windows 19045.2006 IoT Enterprise!!!

     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
    Most likely to happen when setup.exe from "ISO:\Sources\boot.wim\2\sources" doesn't match the one in "ISO:\Sources".
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
    Not LTSC.

    Code:
    Name: en-us_windows_10_iot_enterprise_version_22h2_x64_dvd_51cc370f.iso
    Size: 5595213824 bytes (5336 MiB)
    CRC32: 9141BDA0
    CRC64: 56D082CD2CD1EC5E
    SHA256: 2070c6eb71143a1207805f264d756b25f985769452f0bafccadf393c85d47f30
    SHA1: 42e763d3a883e97616a134eb0847d9fca240aad9
    BLAKE2sp: 7049d375287ddad42873eb5528022a578c0ec597f19c8f078f106c477e9218c4
    
    SKUs:
    Code:
    [01] 08/09/2022 en-US x64 10.0.19041.2006 Windows 10 Enterprise | Enterprise
    [02] 08/09/2022 en-US x64 10.0.19041.2006 Windows 10 IoT Enterprise | IoTEnterprise
    
     
  8. javaspain

    javaspain MDL Member

    Jul 29, 2009
    216
    114
    10
    Well, there we have Windows 19045.2006 IoT Enterprise

    The troll who laughs last, laughs best. LOL!!!!

     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
  10. liam2

    liam2 MDL Junior Member

    Jun 23, 2009
    96
    22
    0
    Thanks a lot, I put the original setup.exe in "ISO:\Sources", and it worked.
    But what do I have to do to put the new setup.exe in "ISO:\Sources\boot.wim\2\sources"?
    Integrate the last cumulative update?
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
    Best to use W10UI for ISO updating and creation, you can use wimlib-imagex to insert the setup.exe but you also could open boot.wim\sources\ in 7zip and drag setup.exe from there and put it in ISO;\sources, should also work.
    Example;
    Code:
    Bin\wimlib-imagex update "boot.wim" 2 --command="add 'setup.exe' '\Windows\sources\setup.exe'"
    With setup.exe and boot.wim in the same folder and cmd as admin is opened.
     
  12. BubuXP

    BubuXP MDL Member

    Jul 21, 2009
    179
    86
    10
    From the screenshot looks like the opposite, LTSC has sandbox active (1) while IoT no (0)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,918
    150
    Glad to see someone that looks carefully to my messages, you are obviously right, it's a typo.

    Whatever my point was not to produce a detailed and exhaustive list, but just to show that there are some meaningful differences, even if the packages installed are the same.

    Then each user can check them himself in matter of 30 seconds.
     
  14. CocoMaricelli

    CocoMaricelli MDL Novice

    Dec 19, 2021
    1
    0
    0
    Hi,

    I can not download an other version than the en-us verion.

    Site says

    "HTTPError: Forbidden\n at responseErrorThrower (worker.js:195:32)\n at async onGet (worker.js:2772:23)\n at async handleRequest (worker.js:3038:46)"

    Actually I could download the en-us version right before.

    Any help for this please?

    Thank you so much

    Regards
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,593
    103,044
    450
  16. Mincemeat

    Mincemeat MDL Novice

    Apr 2, 2019
    8
    4
    0
    #2720 Mincemeat, Oct 25, 2022
    Last edited: Oct 25, 2022
    2022-10 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5018410)

    Installed this on 19.10, same KB number is now showing up to download it for a few days with automatic checks daily for updates between?

    edit: well it downloaded and installed it with no restart so maybe just cheked and in history its still only 19.10 installation