^ KB2661227-v2 does not have Windows Presentation Foundation WPF-PenIMC which is contained in KB2651992-v3. Thus, KB2651992-v3 is not superseeded by KB2661227-v2.
New KUC is out there are also some updates: all superseded nothing 2691967 embedded 2665347 server Hyper-V 2673007 server 2673007 DVD x64 (winre.wim and boot.wim) 2675332 IE8 2665720 all systems but server core
I was just wandering what 2673007 DVD x64(winre.wim and boot.wim) is all about; by that I mean I was expecting wim files in the cab-integrate to installation media type thing-tried Google-nothing. Thanks for the update komm-as usual, very nice.
The very first time that this kind of software really works perfectly. Damn good work and a great progress. This software is now highly recommended! Thanks very much for the great work.
burfadel, Thank you VERY MUCH for your prompt and very useful reply!!! I used your script v25b. I did everything as you recommended except I didn't include updates for IIS, MSMQ, NFS, SNMP, 'Subsystem-for-UNIX-based-applications' to the main folder since i) I don't use them; ii) these Windows features are disabled by default after fresh install of W7SP1x64 (Ultimate). However, when I run the script (C -> option 3), the 1st pass (first 50 updates) goes OK and Windows restarts configuring the updates both on shutdown and before the system launch. On the 2nd pass, however, Windows returns with the following error message: Code: Failure configuring Windows updates. Reverting the changes... I tried 3 times - the same result! It takes a while until Windows reverts the changes and launches again. Then, the script continues to run and completes installation. My check of Event Viewer don't show any adverse impact of the failure - but I'm still unsure that everything goes as required. Can you pls advise what can be done to eliminate the failure problem? Thanks!!!
That is a result of an update not applying properly for some reason (its not the script, its an issue with the installation). You should be okay, as it no doubt installed properly after the reboot. The failure could be because you have a system integrity issue. Run the following command from the command prompt (takes a few minutes): sfc /scannow If that passes, try running KB947821-v20. Its actually a tool, and the script is set to skip it if present but does leave you the option to run it in the tools menu. It runs just like an update (takes some time though), and once both of these actions are completed the issue issue you encountered may be resolved...
The updates release on the second Tuesday of every month (this month the 10th), are mostly security or security related (like the Malicious Software Removal Tool). A lower number of updates just means there are fewer known security issues that have been resolved. The big lot of updates (hotfixes etc) that we have been seeing will probably come out within a couple of weeks (this is completely an assumption based on previous months).
heads up! installing one of these updates seriously messed up my installation, too many bsods Windows6.1-KB2545698-x64.msu Windows6.1-KB2639308-x64.msu Windows6.1-KB2651992-v3-x64.msu Windows6.1-KB2661227-v2-x64.msu Windows6.1-KB2665720-x64.msu Windows6.1-KB2668395-x64.msu Windows6.1-KB2674705-x64.msu Windows6.1-KB2674913-x64.msu had an image backup luckily.
I don't know what or how you did it. Everything is working pretty well without any Bluescreen or so. Even installed the updates on the productive machine...
Follow the updates as per the repository. Even if you hand pick the updates, make sure they're up to date! Windows6.1-KB2665720-x64.msu and Windows6.1-KB2639308-x64.msu are not current repository updates.
I used Komms update checker to download and install missing updates which included those 2... edit: googled a bit and i can confirm KB2639308 was the culprit.
Ah ok! actually I did make a mistake with that post. Windows6.1-KB2639308-x64.msu is required to satisfy WU. However, with all the other updates installed it should be inactive!... I believe the Komm's update checker may be listing Windows6.1-KB2665720-x64.msu also to satisfy Windowsupdate. The updates to satisfy Windowsupdate can be a little tricky, as it seems if you have update 'x' installed installed update 'y' doesn't show unless 'z' is partially superseded... in other words, its definitely not an exact science and in both Komm's and my case they're worked out by observation (at least, I believe that's how Komm does it too?). This list of these 'to satisfy WU' updates changes on each patch Tuesday. The update repository doesn't include these 'to satisfy WU' updates, and they serve no function when installed other than to not show up in Windowsupdate (as long as the latest updates are installed). In any case, since you used the KUC you should have all the latest updates installed, meaning KB2639308 should be 'inert' and cause no functional change to your system. Since it appears this isn't the case, either you don't have all the valid updates installed, or you have a local error on your system which is causing an anomaly with Windowsupdate. Try running sfc /scannow from the command prompt. Once complete if need be, restart, and run KB947821-v20, otherwise run KB947821-v20 immediately upon completion. This should resolve any issues if present that could cause the discrepancies with installing the updates. What method did you use to install the updates?