Note that this applies to windows updates in general and i only describe my own situation below with a specific OS; i am sure this issue is much the same regardless of the OS. Hi everyone: I am at present working on a somewhat automated batch script for installing Windows updates and as I was running this to prepare a VM for release, I ran into something interesting as follows; 1) while checking for updates (using Legacy Update) apparently installing .net framework 2.0, 3.0, and 3.5 also wants to install updates for .net 1.1 for some strange reason? 2) even when installing all .net 2.0 updates, one got missed 3) there’s an update that deals with “revoked certificates” what won’t run with the /Q option even though it will run just by double-clicking it (when running the update with /? It says that /Q is supported) my questions are: 1) what order do updates go in (if there even is a “correct” order) 2) how do I know which updates are for a product only after another is installed? (E.g. what net framework 1.1 updates only apply if net framework 2.0 is installed) that way I can correctly organize the updates and thus install them in the right order 3) what is going wrong with that one update?.
I applaud you for setting up your own batch script. You'll probably want to provide a little more info as to what OS and updates you're specifically trying to install. Some general notes, Microsoft messes up all the time. I've seen issues regarding the downloads MS provides being different from one another. I was looking at updates for the Office viewers for XP and found that, for one of the updates, that I HAD to get it from the 'cabpool' (download.windowsupdate.com) vs the regular download (download.microsoft.com) because, if I DID NOT, it the Windows Update site would keep whining for it even though it was shown as installed on my PC. Also, with regard to Dotnet installers/updates, those things can be extremely flaky, I often have to try two or three times before they'll complete. I'd suggest making sure you check ERRORLEVEL returns in your script. A good 'starting point' would probably be to try to do them in chronological order (by release date), assuming you can gather that info. It may take several tries to get it 'right'. If at all possible, setting up a VM and getting the OS to the point where you're ready to install the updates in question could be extremely helpfully, obviously. Hopefully, if you provide details, someone else can tell you exactly what needs done.