Windows, all in Sessions.xml. You can make it whatever you like as Microsoft does. All you have to provide for the reconstruction is the packages which are not included in the source image.
you said few times about that Sessions ... but it is a bit confusing ... can i edit the session in some way ? whenever you have time to explain i will try to learn ... Have a good night and hope i will get the point in time
Sessions.xml is the image creation log. From the log, we can see how Microsoft installs packages for all available SKUs, and then remove those Non-SAC SKUs. So, you can edit the mum according to Sessions.xml. The problem is about UPDATE. As of 17763.1, you CAN add\remove any package without affecting Update. (Because the Update updates components.) -------------------------------------------------------------------------------------------------------------------------- From 18362.1 forward, NO. (Because the Update updates packages according to the new mums.)
17763.2452 Windows 10 Client LTSC arm64 [EnterpriseS] Code: WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3844319028</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>34872</DIRCOUNT> <FILECOUNT>129801</FILECOUNT> <TOTALBYTES>14465499041</TOTALBYTES> <HARDLINKBYTES>6506471209</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D7FA70</HIGHPART> <LOWPART>0x6B0E64BA</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D8076C</HIGHPART> <LOWPART>0x1A609BE3</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>EnterpriseS</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.17763.2028;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>xx-XX</LANGUAGE> <FALLBACK LANGUAGE="xx-XX">en-US</FALLBACK> <DEFAULT>xx-XX</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>17763</BUILD> <SPBUILD>2452</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>rs5_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Enterprise LTSC 2019</NAME> <DESCRIPTION>Windows 10 Enterprise LTSC 2019</DESCRIPTION> <FLAGS>EnterpriseS</FLAGS> <DISPLAYNAME>Windows 10 Enterprise LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 Enterprise LTSC</DISPLAYDESCRIPTION> </IMAGE> </WIM> [EnterpriseSN] Code: WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3858958137</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>35229</DIRCOUNT> <FILECOUNT>131006</FILECOUNT> <TOTALBYTES>14176309103</TOTALBYTES> <HARDLINKBYTES>6331898408</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D7ECCD</HIGHPART> <LOWPART>0x29DBD66C</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D8077D</HIGHPART> <LOWPART>0x3EF5F9E8</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>EnterpriseSN</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.17763.2028;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>xx-XX</LANGUAGE> <FALLBACK LANGUAGE="xx-XX">en-US</FALLBACK> <DEFAULT>xx-XX</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>17763</BUILD> <SPBUILD>2452</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>rs5_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Enterprise N LTSC 2019</NAME> <DESCRIPTION>Windows 10 Enterprise N LTSC 2019</DESCRIPTION> <FLAGS>EnterpriseSN</FLAGS> <DISPLAYNAME>Windows 10 Enterprise N LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 Enterprise N LTSC</DISPLAYDESCRIPTION> </IMAGE> </WIM>
Oh, too big for free site. Maybe UUP ISO script will be better. EnterpriseS + x86 + amd64 + arm64 + 38 Languages
The difference between 17763 LTSC and 19041 LTSC is the 19041 has these two mandatory packages in SKU mum. Code: <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> So, add two packages to 17763.1 LiteR SKU mum and replace all 17763.1 with 19041.1, and it is 19041.1 LiteR. Do you have 17763.1 LiteR script? No. Then you have to look at the SKU mum in the LiteR install.wim\Windows\Servicing\Packages.
I dig in the 17763.1 LiteR mum files modified by you in the time you were building this beauty image and i need your advice if i manage to do it right in order to build 19041.1 LiteR. Thanks for your time !!!
The Parent packages are alright. But the contents of the following packages are not the same. Microsoft-Windows-Client-Desktop-Required-Package Microsoft-Windows-Client-Features-Package So, you need to test it yourself. To reconstruct with Core install.wim, you have to 1. rename Microsoft-Windows-EditionPack-Professional-Package and wow64 and language pack to Microsoft-Windows-EditionPack-Starter-Package and wow64 and language pack 2. remove Microsoft-Windows-Holographic-Desktop-Merged-Package manually To update, you have to use Custom Update. (Modify\Create the mums in LCU the way you rearrange original mums.)
I tried to install packages to x86 UUP SKU esd, and by mistake I installed Microsoft-Windows-Client-Desktop-Required-Package to my system. Then I made a new 19044.1466 amd64 with 19041.1_Professional_to_EnterpriseS_UUP_ISO.7z to repair. Outcome: Both to no avail dism /online /cleanup-image /restorehealth /source:wim:z:\install.wim:1 /limitaccess dism /online /cleanup-image /restorehealth /source:z:\install.wim /limitaccess Then I re-installed all updates and ran sfc /scannow. OK! No Integrity Violations found.