Burf, thank you for updating the lists. I looked at the x86 list and have some feedback (may apply to x64 as well). See what you think: listed is groove2013-kb2910935 but kb2920746 is newer listed is onenote2013-kb2899502 but kb2956165 is newer listed is publisher2013-kb2768358 but kb2883048 is newer listed is riched202013-kb2899501 but kb2920769 is newer listed is wxpnse2013-kb2880978 but kb2880977 is newer ppaddin2013-kb2920743 should be removed from list since ppaddin2013-kb2956171 is also in it Thanks again for updating the lists.
Oops thanks for that! I'll check it out a bit later tonight (in a couple of hours), once I am able to . I usually do check these things, I just assumed Microsoft weren't going to release old updates anymore now they've claimed they've essentially merged the hotfixes with the general release updates.
I apologise for running out of time tonight to look into those, it's 2.25 am Thursday here. I'll take a look tomorrow (today) afternoon/evening when I get home . The lack of these updates won't affect existing systems, it's only those doing a complete fresh install of Office that will temporarily be missing the latest of these updates.
WHDownloader 2015/03/11: Spoiler Added: Code: 3002657-x64 3012235-v3 3012702 3013172 3018133 3022796 3024751 3024755 3025417 3027209 3029606 3029803 3030377 3030947 3032323 3032359 3033889 3034344 3034348 3035017 3035126 3035132 3035527 3035553 3036228 3036562 3036612 3039066 3044132 3046049 2970653-x64 3014136 3014406 3018454 3020717-x64 3021052 3021190 3021946 3022752 3023869-v4-x64 3025370 3027174-v3 3029348 3031436 3032331-v2 3032590 3033446 3033510 3033930 3035899 3036155 3036579-v2 3036606 3036965 3037317 3037924 3038002 3038017 3038022 3039024-v4 3042085 Removed/Superseded: Code: 2976536 (by 3025417) 3006958 (by 3029803) 3006989 (by 3033889) 3007058 (by 3034348) 3009599 (by 3021190) 3013455-v2 (by 3034344) 3014140 (by 3027209) 3019868 (by 3036562) 3021674 (by 3012702) 3021952 (by 3032359) 3021953 (by 3044132) 3023607 (by 3046049) 3026738 (by 3035017) 3027110-x64 (by 2970653-x64) 3029944 (by 3035132) 3031079 (by 3035553) 3034196 (by 3032359) 3036197 (by 3032359) 3038031 (by 3032359) Removed / WU.Satisfy: Code: 2955164 2958262 2961072 2965142 2965500 2971203 2975719 2976627 2980654 2984006 2993100 2995004 2995388 2998174 3023562 3031432 Not needed: Code: 3040335 already superseded by 3046049 3035131 already superseded by 3032331-v2 3030039 already superseded by 3022776-v3 3027123-v2 included in 3022776-v3 3024252 already superseded by 3029803 3023878-v2 same as 3039066 3023869-v4-x86 included in 3022776-v3 3023555-v2 already superseded by 3022776-v3 server only hotfixes: 3038024 3036614 3035025 3033918 3033917 3016407 3004070
KB2961072 is listed under Removed / WU.Satisfy. However, it was not automatically removed by "dism /online /Cleanup-Image /StartComponentCleanup", so I manually removed it. After a Windows Update check on a Windows 8.1 Pro x86 system, KB2961072 is listed. So, in some cases KB2961072 is still needed by WU.Satisfy. Checking the Microsoft Update Catalog, KB2961072 is not indicated as being replaced.
KB2961072 is already integrated by Microsoft in latest ISO and in my opinion i don't think there's any point in manually removing it aboddi, are you sure KB2962409 it's still needed? on a fresh install of the latest iso, the only rollup WU asks for, is the december one, besides the already integrated april, july and november i also tested by applying RSAT package, and it asks only for these 4 rollups, april, july, november and december i assume they fixed WU since it no longer shows the old superseded updates and rollups, so i assume this means that KB2962409 (june rollup) is somehow superseded by november one and another new update ... unless WU is wrong with this again lol
According to this info: My questions are about Base updates: 1. Can I integrate KB2959977 (offline)? 2. What about KB3012199? This one too offline?
yes, both can be integrated offline 3012199 should be the first to integrate since it's the servicing stack 2959977 is part of april cumulative and can be integrated after servicing stack but doesn't really matter and from my own experience dism /cleanup-image /startcomponentcleanup doesn't remove it, but dism /cleanup-image /startcomponentcleanup /resetbase will remove it and then it will show up again in WU
The WU.Satisfy list is based on installing all updates in General, Security, Hotfix and NET35 did you install hotfix KB3033930? in my test on Pro x86 / ProWMC x64, KB2961072 no longer requested by WU
Yes regadless of WU, KB2962409 have components which are not found (replaced or included) in any other update as matter of fact, WU should not asks for july rollup KB2967917 because it's pretty included in november the only component that isn't included (VAN.dll.mui) has same binary version as april's 6.3.9600.17031, but it has higher assembly version 6.3.9600.17197 so it's sort of a Pseudo KB3000850 is now offered as Important update, not optional as before therefore the "replaced" updates cann't be offered as well
The Windowsupdate satisfaction (WU.Satisy) is a bit of a choice whether you want to install them and have more space used, or use Windowsupdate. If a newer update is already installed, but is provided through Windowsupdate, Windowsupdate will download an express cabinet. Express cabinets have the manifest files to satisfy Windowsupdate, but no binaries. This saves disk space. Windowsupdate can be a bit misleading as it can say it will download the whole update of say, 20 MB, where in fact it will only download a 100 KB express file. If Windowsupdate knows that you already have a newer update installed, you would think it would be smart enough not to offer the update at all, not require an express cabinet!
That's not accurate using WU or the complete package (msu) will give the same result (disk space) if the components binaries are already in WinSxS store (included in other updates), only the package manifests are copied but if they are not (the update is superseded like KB2959977 or KB2968599), the binaries will be downloaded/copied to WinSxS store
With all the updated and hotfixes, somehow I missed installing KB3033930. After installing KB3033930, update KB2961072 is no longer offered by Windows Update. I knew I missed something, thanks for helping.
I'm still required to install KB3023562 although abbodi1406 removed it from WU.Satisfy. What update superseeded KB3023562?
According to the ## Windows 8.1 Update (KB2919355) supplementary ## list and to really silence WU, is this the right install order?: 1. KB3012199 2. KB2959977 3. KB3000850 4. KB2934018 5. KB3003057 6. KB3014442 or 1. KB2959977 2. KB3012199 3. KB3000850 4. KB2934018 5. KB3003057 6. KB3014442 Besides, is there any 'hotfix' needed to satisfy WU? I already know there's no need of hotfixes for integration to satisfy WU but sometimes exist an exception to the rule.
Ah okay . Maybe this is something microsoft resolved in their store efficiency push? I'm sure it used to take up more space. It's good then that it doesn't!