I use W10UI.cmd and add the 662 and 674 updates to my 1703 July Update Official MSDN ISO file. It has the sha-1 verified before installing the updates. In Windows Control Panel under Programs and Features it says the kb4022405-x64 and kb4034674-x64 updates are already installed but doesn't say they are installed in Settings and on my first Windows update it reinstalls both the kb4022405-x64 and kb4034674-x64 updates. Any way to stop them from reinstalling? I've also tried adding them with NLite, same issue. Edit: I update the image with W10UI.cmd than make the ISO with NLIte so I can add my personal device drivers to the image. :/
The used iso is compiled by MSFT with a SSTACK, July CU and the FLASH update already pre-integrated, so they don't show up in setting>updates and security>windows update>history. But they will show up at "installed updates". So if you install more current FLASH update and CU, the old CU will disappear from "installed updates" and the new one will be there. PS, No real need for any third party tool to integrate drivers, dism does it all.
Well, I installed the KB4034674 update with W10UI.cmd and KB4034662, the MSDN July update ISO has the KB4022405 update installed already. I then added all the drivers I need with DISM and on a clean install when I update Windows it installs both the 674 and 405 Cumulative Update. It hurts my techie OCD that it does this. Good news is all the drivers I needed installed right so a small victory.
Here are the steps to setup for and inject the drivers into the boot.wim file with DISM. Preparation Create the following folders on the root of the C drive: C:\Mount C:\Mount\Drivers C:\Mount\BootWIM Copy the drivers you wish to inject into the C:\Mount\Drivers folder Copy boot.wim from your image /sources folder to the C:\Mount folder. Execution: Open a CMD prompt as Administrator. Navigate to "C:\Mount". Use the following DISM commands to mount the Boot.wim: DISM /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:1 /MountDir:C:\Mount\BootWIM Use the following DISM command to add the driver: DISM /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse Use the following DISM command to unmount the Boot.wim: DISM /Unmount-Wim /MountDir:C:\Mount\BootWIM /Commit If any drivers are unsigned add do this below instead of Step 4. DISM /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse /ForceUnsigned Installed my drivers to the install.wim though instead of the boot.wim. I think that's okay as I wanted the added in Windows already after the install and not just loaded on boot as I like to add additional hardware after the install. I think that's okay?
I just noticed that W10UI got updated from 3.3 to 3.4, but I don't recall the changes in 3.4 being discussed anywhere, so I was still using 3.4.
I did not know where else to ask, but didn't want to start another "probably useless" thread. I noticed that if you rebase the image two times in a row, the second time it usually reaches 20% and then done. However, if you disable a bunch of features from Optional Features, like Windows Search, SMB 1.0, Printing, etc., after the first rebase, then rebasing second time results in rebasing quiting at much higher %. This happens even if NetFX 3.5 is not touched or was never enabled in the first place. What does it mean? Why does disabling features result more files being rebased/replaced after all files were already rebased/replaced by the first rebasing before disabling features?
Do you know what resetbase does? It deletes the superseeded components (end it breaks windows options like resetpc afterwards), the second time it runs the percentages always are shown less then 100%.
hmm some minutes ago I was using wumt and in there is show KB4033637 (for 1607) and download don't end never (maybe some huge download ) although in right side appear only 4.04MB maybe I'm wrong but I think is update for 1703 or 1709 so I cancel download until I know more about this strange KB if someone here can help me I like very much thanks in advance