Can you check see if the 405 and 674 cumulative updates installed eventually, took a few reboots for me. The only thing I changed in your script was I'm using my own folder locations for Source, Updates and netfx3. Making the ISO now. Had to redo this, really messed up edit because I can't find the Spoiler option in the editing tool. Settings I used below , I get no errors during the build. Spoiler: W10UI_3.4 Script Settings Code: rem for updating current os, leave this option as %SystemDrive% set "target=d:\1 rem updates location, %cd% represent the current script directory set "repo=d:\3 rem dism.exe tool path (default is system's if the host os is win10) set "dismroot=%windir%\system32\dism.exe" rem enable .NET 3.5 feature set net35=1 rem optional, specify custom path for microsoft-windows-netfx3-ondemand-package.cab set "net35source=d:\5 rem Cleanup OS images to "compress" superseded components (might take long time to complete) set cleanup=1 rem Rebase OS images to "remove" superseded components (warning: might break "Reset this PC" feature) set resetbase=0 rem create new iso file if the target is a distribution folder rem require placing oscdimg.exe or cdimage.exe next to W10UI.cmd set iso=1 rem set this to 1 to start the process directly once you execute the script rem make sure you set the above options correctly first set autostart=0 rem optional, set directory for temporary extracted files set "cab_dir=%~d0\W10UItemp" rem optional, set mount directory for updating wim files set "mountdir=%SystemDrive%\W10UImount" set "winremount=%SystemDrive%\W10UImountre" When I start, and yes, I installed DISM from the Toolkit. And copied netfx3 .cab and the extracted July update ISO and updates to the correct folders. Spoiler: W10UI_3.4 On Start ============================================================ 1. Target (x64): "d:\1" 2. Updates: "d:\3" 3. DISM: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" 4. Enable .NET 3.5: YES 5. Cleanup System Image: YES 6. Reset Image Base: NO ============================================================ 0. Start the process ============================================================ Change a menu option, press 0 to start, or 9 to exit:
You're still missing a lot of updates, for example, the dynamic updates such as KB3197099 which were released only 4 days ago (August 29, 2017) but was listed on my post. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-225#post-1367709 The point of my list was to update everything.
KB3197099 is available since October 2016 https://forums.mydigitallife.net/posts/1282354/ a better point would be to have only latest updates of "everything" i.e. Code: latest SSU KB4035631 latest CU KB4039396 latest Flash KB4034662 latest Dynamic KB3197099, KB3176937 latest Safe OS KB4013419 latest Setup KB4033524 and the specific updates Code: .NET KB3186568 Privacy KB4013214 OOBE Upgrader KB4022632 Remedation KB4023057 Appraiser KB4033637
Could it be because i'm using the MSDN July update ISO instead of the June update? And with the June update which CUs etc. should I use?
It's september so the CU and flash on both iso's are already superseded, just use the last available CU = kb4034674 and flash = kb4034662
Am I correct when the Cumulative Update is released Tuesday I can replace the 674 update with it and I don't need to slip stream 674 as well? And I fixed the updates reinstalling by using the March 1703 ISO and Adding the 405, 662 and 674 updates. Now only Windows Defender definitions and the Malicious Software Tool install.
As said, i never experienced unexpected re-installs of already integrated updates, only when you enable dotnetfx3 by dism using the ondemand cab (not by using add features) after the integration of the current CU, it will reinstall a part of the latest released CU for updating dotnetfx3. And when you've pre-integrated a catalog only or release preview CU before enabling dotnetfx3 it will reinstall a part of the latest CU released on Windows Update and not the CU from catalog. For CU's it's really simple, you only need to integrate/install the most recent released. 405 is not a CU, it's the current servicing stack, not superseded by any other update, even when you would install a more current one, the old won't get the state "superseded" but when you integrate the most current one in a clean image, the old won't be needed to also be installed/integrated. This explanation is meant for official methods, not what 3rd party tools can cause by (mis-)using them.