It may install the EP, but the EP certainly explicitly excludes the LTSC license from applicability. That gets it stuck in a loop.
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">
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?
Most likely to happen when setup.exe from "ISO:\Sources\boot.wim\2\sources" doesn't match the one in "ISO:\Sources".
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
Well, there we have Windows 19045.2006 IoT Enterprise The troll who laughs last, laughs best. LOL!!!!
Actually he was right, there is no and will be no 19045 (IoT) Enterprise 2021 LTSC ever. As shown here in the GiF, the 22H2 EP is offered but is not meant for LTSC so it does not work: https://forums.mydigitallife.net/th...prise-n-ltsc-2021.84509/page-135#post-1760482
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?
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.
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.
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
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