There has been recently a lot of clean-up activity behind the scenes on the Windows Update servers. This started on 20/5/2019 according to my observations. A significant number of old superseded updates for Windows 10 1607 and Windows Server 2016 have been removed from Windows Update / expired in WSUS. Currently updates for 1703 go through the same process. Other superseded updates have also been removed in the last 24-48 hours like KB2734786 Update for Japanese Microsoft IME in various implementations. Very pleased to see this happening because as it stands now, Windows Update and WSUS are heavily bloated with updates which are not useful, in particular in the context of the cumulative update concept. Bloating of the WU servers is known to cause delays in scanning against Windows Update, sometimes making the scanning unavailable using the normal built-in tools. This has been happening few years ago on Windows 7 and I think happens right now on Windows 8.1/2012 R2. For those interested to monitor this process in Windows Update, I suppose the easy way is to launch WUMT with the "Include superseded" option while running it against an RTM distribution of the 1607/2016 or 1703.
What I find interesting is that when scanning Windows 10 against Microsoft Update with WUMT in the past, KB2734786 appeared as installed (3 times), although there was no way that I knew how to uninstall them. Those patches were built-in. Now when they were removed from MU/WSUS, they do not appear as installed anymore, because there is no reference to them on the back-end servers.
Windows 10 Version 1903 Please, Tell Me: To integrate the Updates, is it One to One? or How is the Correct Way? C:\Windows\System32> dism /online /add-Package /PackagePath:c:\windows10.0-kb4498523-x64.cab dism /online /add-Package /PackagePath:c:\windows10.0-kb4497935-x64.cab dism /online /add-Package /PackagePath:c:\windows10.0-kb4502374-x64.cab
SSU first, next CU. Code: dism /online /add-Package /PackagePath:c:\windows10.0-kb4498523-x64.cab /PackagePath:c:\windows10.0-kb4497935-x64.cab Is not a CBS update (it's for updating ISO:\Sources).
great Sir, /sources/boot.win 2 indexes must be actualized with any of this updates? & exported to reduce size? can we /ceanup-image /startcomponentcleanup this actualized wims? my problem is to generate a EDUCATION RETAIL version up to date...from uup 18362.1 with pro & virtualversions but not VL KMS KEY or do it from consumer edition x64 18362.30 ??? saludos
Use W10UI and feed it an extracted iso folder + the needed updates and it does all for you EDIT, @drew84 noticed that the script doesn't put the DU setup files in the iso. Do it manually: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-406#post-1526578
W10UI, some questions, and an observation. Code: - Handle dynamic updates for setup media 'sources' folder (skip installing it, extract it for distribution target) ... skip installing it (Q. presumably if already superseded). ... extract it for distribution target (Q. to a TEMP folder (if so, where?) or as states the distribution target (sources) folder). Script works perfectly except this last part has never succeeded in my case since implementation. Code: ============================================================ Running W10UI v6.4 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/5: Windows10.0-KB4495620-x64_NFU_18362.102.cab 2/5: Windows10.0-KB4497932-x64_FSU_18362.114.cab 3/5: windows10.0-kb4497935-x64_CCU_18362.145.cab 4/5: windows10.0-kb4498523-x64_SSU_18362.144.cab 5/5: windows10.0-kb4502374-x64_SDU_18362.141.cab << - updated target still has this as 18362.001 ... files all in same folder and all extracted successfully EDIT: solved
That's a question for @abbodi1406, personally i never use the setup du's nor the cbs ones, and when i did (in the past), i already copied them manually to the W10UI work folder (extracted iso).
Agreed, Was originally aiming the question at @abbodi1406, but in the end adapted post to follow on from previous converstion Previously always handled DU's manually, just recently started using the script to test if it indeed works (saves 1 step in operation) AS a rule I always have a virgin distribution target on HDD, to which I would usually extract the DU directly to sources folder, .. all other updates to UPDATES folder, then run prepared script -> updated installation media.
Patch boot.wim #2 will update some du files. But not for all. Some times will be downgrade. Like you put du files in current place, after #2 progress done. DLL build downgrade from 404 to 292(17763 example)
Afaik, the dynamic updates for setup media (iso:\sources) don't go into any other place. Dynamic updates for dism integration are superseded by the CU very fast after release.
W10UI expand DU to iso\sources normal boot.wim\2\sources is updated with CU (cannot be controlled) uup boot.wim\2\sources is updated manually with DU (if any) during creation