KB3199389 is not completely superseded as dynamic update, but it's obsolete the files it contain and not present in kb4039556 are superseded by CU i.e. integrate CU to boot.wim/2 then copy updated files from sources folder
How this dynamic update files should be used? I usually copy/overwrite the files from the Dynamic update into a clean extracted iso on a usb stick. Is the CU integration necessary?
I just did an offline install with W10UI 3.4 with set cleanup=0 and resetbase=1, but no resetbase was done and I ended up with an image that went from 3gig (exported from install wim) to 7gig. The way I understood the options was cleanup compresses superseded components whereas resetbase removed superseded components. Why does cleanup need to on in order to allow a resetbase? Spoiler Code: ============================================================ 1. Target (x64): "x:\$W0\$0_WUI\x64\LTSB+09.wim" 2. Updates: "x:\$W0\$0_WUI\x64\Repo-Dir" 3. DISM: "x:\$W0\ADK_6\amd64\DISM\dism.exe" 4. Enable .NET 3.5: YES 5. Cleanup System Image: NO ============================================================ 0. Start the process ============================================================ Change a menu option, press 0 to start, or 9 to exit: 0 ============================================================ Extracting/Copying .cab files to temp folder ============================================================ 22:10 1/4: windows10.0-kb3186568-x64_Net47.msu 2/4: windows10.0-kb4035631-x64_SSTack.msu 3/4: windows10.0-kb4038782-x64_CU_0912.msu 4/4: windows10.0-kb4038806-x64_Flash.msu
Because Rebase is also a Cleanup operation, thus it's a sub-option what's wrong with setting both to 1?
Not a problem. I misunderstood the comments for those options and it was not clear to me until now that resetbase was a sub-option of cleanup in your program.
Spoiler: W10UI_3.4 15063.0 > 15063.608 Log ISO size: 3.45 GB (3,705,784,320 bytes) (10 index install.wim)
I remove Windows Home and the recovery image from my ISO using DISM, add all the motherboard drivers etc. I need with DISM to the install.wim so they are preinstalled when I install Windows Pro. It only has the Windows Pro image and the Windows install boot image. Can't boot into recovery console from my Windows install USB and no option to install Windows Home. I then use the cleanup=1, resetbase=0 and lastly I use Nlite with the trim option (though I already did that with DISM, don't think I need to) make ESD option to create the ISO. I tried making the ESD with DISM with max compression on but i find Nlite makes a much smaller ESD file for some reason. The ISO size when I'm done is 3.23GB and after I install Windows the only drivers I need to install are the Nvidia drivers and my PCI sound card. And like I said before if I add the 405 service stack and the latest flash and cumulative update to the official 1703 March ISO the 405 and cumulative updates don't reinstall in Windows Update. They do reinstall if I use the MSDN June or JULY ISO. Edit: When I get home I'll share how exactly I remove the Windows Home and recovery images with DISM.
Both methods to compress install.wim > install.esd (DISM export compression /recovery* or wimlib imagex) will differ just a few kb's in size, maybe NTLite chops some more, but imho is, if you don't know what the tool does, don't use it. * Code: dism /Export-Image /SourceImageFile:"x:\install.wim" /SourceIndex:1 /DestinationImageFile:"y:\install.esd" /Compress:recovery /checkintegrity You can get rid of any index by just exporting the other(s) to a new install.wim, or use the imagex delete index commandline* (or just use GimageX for it). * Code: imagex /delete d:\install.wim 1
if I use your DISM options to make the ESD file Thank you, Now I'm not using Nlite with your help and the iso I made is under 4GB which is what I need to fit on a 4GB USB drive. I just used DISM to remove the indexes though.
This is how I do my Windows ISOs for my PC. On my C: drive I make C:Mount C:\Mount\Drivers and C:\Mount\Wim folders. I extract Win10_1703_English_x64.iso the official March update ISO to the D:\1, my secondary SSD and copy the boot.wim and install.wim files from the D:\1\sources folder to C:\Mount Win10Pro Code: Dism /Delete-Image /ImageFile:C:\Mount\install.wim /Index:2 Dism /Delete-Image /ImageFile:C:\Mount\boot.wim /Index:1 Win10Home Code: Dism /Delete-Image /ImageFile:C:\Mount\install.wim /Index:1 Dism /Delete-Image /ImageFile:C:\Mount\boot.wim /Index:1 I put my ethernet driver, motherboard drivers and storage drivers (960 Pro, Intel 750 and ACHI drivers) .inf files and related files to the C:\Mount\Drivers folder. Code: DISM /Mount-Wim /WimFile:C:\Mount\install.wim /Index:1 /MountDir:C:\Mount\Wim DISM /Image:C:\Mount\Wim /Add-Driver /Driver:C:\Mount\Drivers /recurse /ForceUnsigned DISM /Unmount-Wim /MountDir:C:\Mount\Wim /Commit Some of my drivers are Unsigned so I use the Unsigned flag. Then I copy the install.wim and boot.wim back to the D:\1\sources folder overwriting the originals. Next I run W10UI.cmd with the 'set cleanup=1' 'set resetbase=0' options. Now I Code: dism /Export-Image /SourceImageFile:D:\1\sources\install.wim /SourceIndex:1 /DestinationImageFile:D:\1\sources\install.esd /Compress:recovery /checkintegrity I delete the original install.wim file from the D:\1\sources folder and I make an ISO from the D:\ 1 folder with ImgBurn. I ignore the error that it needs a boot option in ImgBurn and accept all the other options it changes. Booted and installed Windows Pro just fine, only drivers I need to install are my Nvidia drivers and PCI sound card drivers. Burn the ISO to a 4GB or bigger USB with Rufus. Still open to suggestions though as I'm new to this as a better option then ImgBurn or anything else needed.
The overall size of the install.wim won't be much different when all indexes are left untouched (no deletion needed). Simple tip: when you run W10UI directly on the multiple editions wim (home + pro) or on a 10 indexes wim, it will copy over the updated winre.wim from the first index to all indexes, so the size is not increased by the different winre.wim sizes. Example: My 15063.608 x64 install.wim (containing 10 indexes) size = 4.13 GB (4,443,719,980 bytes) After compressing to install.esd, the size = 2.97 GB (3,198,217,480 bytes) AiO ISO with install.esd: 3.47 GB (3,733,094,400 bytes) When you don't need the iso to be able to do an upgrade (clean install from boot only), you can use MSMG toolkit to delete all unneeded files from the iso, it will decrease the size to: 3.33 GB (3,578,898,432 bytes) But this thread is about publishing/installing/integrating updates.
With DISM how exactly do I add a language pack to the install.wim? That would be perfect for my purposes, have a Windows Pro/Home ISO with current updates integrated and the language packs I want. Edit: I tried Googling it but it was really confusing.
I never would add a language to my iso's, i prefer to do separate language iso's, but the best script to do it is @abbodi1406's W10MUI script.