Link to home
Start Free TrialLog in
Avatar of Jay Schwegler
Jay SchweglerFlag for United States of America

asked on

Server 2016 Pending Update Behavior

I have a question concerning a slight annoyance with Windows updates in 2012 vs. 2016 Server

I have my servers set to download the updates, but not apply them. This obviously saves me the download time and I can apply them quicker during maintenance periods.

In 2012, if either more updates are released or something is revised, Windows Update re-downloads the changes during it's normal polling cycle and everything is current when it's time to install them.

Under Server 2016, it will appear to download whatever updates are available at that time and then wait with the Install now button. If something newer is released after that, it doesn't appear to re-scan until the currently downloaded updates are installed (even if they are out of date).

In that situation, is there a way to force Windows Update to re-evaluate the available updates like Server 2012 does?
Avatar of Sean Bravener
Sean Bravener

there are a few ways.  the best however is to use command line.  f
from an elevated command prompt (or powershell)
You have to use usoclient StartScan to start a scan.

There are other options as well:

StartScan: Used to start scan
StartDownload: Used to start download of patches
StartInstall: Used to install downloaded patches
RefreshSettings: Refresh settings if any changes were made
StartInteractiveScan: May ask for user input and/or open dialogues to show progress or report errors
RestartDevice: Restart device to finish installation of updates
ScanInstallWait: Combined scan, download, and install
ResumeUpdate: Resume update installation on boot
Avatar of Jay Schwegler

ASKER

Yes, I had tried that, and it does do the re-scan, but it ends up at the same place with the older patch waiting for installation.
ASKER CERTIFIED SOLUTION
Avatar of Sean Bravener
Sean Bravener

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes, I was seeing if there was an alternative to blowing away the Windows Update Database, but it looks like that is the only real way to accomplish this. Thanks.