March, 2017 Security Monthly Quality Rollup for Windows Server – Fails to install with Configuration Manager 2012 R2 SP1

I had a customer report an issue this week trying to install MS17-006 on all 2012 R2 and 2008 R2 servers in their environment.

The WUAHandler.log file produced an error:

“User cancelled the installation”

The update then showed it had failed to install.

The maximum runtime limit set in this update was only 5 minutes

 

Changed this value to 30 minutes to be on the safe side, gave it time to marinade (just like everything with SCCM) and it installed.

Please note, the time you set here will impact the calculations of Maintenance Windows, so if you have a few updates to get through in a small amount of time be cautious and always pilot the deployment changes.

 

11 Replies to “March, 2017 Security Monthly Quality Rollup for Windows Server – Fails to install with Configuration Manager 2012 R2 SP1”

  1. Hi Greg, would like to try your fix and increase the time limit, unfortunately I do not know how you got that screen up in order to navigate to the “Maximum Runtime Tab” and set the Time from 5 minutes to 30 minutes.

    Have allot of experience in IT, just have never done this before…what command and/or set of menu options will get me to that screen for a specific Microsoft Windows Update?

    Thanks.

  2. Hi Craig, Just navigate to the update found under Software Library > Software Updates > All Updates. Once you have selected the update, right click and select properties. You will see a maximum runtime tab, choose that and change the maximum run time minutes. Hope this helps.

    Cheers,
    Shon.

Leave a Reply