Test 25398.1 IoTEnterpriseS Key Types [OEM] Code: ------------------------------------------------------------ Set IoTEnterpriseS key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : IoTEnterpriseS (OEM:NONSLP) ============================================================ [Volume] Code: ------------------------------------------------------------ Set IoTEnterpriseS key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : IoTEnterpriseS (Volume:GVLK) ============================================================
If you, alike me having customized files, cannot use zwl29107's 25398.531 CU KB5032202.esd which supports 18 languages. Q: How to easily use zwl29107's 25398.531 language packs? A: 5-1. Extract official CU Windows11.0-KB5032202-x64.esd to Windows11.0-KB5032202-x64-18. 5-2. Extract zwl29107's KB5032202.esd to KB5032202. 5-3. Copy KB5032202\update.cat and update.mum to Windows11.0-KB5032202-x64-18 and overwrite. 5-4. Select all of KB5032202 and copy\paste to Windows11.0-KB5032202-x64-18. When it prompts "Do you want to overwrite existent files?", press "Skip". 5-5. Compress Windows11.0-KB5032202-x64-18 to Windows11.0-KB5032202-x64-18.esd. [Credits] zwl29107
Test Construct 19044.3758 Windows 10 IoT Enterprise LTSC arm64 el-GR Code: ------------------------------------------------------------ Add Servicing Stack update to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3745~31bf3856ad364e35~arm64~~19041.3745.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ Add 21H2Enablement to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB5003791~31bf3856ad364e35~arm64~~19041.1237.1.3 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ Add Cumulative update to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~19041.3758.1.23 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ Code: ======================================================================================================== 19044.3758 Windows 10 IoT Enterprise LTSC arm64 el-GR has been successfully constructed on 2023/12/3 ======================================================================================================== Mission took 0:27:22.03 (1642.03s total) Code: WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3692291700</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>30460</DIRCOUNT> <FILECOUNT>95751</FILECOUNT> <TOTALBYTES>14043193604</TOTALBYTES> <HARDLINKBYTES>6191336358</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01DA2541</HIGHPART> <LOWPART>0xDDBC21A3</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01DA2541</HIGHPART> <LOWPART>0xF64F1C5A</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>IoTEnterpriseS</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.19041.3636;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>el-GR</LANGUAGE> <FALLBACK LANGUAGE="el-GR">en-US</FALLBACK> <DEFAULT>el-GR</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19044</BUILD> <SPBUILD>3758</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>vb_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 IoT Enterprise LTSC 2021</NAME> <DESCRIPTION>Windows 10 IoT Enterprise LTSC 2021</DESCRIPTION> <FLAGS>IoTEnterpriseS</FLAGS> <DISPLAYNAME>Windows 10 IoT Enterprise LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>19044.3758 Windows 10 IoT Enterprise LTSC</DISPLAYDESCRIPTION> </IMAGE> </WIM>
22621 ---> 22631 = 22621 + SV2Moment4 22635 = 22621 + SV2Beta 22621, same. 22631 and 22635, different for different Enablement and CU. ---------------------------------------------------------------- 22635 with SV2Beta ---> 235XX.1001with SV2Beta ---> Same SV2Beta Enablement name; Different build. So, one same 22621 family, there are three builds: Two different 2263X builds. One 235XX build based on 2263X with SV2Beta. ---> 22631 22635 23XXX To sum it up: SV2Moment4 and SV2Beta are different systems, don't mix. We can see them as: 22631, Official. 22635, Preview. So, you can do 22621 LTSC with two different CUs: 1. 22631 CU or 2. 22635 CU
Supports the following SKUs: Code: Microsoft-Windows-CoreCountrySpecificEdition Microsoft-Windows-CoreEdition Microsoft-Windows-CoreNEdition Microsoft-Windows-EnterpriseEvalEdition Microsoft-Windows-EnterpriseGEdition Microsoft-Windows-EnterpriseGNEdition Microsoft-Windows-EnterpriseNEvalEdition Microsoft-Windows-EnterpriseSEdition Microsoft-Windows-EnterpriseSEvalEdition Microsoft-Windows-EnterpriseSNEdition Microsoft-Windows-EnterpriseSNEvalEdition Microsoft-Windows-PPIProEdition Microsoft-Windows-ProfessionalEdition Microsoft-Windows-ProfessionalNEdition Microsoft-Windows-ServerAzureStackHCICorEdition Microsoft-Windows-ServerDatacenterCorEdition Microsoft-Windows-ServerDatacenterEdition Microsoft-Windows-StarterEdition Microsoft-Windows-StarterNEdition Supports the following LPs: Code: cs-CZ de-DE en-US es-ES fr-FR hu-HU it-IT ja-JP ko-KR nl-NL pl-PL pt-BR pt-PT ru-RU sv-SE tr-TR zh-CN zh-TW I did not conduct comprehensive testing, but theoretically, it is fully compatible with the 25398_OtherEditions-UUP-Patch and LPs of gailium119. In actual testing, Professional/EnterpriseS zh CN passed the test.
26002.1000 License Agreement is standalone from Editions package. e.g. Professional. (You can check Sessions.xml.) Professional is "Parent" of other 10 editions. But it uses three License Agreement packages. One for 9 Editions. One for IoTEnterprise. One for IoTEnterpriseK. In Microsoft-Windows-EditionSpecific-Professional-Package. Code: Microsoft-Windows-Licenses-Professional-Package Microsoft-Windows-Licenses-IoTEnterprise-Package Microsoft-Windows-Licenses-IoTEnterpriseK-Package
Hi if I update offline the install.wim, I get an error during installation. "Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation." dism /scratchdir:temp /image:mount /add-package:update\SSU-19041.3684-x64.cab dism /scratchdir:temp /image:mount /add-package:update\Windows10.0-KB5015684-x64_PSFX.cab dism /scratchdir:temp /image:mount /add-package:update\Windows10.0-KB5032189-x64.cab I want to update to 22h2. I using windows 10 EnterpriseG. (19041.1)