...
WuInstall /search /severity CI
Tip: The severity is only filled for security updates, so it is not really suitable for finding high priority updates as security updates usually ARE high prioritoy updates. Classification is better for that purpose. |
2.6. Classification
Each update belongs to one of those classifications:
...
WuInstall /search /classification SCU
Tip: High priority updates can best be found with the classification CRS (Critical, Security and Update Rollups), however sometimes also U (Updates) can be high priority. Generally speaking, selecting which updates are high priority and which are not is up to the administrator, there is no general rule how to automatically match the high priority categorization on the microsoft update website |
2.7. Product
...
For example, find all Updates for Visual Studio 2008:
Tip: The product name has to match exactly, so just specifying "Visual Studio" here would produce no results. |
WuInstall /search /product "Visual Studio 2008"
Tip: All update selection options (/match /nomatch /matchfile /nomatchfile /severity /classification /product) can be used in combination with each other! |
3. Additional options
...
WuInstall /install /reboot
Tip: The /reboot option reboots the system after executing WuInstall unconditionally after the specified number of seconds. The result of WuInstall has no influence whether if there is a reboot or not. |
3.2. Rebootcycle
With this option complete cumulative updating of windows systems becomes possible. That means installing updates, rebooting and installing further updates will be automated. After performing an update and rebooting afterwards, WuInstall starts again before the Windows Logon and executes the same command again, which was done before the reboot. The /rebootcycle option uses the Windows Task Scheduler to restart WuInstall.
Tip: You can limit this rebootcycle option to a maximum number of reboots to prevent of getting stuck in an endless loop. Default is 3. |
The /rebootcycle option works together with /reboot or /reboot_if_needed.
When the /rebootcycle is used WuInstall outputs in the console:
| Code Block | ||||
|---|---|---|---|---|
| ||||
/rebootcycle is specified, going to run this wuinstall command at most x times again at startup if reboot is triggered |
Example usage:
wuInstall /install /logfile_append c:\loginst.txt /reboot_if_needed /rebootcycle 2This command installs all available software updates. If necessary the system will reboot after an update installation and WuInstall will execute the command until all pending available updates are installed. In this case the numbers of reboots is limited to a maximum of 2 in any case. Also the /logfile_append option is set to have a report about the whole installation process including all reboots.
3.3. Rebootcycles and shutdown when finished
As already mentioned the /rebootcycle option automates reboots inbetween of updates. In many cases it might be necessary to shutdown the machine after having all updates done. For example if you want to schedule your windows updates during the night.
Example usage, which installs all available updates and shuts down the system when finished:
WuInstall /install /rebootcycle /shutdown3.4. Bypassing the WSUS
If you have a WSUS, but want to go for the Windows Update Site instead of WSUS for some reason, you can use the option /bypass_wsus to bypass the WSUS server for the time WuInstall is executed.
For example, bypass wsus and install update KB956844 from the Windows Update Site:
WuInstall /install /bypass_wsus /match "KB956844"After execution of WuInstall, WSUS is re-activated for your system. This option automatically executes the Sc stop wuauserv and Sc start wuauserv commands in order for the bypass to take effect.
Tip: If WuInstall fails for some reason or is aborted before it finishes, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU, Value UseWuServer is still set to 0. You have to set it to 1 manually, in order to tell your system to use WSUS again. |
3.5. Selecting another WSUS
Quite the opposite of the bypass_wsus option is the /use_wsus option. If you want to choose another WSUS or if you have no WSUS configured at the machine and want to get updates from a certain WSUS, the use_wsus option can force WuInstall to use a certain WSUS
For example, install your updates from the server wsus2 instead of wsus1:
WuInstall /install /use_wsus http://wsus2
WuInstall writes something like this:
You are using WSUS Server http://wsus1
use_wsus specified .... WUServer and WUStatusServer successfully set to http://wsus2
After execution of WuInstall, the initial state is restored (e.g. wsus1 is re-activated or WSUS is switched off again if it was off)
use_wsus specified, reactivating WUServer http://wsus1, WUStatusServer http://wsus1 ... successful!Tip: If WuInstall fails for some reason or is aborted before it finishes, the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWuServer, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUStatusServer have to be reset manually to the initial state |
3.6. Accepting EULAs
Some updates require the user to accept an EULA in order to install. To automate this, the /autoaccepteula option automatically accepts all EULAs for updates which require this, without any user interaction or interruption.
Example:
WuInstall /install /autoaccepteula