Deploy Update 1 (KB2919355) to Windows 8.1 and Windows Server 2012 R2: Smooth Sailing Style
At a customer the other day they said that they had some problems on a handful of servers while deploying a particular patch. While looking into it I could see that the troublesome patch were KB2919355 more known as Update 1 to Windows 6.3 aka Windows 8.1 and Server 2012 R2.
The reason the patch didn’t install was of error code 0x87D0070C which translates into “installation exceeded maximum allowed run time”. When Configuration Manager installed patches, each patch is allowed, by default, 10 minutes to install. This is a security feature so that a faulty patch wouldn’t hang the system for all eternity. This particular update just as any service pack or like wise is quite large and takes some time to install. For most of my customers servers 10 minutes just enough so that it got installed but on this handful of VMs the performance wasn’t enough and they got this error.
The fix is to increase the maximum allowed run time for the particular patch in the Software Library workspace under the Software Updates node.
For us, 12 minutes was enough for all VMs to complete the installation but we went with 30 minutes just to be on the safe side. It is however important to remember that ConfigMgr calculates if it has time to install the update based on how much time that is left of the Maintenance Window when ConfigMgr is about to start with each and every update. So by increasing the maximum run time to 30 minutes requires that each agent that is about to install this update must have at least 35 minutes (left of) a maintenance window in order to start installing it. The extra five minutes is added by ConfigMgr in order to have some buffer time to complete a reboot that might be required.