can updateos 3.1 make 20348 custom updates? vn-z.vn/threads/windows-11-enterprise-g-24h2-build-26100-268-re-contruction.95047/page-46#post-1242951
we still have some work to do before we get a working custom update - 2012mshs has helped me a lot with trying to develop this 20348 client update mod - the challenge is to get the UBR to match the update
It can and modified LCUs do install on the constructed Pro image: Code: -------------------------------!! ATTENTION !!----------------------------- ------------------!! Windows update needs some minutes !!------------------ ----------------------!! Create mount and scratch folders !!--------------- ----------------------!! Get index id in install.wim !!-------------------- ----------------------!! Mount install.wim !!------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Mounting image [==========================100.0%==========================] The operation completed successfully. ----------------------!! Custom cumulative updates !!---------------------- =========================================================================== Add cumulative updates =========================================================================== Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.20348.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3440~31bf3856ad364e35~amd64~~20348.3440.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.20348.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.3453.1.14 [==========================100.0%==========================] The operation completed successfully. Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\lcu.txt Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\lcu_n.txt =========================================================================== Finished update --------------------------------------------------------------------------- Add Drivers --------------------------------------------------------------------------- Clean-up Wim --------------------------------------------------------------------------- Check pending update =========================================================================== =========================================================================== Auto Cleanup WinSxS after install Windows =========================================================================== =========================================================================== Update WinRE =========================================================================== 1 file(s) copied. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Mounting image [==========================100.0%==========================] The operation completed successfully. lcu_mod\SSU-20348.3440-x64.esd 1 file(s) copied. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.20348.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3440~31bf3856ad364e35~amd64~~20348.3440.1.0 [==========================100.0%==========================] The operation completed successfully. Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\lcu_re.txt Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\lcu_re\SSU-20348.3440-x64.esd Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.20348.1 Searching for driver packages to install... Found 7 driver package(s) to install. Installing 1 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Intel NVMe Driver v5.3.0.1010\IaNVMe.inf: The driver package was successfully installed. Installing 2 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Intel_13TH_IRST_Driver\HsaComponent\iaStorHsaComponent.inf: The driver package was successfully installed. Installing 3 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Intel_13TH_IRST_Driver\HsaExtension\iaStorHsa_Ext.inf: The driver package was successfully installed. Installing 4 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Intel_13TH_IRST_Driver\iaStorVD.inf: The driver package was successfully installed. Installing 5 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Micron NVMe driver v2.1.19.0\mtinvme.inf: The driver package was successfully installed. Installing 6 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Samsung NVMe driver v3.3.0.2003\secnvme.inf: The driver package was successfully installed. Installing 7 of 7 - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\Drivers\Western Digital, HGST NVMe driver v3.3.2102.41615\nvme_wdc.inf: The driver package was successfully installed. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.20348.1 [===========================60.0%== ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image File : D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\wim\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. "wim\winre.wim" original size: 427050 KiB Using LZX compression with 16 threads Archiving file data: 1108 MiB of 1108 MiB (100%) done "wim\winre.wim" optimized size: 420252 KiB Space saved: 6797 KiB 1 file(s) moved. =========================================================================== Save and unmount install.wim =========================================================================== Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image File : D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\wim\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. =========================================================================== Optimize install.wim =========================================================================== Using LZX compression with 16 threads Archiving file data: 9284 MiB of 9284 MiB (100%) done Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\wim\install.wim =========================================================================== Bypass TPM =========================================================================== =========================================================================== Clean up =========================================================================== Deleted file - D:\Users\Administrator\Desktop\UpdateOS_EN_V3.1\Data\INDEXLIST.TXT Mission took 0:20:42.32 (1242.32s total) --------------------------------------------------------------------------- Script by [email protected] --------------------------------------------------------------------------- Just that LCU installs as a pending package, which is quite weird. EDIT: It didn't work. It would be way better to just wait for WPMT. Spoiler: "updated" system
Q: What is Microsoft-Windows-ClientRootSecurity? [Client] Microsoft-Windows-ClientRootSecurity-Package Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-ClientRootSecurity" version="10.0.27842.1000" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <directories> <directory destinationPath="$(runtime.bootDrive)\"> <securityDescriptor name="WRP_CLIENT_ROOT_DIR_DEFAULT_SDDL" /> </directory> </directories> <trustInfo> <security> <accessControl> <securityDescriptorDefinitions> <securityDescriptorDefinition name="WRP_CLIENT_ROOT_DIR_DEFAULT_SDDL" sddl="O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:P(A;OICI;GA;;;BA)(A;OICI;GA;;;SY)(A;OICI;0x1200a9;;;BU)(A;OICIIO;SDGXGWGR;;;AU)(A;;0x4;;;AU)(A;;0x1000a1;;;S-1-15-3-65536-1888954469-739942743-1668119174-2468466756-4239452838-1296943325-355587736-700089176)S:P(ML;OINPIO;NW;;;HI)" operationHint="replace" /> </securityDescriptorDefinitions> </accessControl> </security> </trustInfo> </assembly> [Server] Microsoft-Windows-ClientRootSecurity-Package-base-Package Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-ClientRootSecurity" version="10.0.26376.5000" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <directories> <directory destinationPath="$(runtime.bootDrive)\"> <securityDescriptor name="WRP_CLIENT_ROOT_DIR_DEFAULT_SDDL" /> </directory> </directories> <trustInfo> <security> <accessControl> <securityDescriptorDefinitions> <securityDescriptorDefinition name="WRP_CLIENT_ROOT_DIR_DEFAULT_SDDL" sddl="O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:P(A;OICI;GA;;;BA)(A;OICI;GA;;;SY)(A;OICI;0x1200a9;;;BU)(A;OICIIO;SDGXGWGR;;;AU)(A;;0x4;;;AU)(A;;0x1000a1;;;S-1-15-3-65536-1888954469-739942743-1668119174-2468466756-4239452838-1296943325-355587736-700089176)S:P(ML;OINPIO;NW;;;HI)" operationHint="replace" /> </securityDescriptorDefinitions> </accessControl> </security> </trustInfo> <localization> <resources culture="en-US"> <stringTable> <string id="description" value="Provide default security for offline image" /> <string id="displayName" value="Provide default security for offline image" /> </stringTable> </resources> </localization> </assembly>
It is firstly posted by zwl29107 for "renaming" package... Isn't it? Posted By zwl29107: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-95#post-1876273 Followed by xinso: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-96#post-1876391 Followed by gailium119: https://forums.mydigitallife.net/th...s-reconstructions.88605/page-102#post-1876949
Q: Is it more efficient to use the smallest image as reconstruction Source? A: Of course if only Target image could be perfect. Last night, I tried to slim down the Source image a bit further, the OOBE of Target installation can not input abc123. No abc123; no go. No matter how many ways\times you tried to install. Successfully completed != Perfectly reconstructed Q: Why?
To construct a tiny base image for Reconstruction with few tiny packages in Edition mum, the Cbs asking for a module before it can proceed. Q: What module does it mean? Which package has this module?
What's the point of using neutral base anyway? Microsoft uses Starter(N), ServerWeb and ServerStandardCor to construct Client(N), Server (Full) and Server (Core).