Had this recently on a machine we were upgrading to Win 10 1909. Initially it looked as though there was an issue detecting the application being installed correctly but on closer inspection, the AppDiscovery log file revealed that the same timeout issue was happening on several applications. Googling about there were quite a few posts on how later versions on ConfigMgr now incorporated a client property to change the script timeout setting but this sadly appeared not to be the case. Other posts suggested a script that could be run at server level to fix this. Not really the short-term fix I needed to sort my issue as it would doubtless take weeks to get the change through at work.
Then I found what I needed – a client-side script which I have now lost the source to, so really sorry if this came from you. I’m happy to set the record straight and link as needed. In any case, I do have the script itself, see below. This wil set the timeout to 1200 seconds (from the 60s default). This fixed my issue. I would imagine this could be added to the start of a task sequence if required. Note it’s a VBScript…old skool.
On Error Resume Next strQuery = "SELECT * FROM CCM_ConfigurationManagementClientConfig" Set objWMIService = GetObject("winmgmts:\\" & "." & "\ROOT\ccm\Policy\Machine\ActualConfig") Set colItems = objWMIService.ExecQuery(strQuery, "WQL") For Each objItem in colItems objItem.ScriptExecutionTimeOut=1200 objItem.put_() Next Set objWMIService = GetObject("winmgmts:\\" & "." & "\ROOT\ccm\Policy\Machine\ActualConfig") Set colItems = objWMIService.ExecQuery(strQuery, "WQL") For Each objItem in colItems If 1200 = objItem.ScriptExecutionTimeOut Then WScript.Echo "True" Else WScript.Echo "False" End if Next