Thanks komm. Just to summarize: KUC says 20 or so updates for optional Windows components (IIS, NFS, MSMQ, etc) are missing and should be installed even when those Windows components are not installed. The updates won't apply if those Windows components are not installed. You do have descriptions for many updates already. But only the KB # is listed for those 20 updates, so the user needs to look up those KB's to discover they're actually not applicable. My suggestion was to add a description to those 20 updates saying they're for optional components and might not be applicable in all cases, so users wouldn't need to look them up. This is not a big deal It's a convenience issue. But since a majority of KUC's users probably won't have those Windows components installed, the suggestion may benefit others as well. I'll send you the packages.txt and a list of the 20 updates.
want to say the following is missing:KB2556532,KB2545968,KB2534366,KB2498472,KB974405,KB969168,KB943790 These are publicly available from Microsoft website.
found one more missing KB2607047 and KB974405,KB969168,KB943790 are not missing, my mistake So the updates I found to be missing are:KB2556532,KB2545968,KB2534366,KB2498472,KB2607047
If they are missing, they have most likely been replaced by more recent hotfixes. I.e. KB2556532 was replaced by KB2532445-v2 KB2534366 was replaced by KB2532445-v2
Why replace KB2556532 with that? KB2556532 is a security update. And KB2556532 is about "You can circumvent AppLocker rules by using an Office macro on a computer that is running Windows 7 or Windows Server 2008 R2" support.microsoft.com/kb/2532445 And after I have installed KB2532445-v2 I can still install KB2534366.
If all you care about are security updates, this is the wrong topic for you BTW any superseding hotfix will have the same security fixes as the security update it replaces...and just because you can install it does not mean the files are actually used
On a KB article basis, no updates really supersedes another update unless it is a later version of the same update (denoted by -v2, -v3 etc). We look beyond that to a file level. Later versions of the same file includes all previous changes to that file, including those belonging to other KB articles. These changes may have absolutely nothing to do with the KB article belonging to the newer update. To confuse the situation more, a GDR version of an update, if present, only includes previous security and mainstream release changes of that file. In this case a newer GDR file may not necessarily supersede an older one, so you are partially correct there. The difference comes with the LDR version of the updates, which exist if there is a previous KB article or other change relating to those files. LDR files are cumulative, so include all previous security updates and changes relating to all previous KB articles affecting that file. The repository is about having the latest LDR files (or GDR files if GDR release only), so the kb article relating to that specific update doesn't reflect all the other changes to those files. If not all files are updates in a new update, the old update is kept just to keep those newer files that exist in the older update. I hope that makes sense its all about having the latest level of updateness!
Integration is okay. All the updates integrated show as install pending in the KUC list. It's all of the other lines that don't make sense to me. For example (condensed format): Code: Install Pending Hotfix 1/2/2012 12:35 AM 2276594 Windows6.1-KB2276594-x86.msu OK Hotfix BF_2276594 Windows6.1-KB2276594-x86.msu ADD Update is missing!
These updates do install, if you use SoLoRs update.cmd installer. KUC checks only the packages that are installed. It did not check if a feature is enabled. For additions that's no problem, they are listed in the /get-packages output. So the next version of KUC will not add an Addition Update if you don't have installed that addition. Normaly you want a windows that is prepared for all situations. Let's say you don't have blue-tooth on you (1-2 year old) Desktop PC. You would not think about not installing blue-tooth updates 2509318 or 2532531. They are not necessary on your desktop, but you install them. Then, when you ever add a blue-tooth adapter, you are prepared. Let's say you want to run you "old" Win7 installation in a Hyper-V vm [Win2008R2 or Win8]. No problem you have installed all the necessary windows updates already. You want to run a IIS application on your computer, if you don't have installed all IIS update .... But PointZero is right. Normal users don't need IIS, NFS, SUA... The best way would be, if the KUC also would check the /get-features output. So KUC could check, if a special feature update is needed. But that's in the fare future. The next version of KUC will flag the first part (IIS and ..) of those updates, so the user can decide if he wants it or not. (Surely it not a way to make the use of KUC easier).
I knew those updates wouldn't install manually, but I didn't know that SoLoR's script would install them. Thanks for the info. Yes, that's true in many cases, but for my personal system, I only install the bare minimum of things that I'll actually use. I try to keep the system as lean as possible. Also, I may be overly-cautious (and probably wrong) but I consider having things like IIS installed in a non-server environment as an unnecessary security risk since it could be a potential entry-point to a system. But again, my main goal is to keep things as lean as possible. Thank you very much komm. As I mentioned to you earlier, your approach is much more elegant than my suggestion of just adding the descriptions since users will now be able to choose whether or not to check for those updates (so they avoid those missing updates being listed in the first place). There may be more options in the program to choose from, but the output will be easier to manage. Thanks again.
SoLoR's script will install them because it looks into the subfolders. Only a few of the updates are installable on normal systems, most of them aren't applicable. I would suggest copying those that are applicable into the folder with the rest of your updates. You can find which are applicable by running them and seeing whether it asks you to install then move them over... I would tell you but still away on holidays! I'm not sure whether those that are installable only work on certain versions of Windows 7, like Ultimate, or all of them. If they are installable on all Windows it would probably be good for them to be part of the main folder. The idea of the subfolders is that the updates may not be applicable, but if they are, makes sense to move them... If someone could find that out maybe the suggestion could be made to SoLoR. It doesn't harm trying to install updates that aren't applicable, but it does mean wasted time during installation.
burf- yes, SoLoR's script initially surprised me since it installed from subfolders (yours didn't) and I didn't want those other additions installed. My point to komm earlier was that I didn't think some of them (like IIS) would actually apply since the Windows features weren't turned on beforehand. As you said, it would be good to figure out which apply with default features on/off and if they'd apply to all vers of Windows. Thank you for the good info. Enjoy the rest of your holiday.
Check my sig guys I updated the transforms for .net4 and vc2k8 WU fix (minor updates). Everything you need to slim and satisfy Windows Update when it comes to .net4, vc++ 2k8+10 and fsharp2 you will find in this folder