You haven't hosed your system, just the opposite. The installer can install any combination of updates, and its not a requirement that you install all updates. Installing all updates is only a requirement if you use the superseded update remover. The updates show in Windowsupdate because Windowsupdate requires that both GDR and LDR versions these files are installed. You can either download them through Windowsupdate or download them manually and run the script over them again with the 'install all updates' (option 1). The script has a list of updates internally that is used to know whether both versions (GDR and LDR) need to be installed or not. If they were already installed it's strange that they should be showing, even if you run the superseded uninstaller without all the latest updates installed. What do you mean by '(without restarting!) to remove updates that were no longer required', as that is not a function of the script. The only function that comes close to that in the installer is the removal of non applicable/non applyable updates, which only removes .msu/.cab update files, and not active files on the system. If an update isn't applicable/applyable, it's just that, 'not for your system', and as such is not needed on your system. kb947821-V24 is another possibility of a need to be run. With both the installer and the superseded uninstaller run properly, these shouldn't be showing (not sure if McRip has all the required updates to hide WU updates in most cases). I hope that wasn't too confusing, I didn't know how best to explain it! The showing of updates in Windowsupdate is actually a bit of an annoyance, as many are superseded and even when installed are completely non-functional, except for not showing in WU. The other annoyance is that for the updates which are still applicable, both the GDR and LDR (if present) versions need to be installed even if the LDR version is the only one needed.
Phew First let me clarify what I did (I may have led you astray a little): I have folder containing the msu files for updates I have installed (note that this is not the complete list from McRips repo, just ones I picked out). These were installed via a batch file that runs each with the "/quiet /norestart" flags. I downloaded the "Installer For Windows Updates V26f.cmd" tool and put into the folder. Running the tool I first chose option 'C' and then option '2'. The tool did it's thing (there were a few new ones). Then without rebooting I chose option '3' from the "Tools" menu to remove GDR versions. After this completed I rebooted. This is when WU started showing those extra updates that I know were already installed. Is it worth me running kb947821? I don't normally let WU install anything, I just check out what it has to say and then install what I want manually. I'm pretty fussy about what gets installed, and also I've been bitten many too times to allow WU do whatever it wants and I don't trust it.
Ah ok! I checked the superfluous GDR removal tool and it worked fine, it didn't process the updates in the wusatisfy exclusion list. The interesting thing is that you were able to run it after installing updates that most likely would have required a reboot. The tools becomes unavailable (until after the reboot) if there is a pending.xml file present in %windir%\winsxs (c:\windows\winsxs), which should be present if there were any updates or changes that require a reboot to be finalised. This suggests the updates didn't actually process properly with dism, a sign that something may be amiss. Possibilities are: - the script you use doesn't take into account WU satisfaction update requirements - you are running Windows 7 RTM and not SP1 - your system has a file system integrity issue. You can run sfc /scannow from an elevated command prompt to make sure this isn't an issue - you may actually have to run kb947821-v24 If the first item is true (most likely), to reinstate the GDR updates for WU satisfaction you can simply run my installer script with option 1. It will reprocess all updates in that folder and install any necessary components that aren't installed. Reprocessing updates is significantly quicker than the initial install, so it shouldn't take too long in this case.
I ran sfc /scannow and it gave me the all clear. I downloaded and ran kb947821-v24 and it had nothing to report either. I'll try option 1 and report back later. I'm on Win7 x64 sp1 by the way.
I don't think KB947821 actually reports anything even if it does rectify issues. I say it's most likely the original script you use didn't take into account WU updates.
Komm, Do I need the updates in OLD for BAD? I am applying updates on a fresh Windows 7 SP1. And which script do I choose to install all of the updates? And should I put all of them in one folder or leave them structured as the repository is?
You could use my script Actually there are a couple of different variations of script you can use, but if you are installing all the updates you want to make sure they use the LDR version of each update, as they include all previous changes to those files, including 'superseded updates'. In other words, they have a higher level of 'updatedness'. LDR versions, if present, have to be installed specifically. If you are installing all the updates, keep in mind that installing all of them at once will be so painfully slow in the end you need to leave ample time for it to process. The problem is DISM has to keep track of not only what's in the system, but by the changes of previous updates, meaning that the more updates you install, the slower the process gets. In my installer there is an option in the cab menu to 'autoreboot' and continue installing. You have to have UAC disabled for this, and it's best to use without the need to login so you don't have to sit there whilst it progresses. It will install around 50 updates, reboot automatically, and after reboot continue installing untill all updates are installed. If some of the updates aren't applicable the check mechanism in the installer will catch it so you aren't caught in an endless cycle. To use this, you have all the updates you desire to be installed in the same folder. Of course you can use other scripts, but just make sure they install LDR versions, and that you split the updates into say, groups of 50. DON'T try and install all of them in one go!
They are superseded. It seems they are for a specific purpose that you shouldn't encounter with a fresh install.
Burfadel, I used your script to install the updates and all things installed correctly.. Thank you for your great script and thanks to Komm for his great repository and Update Checker. View attachment 17066