I'd like to leave Windows Automatic Updates enabled but block a specific patch from being installed that is causing us problems.
Is this possible? Anyone know how to do that?
I'd like to leave Windows Automatic Updates enabled but block a specific patch from being installed that is causing us problems.
Is this possible? Anyone know how to do that?
In a larger network you will want to use WSUS as DanBig pointed out. However, if you owant to block an individual hot fix you can do so with the hot fix ID using this script:
If the update is not linked to an KB article then you would need to find the update ID using this script:
And block it using this script:
You can do all of the above in Windows PowerShell as well. I created the scripts in VBScript originally because I wanted to interact with the Windows Update Agent before PoSH was installed. The Windows Update API is documented on MSDN.
If you are using WSUS, you can decline an update. I don't know of a way to do it otherwise.
Within the Windows Update application (on Vista and 7), right-click the update you want to block and select "Hide Update". This will remove it from the list and block installing it during automatic installation. You can "restore" the hidden update any time in the future so it will appear back on the list.
There is a similar process on the older style Windows Update web site (for Windows XP) where you can hide an update. The option to do so is in different place though.
I recommend a one-line change to the Colin's scripts. I'm not certain exactly why, but I find I am seeing the wrong KB number unless I use a search like:
If I only specify IsInstalled=0, I sometimes get a different KB number.
For instance: KB2956078 is ready to install on my machine. If I specify both conditions to Search(), I see:
However, with only the "IsInstalled=0" conditional, I see:
Looking at Windows Update, I see that KB2956078 is the update that is being displayed. Also, I am setting that update to hidden, and that works correctly and hides the update with the change I am proposing.
Minor update: I may have figured out why this is happening. I've been suppressing certain Outlook updates that break Outlook scripting. The two updates in question have very similar titles, and it looks as though Windows Update gets confused.