You would have in case of IE11. KB2976627 package for IE10 is different and doesn't even contain inetres.adml for multiple languages so only in case of using IE11 on non-English Windows 7 KB2976627 is needed along with KB3003057
WHDownloader 2014/12/10: Spoiler Added: Code: 2952664-v7 3004394 3006121 3006625 3008923 / IE 3009736 3012176 / IE8 3013126 3013410 3014406 2535094 2965917-v2 2974005 2999802 3001267 3006112 3006139 3008558 3009197-x86 3009350 3009621 3012696 3013102 / Features\SUA 3014300 3014793 3015999 3016350-v3 3016375 Superseded: Code: 2920188-v7-x86 (by 3009197-x86) 2641634-x64 (by 3009621) 2743155-v2 (by 3013126) / WithoutPlatform 2799603-x86 (by 3009621) 2831206-v2 (by 3015999) 2870437 (by 3014406) 2885209-v2 (by 2535094) 2887519 (by 3013102) / Features\SUA 2906850 (by 3001267+3012696) 2909210 (by 3012176) / IE8 2929755 (by 3013126) 2939576 (by 3009350+2993958) 2957509 (by 3006112) 2974313 (by 3006625) 2974617 (by 3014793) 2978668 (by 3008558) 2979933 (by 2965917-v2) 2996534 (by 2999802) 3001232 (by 3012696) 3003057 (by 3008923) / IE 3004543 (by 3016375) 3011843 (by 3013410) Note: IE11 2976627 is superseded by 3008923, but i kept it since WU now ask for it when it was required it didn't ask for, and now when it's superseded it does, unbelievable
Hello If I never use WU, I have to install it I ask because when I uninstall several updated simultaneously During the reboot, it is "blocked" on it View attachment 32557 I have to turn off "manually" Thanks
looks like MS pulled two updates: KB3011970 (Silverlight Update) KB3004394 (Root Certificate Update) -andy-
Hmm, KB3004394 may indeed have caused problems. I read some stuff about people having trouble with this update and checked my VM install from last night were I installed all WHD updates via batch script (live in VM, for sysprep) and was astounded to find over a 100 updates still being offered on WU. This morning I read about KB3004394 and problems with installing updates after installing that update, so I looked at my installed updates on the vm and it appears almost no updates in the KB300xxxx range were installed (after KB3004394) so I think it is botched and can prevent other updates from installing. Someone mentioned this update prevented them from installing subsequent updates. Sigh MS... Also, a VirtualBox issue was reported after installing that update. VB is really annoying the last releases (since 4.3.12) because it started to check for file signatures, etc., so if you have uxtheme files or other dll's patched, the vm's fail to load. So I'm still using 4.3.12 because even latest .20 release still has these issues. So makes sense the root certificate update KB3004394 is causing this issue for VB since it check such things in the OS now. Will report back if I find out anymore about this update and how it impacts installation of updates. EDIT: No, my script is what caused the KB3* updates not to install... (it had kb2* mentioned in there...)
The GDR branch in KB3004394 (except crypt32.dll) is exactly the same as in the withdrawn update KB2949927 whereas the LDR got updated, maybe that's why i don't have any issues i guess that's the beauty of LDR branch, i hardly faced errors in updates == added new hotfix 3015692
Thanks for mentioning, abbodi. Could you direct me to a good/current ldr install script, please? I was using the older one but it was scripted to only install up to kb2*. I edited it to also install the kb3* updates but it didn't seem to work. EDIT: OK, the script edits I performed did work, it was just that the test I did afterwards of double-clicking to install some kb3* updates happened to be several updates that could still be installed, even though they were already listed as installed. This would be the same thing as updates getting offered on WU, even though there were installed already (WU satisfy). So that confounded me for a moment but it's OK. I had another question. Among IE11 updates, I was under the impression they were cumulative updates, so why do we currently require 2 of these (KB2976627 & KB3008923)?
Does anyone know what's up with the mysterious update KB3024777? It's 29KB, cannot be unchecked or denied as it is of grey color. MS site for that update says 'Oops'. Something's fishy. Edit: Analyzed it a bit, in the code is Code: dism.exe /online /remove-package /packagename: and the packagename for KB3004394. Looks like its only use is to uninstall the botched KB3004394 update. Interesting. Cool: Internal name is 'FixBrokenUpdate.exe'. Sounds they'll really need it in the future.
After the release of Windows 8.1 update, which current IE11 updates follow, updates varies, sometimes it's fully cumulative and sometimes it's partially cumulative as for the current KB2976627, it's fully superseded by KB3008923 however, WU still asks for it, so i left it.
Is the update KB3024777 purely an undoing of 3004394, or does it fix the issues with 3004394 but still update the 'Windows Root Certificate Program'? I'm thinking the former, because I read that people don't get 3024777 offered on WU when they uninstall 3004394.