Unless someone knows where in the registry the pause durition value is set, then the solution I offered is probably *not* good for mass producing a fleet of pre-configured devices. On each of my online devices, I add the registry key, open the update control panel and manually set the pause duration. The key I shared only allows you to have a pause duration of 180 years. AFAIK, you have to manually make the change in the advanced update control panel ms-settings:windowsupdate-options on a device-by-device basis.
Q: For Custom Update, which is easier and POSSIBLE, old (as of 17763) or new (since 18362) update technology? A: New.
19044.1237 Windows 10 IoT Enterprise LTSC arm64 Code: WIM Information: --------------------- GUID:{27D8412A-06BD-45A0-97B1-FED4605B8D02} Image Count:1 Compression:LZX Part Number:1/1 Attributes:0x8 RP_FIX Image Index: 1 ------------------- Name:Windows 10 IoT Enterprise LTSC 2021 Description:Windows 10 IoT Enterprise LTSC 2021 Flags:IoTEnterpriseS Files:90746 Folders:28080 Expanded Size:12731 MB WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3241038932</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>28080</DIRCOUNT> <FILECOUNT>90746</FILECOUNT> <TOTALBYTES>13350206697</TOTALBYTES> <HARDLINKBYTES>6132768771</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D5AD00</HIGHPART> <LOWPART>0xA8B782B5</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D7AA3B</HIGHPART> <LOWPART>0x9768E5C5</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>IoTEnterpriseS</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.19041.1202;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19044</BUILD> <SPBUILD>1237</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>Windows 10 IoT Enterprise LTSC</DISPLAYDESCRIPTION> </IMAGE> </WIM>
18362.1.190318-1202.19H1_RELEASE_ENTERPRISE_LTSC_OEM_A64FRE_XX-XX_LITE.wim for testing on QEMU. 2.8 GB --> 2.3 GB Start: 12:55 Finish: 13:45
[NOTE/EDIT this projected has a new update [Post #4865] Windows 10 Enterprise LTSC IoTEnterpriseS edition 19043.1237 Reconstruction Project [edit 17 SEP 21 - correct Build number. Thanks @SunLion!] This is a tribute/homage to @whatever127's educational project to recreate unavailable Windows editions from officially available resources using DISM only. This post presents a scaled down sub-set (SDSS) of @whatever127's bigger project. The SDSS project is limited to recreating the IoTEnterpriseS edition of Windows 10 Enterprise LTSC (IOT) from a prerequisite single index install.wim of the Windows 10 Pro edition (PRO) using baseless updates (BASELESS-PSF-CAB). Only English (United States) PRO images, BASELESS-PSF-CABs and recreated IOT editions are supported. Usage In order to create the desired edition, the Update Build Revision (UBR) number and architecture of the UUP compiled resources must match. For example: Match PRO x64 19043.1237 install.wim with BASELESS-PSF-CABs KB5005565-x64. To create the IOT edition using files provided with this SDSS project you need to do the following: 1. Download all required SDSS project files from next post in this thread 2. Extract the main archive of the SDSS project to a short path, for example: C:\work 3. Extract from an ISO or create a single index PRO install.wim and put it in the main directory 4. Download the BASELESS-PSF-CABs. UBR matches PRO install.wim e.g. 1237 and put them in the main directory 5. Run build.cmd and let it do its magic 6. Use your IOT install.wim to install your OS All logs of the process can be found in the logs directory which is created when starting the SDSS build process. If the SDSS build process fails, discard the image that was mounted by the script using Code: dism /unmount-wim /mountdir:mount /discard The provided SDSS project files are for UBR 1237 Modify build.cmd and 2.xml to support prior/future UBRs Example of *retrograde* from 1237 to 1200 Replace all instances of words/numbers KB5005565 by KB5005101 and 1237 by 1200 in build.cmd and 2.xml Once you've built your OS, confirm the desired outcome by running the following Code: dism /online /get-currentedition