Still no pre September 2016 fixes added to Monthly Rollup even though WUA got updated, but AMD Carrizo thing still listed as not fixed this rollup model is boring
Regarding some .NET 3.5.1 updates that still required for non en-us systems although they are not officially superseded per CBS rules, but they are superseded per WU metadata 3032655 3096436 3142024 3210131 after checking the actual language files included, it turns out that all files are still the same as inbox Windows 7 SP1 files therefore, these updates are *Not Needed* anymore for non en-us systems 3210131 has a special exception, it has some updated lang files, but they are the same as Convenience Rollup KB3125574 so it's only needed for non en-us systems WithoutKB3125574
Maybe o/t (maybe not) question (calling on Master abbodi1406 ) why on fresh install with Conv Rollup 3125574 WU ask for the following 10 updates (also others) supposedly superseded by / included in KB3125574? Spoiler: KB's Ask by WU KB2574819 (RDP) KB2603229 (not allowed offline) KB2732059 KB2773072 KB2830477 KB2834140 KB2919469 KB2970228 KB3006137 KB3102429 Spoiler: Replaced by 3125574 Update for Windows 7 for x64-based Systems (KB2574819) Update for Windows 7 for x64-based Systems (KB2603229) Update for Windows 7 for x64-based Systems (KB2607047) Update for Windows 7 for x64-based Systems (KB2607576) Update for Windows 7 for x64-based Systems (KB2633952) Update for Windows 7 for x64-based Systems (KB2639308) Update for Windows 7 for x64-based Systems (KB2640148) Update for Windows 7 for x64-based Systems (KB2647753) Update for Windows 7 for x64-based Systems (KB2660075) Update for Windows 7 for x64-based Systems (KB2661254) Update for Windows 7 for x64-based Systems (KB2677070) Update for Windows 7 for x64-based Systems (KB2679255) Update for Windows 7 for x64-based Systems (KB2699779) Update for Windows 7 for x64-based Systems (KB2709630) Update for Windows 7 for x64-based Systems (KB2709981) Update for Windows 7 for x64-based Systems (KB2719857) Update for Windows 7 for x64-based Systems (KB2726535) Update for Windows 7 for x64-based Systems (KB2731771) Update for Windows 7 for x64-based Systems (KB2732059) Update for Windows 7 for x64-based Systems (KB2732487) Update for Windows 7 for x64-based Systems (KB2732500) Update for Windows 7 for x64-based Systems (KB2735855) Update for Windows 7 for x64-based Systems (KB2739159) Update for Windows 7 for x64-based Systems (KB2741355) Update for Windows 7 for x64-based Systems (KB2749655) Update for Windows 7 for x64-based Systems (KB2756822) Update for Windows 7 for x64-based Systems (KB2760730) Update for Windows 7 for x64-based Systems (KB2762895) Update for Windows 7 for x64-based Systems (KB2763523) Update for Windows 7 for x64-based Systems (KB2773072) Update for Windows 7 for x64-based Systems (KB2779562) Update for Windows 7 for x64-based Systems (KB2786081) Update for Windows 7 for x64-based Systems (KB2786400) Update for Windows 7 for x64-based Systems (KB2791765) Update for Windows 7 for x64-based Systems (KB2794119) Update for Windows 7 for x64-based Systems (KB2798162) Update for Windows 7 for x64-based Systems (KB2799926) Update for Windows 7 for x64-based Systems (KB2800095) Update for Windows 7 for x64-based Systems (KB2808679) Update for Windows 7 for x64-based Systems (KB2813956) Update for Windows 7 for x64-based Systems (KB2829104) Update for Windows 7 for x64-based Systems (KB2830477) Update for Windows 7 for x64-based Systems (KB2834140) Update for Windows 7 for x64-based Systems (KB2835174) Update for Windows 7 for x64-based Systems (KB2836502) Update for Windows 7 for x64-based Systems (KB2843630) Update for Windows 7 for x64-based Systems (KB2846960) Update for Windows 7 for x64-based Systems (KB2846960) Update for Windows 7 for x64-based Systems (KB2847077) Update for Windows 7 for x64-based Systems (KB2852386) Update for Windows 7 for x64-based Systems (KB2853952) Update for Windows 7 for x64-based Systems (KB2863058) Update for Windows 7 for x64-based Systems (KB2868116) Update for Windows 7 for x64-based Systems (KB2882822) Update for Windows 7 for x64-based Systems (KB2888049) Update for Windows 7 for x64-based Systems (KB2890882) Update for Windows 7 for x64-based Systems (KB2891804) Update for Windows 7 for x64-based Systems (KB2893519) Update for Windows 7 for x64-based Systems (KB2904266) Update for Windows 7 for x64-based Systems (KB2905454) Update for Windows 7 for x64-based Systems (KB2908783) Update for Windows 7 for x64-based Systems (KB2913152) Update for Windows 7 for x64-based Systems (KB2913431) Update for Windows 7 for x64-based Systems (KB2913751) Update for Windows 7 for x64-based Systems (KB2918077) Update for Windows 7 for x64-based Systems (KB2919469) Update for Windows 7 for x64-based Systems (KB2922717) Update for Windows 7 for x64-based Systems (KB2923398) Update for Windows 7 for x64-based Systems (KB2923545) Update for Windows 7 for x64-based Systems (KB2928562) Update for Windows 7 for x64-based Systems (KB2929733) Update for Windows 7 for x64-based Systems (KB2929755) Update for Windows 7 for x64-based Systems (KB2966583) Update for Windows 7 for x64-based Systems (KB2970228) Update for Windows 7 for x64-based Systems (KB2973337) Update for Windows 7 for x64-based Systems (KB2977728) Update for Windows 7 for x64-based Systems (KB2978092) Update for Windows 7 for x64-based Systems (KB2980245) Update for Windows 7 for x64-based Systems (KB2981580) Update for Windows 7 for x64-based Systems (KB2985461) Update for Windows 7 for x64-based Systems (KB2994023) Update for Windows 7 for x64-based Systems (KB2998527) Update for Windows 7 for x64-based Systems (KB2999226) Update for Windows 7 for x64-based Systems (KB3000988) Update for Windows 7 for x64-based Systems (KB3001554) Update for Windows 7 for x64-based Systems (KB3004394) Update for Windows 7 for x64-based Systems (KB3005788) Update for Windows 7 for x64-based Systems (KB3006121) Update for Windows 7 for x64-based Systems (KB3006137) Update for Windows 7 for x64-based Systems (KB3006625) Update for Windows 7 for x64-based Systems (KB3008627) Update for Windows 7 for x64-based Systems (KB3009736) Update for Windows 7 for x64-based Systems (KB3013410) Update for Windows 7 for x64-based Systems (KB3013531) Update for Windows 7 for x64-based Systems (KB3014406) Update for Windows 7 for x64-based Systems (KB3020338) Update for Windows 7 for x64-based Systems (KB3020370) Update for Windows 7 for x64-based Systems (KB3040272) Update for Windows 7 for x64-based Systems (KB3045645) Update for Windows 7 for x64-based Systems (KB3048761) Update for Windows 7 for x64-based Systems (KB3049874) Update for Windows 7 for x64-based Systems (KB3054476) Update for Windows 7 for x64-based Systems (KB3065979) Update for Windows 7 for x64-based Systems (KB3068708) Update for Windows 7 for x64-based Systems (KB3075249) Update for Windows 7 for x64-based Systems (KB3077715) Update for Windows 7 for x64-based Systems (KB3078667) Update for Windows 7 for x64-based Systems (KB3080079) Update for Windows 7 for x64-based Systems (KB3080149) Update for Windows 7 for x64-based Systems (KB3081954) Update for Windows 7 for x64-based Systems (KB3092627) Update for Windows 7 for x64-based Systems (KB3095649) Update for Windows 7 for x64-based Systems (KB3102429) Update for Windows 7 for x64-based Systems (KB3107998) Update for Windows 7 for x64-based Systems (KB3112148) Update for Windows 7 for x64-based Systems (KB3118401) Update for Windows 7 for x64-based Systems (KB3121255) Update for Windows 7 for x64-based Systems (KB3133977) Update for Windows 7 for x64-based Systems (KB3137061) Update for Windows 7 for x64-based Systems (KB3138378) Update for Windows 7 for x64-based Systems (KB3138901) Update for Windows 7 for x64-based Systems (KB3147071) Update for Windows 7 for x64-based Systems (KB3148851)
You could import KB3125574 from Catalog in WSUS and you would see the supersedence built-in this update and likely the behaviour which you would expect. In such a case there is supersedence metadata in KB3125774 which works, although I have no way to know if it was implemented accurately. In case of Windows Update though, it behaves as abbodi1406 says, because KB3125774 does not exist for WU.
@abbodi1406 A couple of questions, I'm sure you can help (W7 x64) 1. The WMF 5.1 msu contains several cabs. In both of your w/ and w/o Convenience RU update installer scripts you seem to skip (delete) all included cabs except main payload 3191566 if installing WMF 5.1 (provided prerequisites are met). Specifically the 2809215 cab is superseded by Convenience RU. I applied the WMF 5.1 msu by running it a setupcomplete.cmd succesfully, to an offline-updated image (w/ CRU script used). Eventlog reports that 2809215 was installed in addition to 3191566 (the remaining cabs were certainly skipped as in your script). So, is 2809215 actually required? 2. I would like to use dism to install the "not allowed offline" updates in addition to WMF 5.1 at setupcomplete.cmd to avoid the WU service dependency (currently I'm simply running the msu files in proper order from the cmd file, but this requires WU service running). Those msu files usually contain several cabs or an exe file plus a cab file. Is it correct to just follow the PkgInstallOrder.txt file and issue dism add-package commands pointing to the extracted cabs and/or running the exes accordingly (same order)?
1. KB2809215 is not required w/ CRU, but it will be always installable regardless if superseded w/o CRU, KB2809215 exists as separate update, so it will be skipped when installing WMF through the script similar case with KB2872035 KB3033929 is replaced with Monthly Quality Rollup 2. Following PkgInstallOrder.txt steps would work but i think some or all these exe files require system privileges to work properly not sure if setupcomplete.cmd runs in system account KB2603229 has special case, UpdateWowRegisteredOwner.exe is contained within the cab file so you will need to extract it first
Afaik, setupcomplete.cmd runs with the highest permission level possible but why not installing them in Audit mode?
@abbodi1406 So do you mean extracting the exe from cab in advance, then, when installing OS, running both the extracted exe and the dism add-package command on the cab? Any required relative order? @Enthousiast I have yet to read that super nice thread by s1ave77 regarding audit mode, to evaluate its possible benefits. Right now what's working for me is briefly as follows: - USB boot to WinPE - Disk setup, updated and tweaked install.wim deployment (no need for iso) using WinNTSetup, plus suitable unnatend xml (no audit pass), drivers, standalone $oem$ folder (contains setupcomplete.cmd, online msu files, redists and final tweaks, easily updatable) and and automated programs/data copy to host storage via post-deploy cmd - USB removal and reboot. After around 30 minutes the host PC is fully ready for use. I use setupcomplete.cmd for msu (maybe cabs now?) and redist installation, then chainload a cmd at HKLM\RunOnce for most part of final OS tweaking and shortcuts to portables setup. A finishing cmd at HKCU\RunOnce applies those tweaks requiring an user logged in, plus installs some light programs which pose an advantage in being readily available at system startup (Classic Shell, 7-zip, etc). This last cmd reboots the box to apply changes.
I use the audit/sysprep/capture method in vmware, to produce an re-usable install.wim, to have most ready and really pre-installed (for deployment on multiple systems). No (auto)unattend.xml, setupcomplete.cmd's and no tweaks whatsoever, installs in 10 min It was a suggestion for another route to try