Windows 7 Hotfix repository

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.

 

It updates Samlib.dll Samsrv.dll to 6.1.7601.18377_22579 and also superseeds KB2844009

 

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...

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

abbodi, KB2844009 superseded by KB2923392?

Thanks

 

Yes

thanks to DJAlik for pointing.

 

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

 

KB2918550 fwpkclnt.sys, netio.sys, tcpip.sys 6.1.7601.22590

 

KB2847346 nsi.dll, nsiproxy.sys, nsisvc.dll, winnsi.dll 6.1.7601.22590

 

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.

 

no hotfix superseded?

Thanks

 

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

 

You need to login to view this posts content.

 

I sure had WU offer a lot of updates after using the latest batch of updates (x64). I had 20 important updates and like 25 optional ones (this is in a VM). We don't do WU Satisfy but it seemed a bit disconcerting to see how many there are being offered. But when I looked closer at all the updates offered, I realized the majority that WU offered were actually present in the current batch of updates, but had not applied according to WU; this is because I installed them with LDR>GDR script. So in fact, the only updates offered by WU that were not part of the current batch of updates are:

Spoiler

Code:

important:

2446710 (and 3 other .NET 3.5.1 updates I couldn't make out in my screenshots)
2610339
2667402
2676562
2813347
2862966
2868725
2798162
2904266

optional:

2858725
(2 kernel-mode & driver mode Framework 1.11 updates, not sure about kb numbers)
2545698
2547666
2574819
2592687
2761217
2830477

 

You need to login to view this posts content.

 

.cab support maybe? What are the filenames for the .cab files? If you have service pack 1 installed, there are only 4 update since so this shouldn't be an issue.

I'm trying to get people away from using the .msp's, since the filenames are the same regardless of whether it's Office 2010 or 2013, x86 or x64. It's common people try and use the installer on the wrong .msp's. If I didn't have it as silent install, people would be aware, but it would also mean a lot of popup install windows etc. Furthermore, even on the correct Windows there may be some updates not applicable to their system, so having them show and error boxes appear would confuse people (and take away from the automation). This is particularly true for language .msp's etc.

The .msp extraction for the old repository was actually my idea , but at the time it was suitable for the old repository type. The new repository type and method it really isn't required.

 

You need to login to view this posts content.