Change the maximum run time of cumulative updates to 30 minutes
With the new 'cumulative updates' model I think it would be a good idea to change the maximum run time of cumulative updates to 30 minutes (or whatever is best suited). I have noticed more timeout issues with patching in the last couple of months due to the default 10 minutes not being enough time to install 'X' patches as a single CU. This would be preferred to manually overriding them every month.
This is improved for win10 cumulative updates on ConfigMgr 1706. If the update size is bigger at import time; we will set a larger timeout.
djam was kind enough to confirm that this truly only applies to Windows 10 via Twitter. I'm not sure if they can uncomplete an UV item so feel free to pile onto this item: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/20039980-set-maximum-run-time-on-cumulative-update-for-wind
+1 on the Server 2016 CU - we mainly patch Datacenters and this is a pain to have to manually change the timeout every month.
djam this was already confirmed for W10 updates, but it needs implemented for Server 2016 also - surely this idea should not be closed?
Brian MacLusky commented
Make sure this happens for server patches too. Lots of problems on our domain controllers running out of time during the past couple of months patching
What about Server 2016 updates? This is critical in a virtualised environment as they always fail.
30 minutes is not enough for a Azure VM Standard_A2_v2. It takes around 45 minutes to install a cumulative update on Windows Server 2016.
Stefan Röll commented
Has this already been implement? I can see for all Win10 CUs, that the max runtime is now 30 Minutes.
However, for Server 2016 CUs, it is still 10 Minutes
Iain Fairbairn commented
Also it should be noted that since it is a cumulative update, which changes KB ID and supersedes every month, the pain is that you have to go back and change the maximum run length time each time a new version is synced for each server OS otherwise you will find the same errors will crop up again in the future..
Martin McManus commented
Now that we have more 2016 servers, admins have been complaining that patches my team distributes with SCCM are failing because the run time is only 5 minutes. I can see the run time for Windows 10 has been increased, but why not server 2016? In the meantime I'll use a script to update the run time to 30 min for cumulative server 2016 patches until I see them sync with a longer time.
This is an issue amidst all of the changes that have been made to Software Updates and it's really making things difficult.
Steven Cera commented
Agreed, We are seeing an increasing number of timeout failures. I've had to manually increase the timeout period for some of the cumulative updates, for example, this month with KB4019472 for Windows Server 2016 because we were seeing timeout failures on about 20% of our systems.
Microsoft please consider, at least for larger cumulative updates, increasing the timeout value to 20 or 30 minutes.
Bruno Boux commented
When you try to install patches, for example this critical security update.
Windows10.0-KB3205386-x64 with a size of 1.03 GB.
The installation fails recurringly with a timeout error. (0X87D0070C)
The root cause is the maximum runtime is a default value in metadata.
this value is set to 10 minutes.
Microsoft changed his method of deployment for patchs for Windows 7 Windows 8 and Windows 10
All patches are now bundled in a single update .
If you don't go into each patches to change the default value you'all going to receive the same error .
May be Microsoft can be change the default value of metadata, or may be add a feature to autorise administrators to define the value by default .
I can see this change for Windows 10 allowing 30mins, however Server 2016 Cumulative updates still are defaulting to 10mins.
Nuno Silva commented
I vote on that as well...at least for this type of updates. Microsoft please test it on your labs are check if they are installed before 10m...
This seems to have been implemented ... at least for the cumulative Windows 10 updates in 1602. However, even that doesn't seem to be enough and I'm still seeing timeouts.
Looking at the new servicing model it only makes sense to have the runtime bumped up to 30 minutes.