(as posted in the Windows 8.1 repository thread) WHD repo Office 2013 2013/03/12 KB2863911 (Outlook 2013) KB2863908 (Lync 2013) Service Pack 1 for Office 2013 should be installed before installing these updates. If not already installed, it can be downloaded via the SP1 links for Office 2013 in WHD.
Added: Spoiler Code: 2903025 2916266-v3 / Without Platform 2923884 2925489-v3 2936589 / IE8 Removed: Spoiler Code: 2862152 (by 2925489-v3) 2862966 (by 2868626 + 2903025) 2916266 (by 2916266-v3)
Wow, I hadn't really used the Windows Hotfix Downloader and the new system in-depth yet, but it is great! All the functions (like Superseded remover, checking against existing lists, etc.) are really well done. Thanks to the team (Abbodi, PointZero, Alphawaves, and everyone involved) for this great tool.
For Office 2013 please note I just amended the list update I did several hours ago and added back a pre-SP1 Lync update. This update will show in Windowsupdate even after a fresh install (including proper Office 2013 SP1 ISO), and the files contained within it were not included in SP1. It appears Microsoft accidentally left out this update.
Isn't IE 11.0.4 out for Windows 7 too now? I saw some links but I think they all say "Enhanced with Bing & MSN" so I didn't know if there will be another version without enhancements or if there was even a new IE 11 out at all for purposes of integration into images. EDIT: abbodi, I had a question for you. Somewhere in this thread you mentioned something about NativeImages. Do you know if NativeImages can be deleted or reset or something in Windows 7? The reason I ask is, when you use sysprep to capture images from a VM, because the Windows 7 installation runs live, ngen generating makes the NativeImages folders increase in size. What I was wondering if there is a way to reset/delete those before applying sysprep, so that the folders reduce in size so that the install.wim will be smaller. I can't find any definitive information on this. But I thought the NativeImages generation is a per-system thing, but I could be wrong. Anyway, the longer you let a VM install run live, the greater the chance the NativeImages folders swell in size (for example in Windows\assembly\NativeImages_v2.0.50727_64). It can swell 200mb in size that way (without installing any updates). But if you install Win7 in a VM and immediately perform sysprep, the NativeImages don't have time to increase in size, and thus the resulting iso sizes are smaller. It just doesn't seem to make any sense how this works, but perhaps someone has some insight in this. Thanks...
Thanks for the tips regarding the Native Images. I tried some commands to uninstall, delete, etc., the native images but no luck. It is probably not a very fruitful thing to mess with that anyway, but I was trying to capture a base image (iso) to use for updated iso's but found my Win7 x64 image was almost 100mb larger than the previous base image I had been using. And when I compared install.wim sizes via 7-Zip, it became apparent the assembly folder (NativeImages specifically) had grown larger. I thought there might be a way to force re-generation of the NativeImages, just like it seems to do after an install, without causing any problems down the road. But I can't seem to reset/force regeneration that way so I'll probably have to live with it
BTW, abbodi, Ricktendo, etc. Strangest thing, I was on a forum (WinReducer) and someone just mentioned he always deletes the NativeImages as these are automatically regenerated when installing .NET 4 (and he linked to the slim version by Ricktendo as a matter of course). So it appears those folders can be removed as Windows can re-generate them. For now I'll try it out of curiosity, but if it turns out to be something without negatives I may use that method for images.
KB2918550 (6.1.7601.22590) supersedes KB2920289 (6.1.7601.22553) KB2847346 (6.1.7601.22590) supersedes KB2588507 (6.1.7601.22009) which was x64 only, no x86 version