System Center Configuration Manager Feedback

How can we improve Configuration Manager?

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.

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..

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.

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.

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 .