Not sure if it is something that may be should be added to the check:
powershell -executionpolicy bypass -noprofile -command "& {$query=gwmi -class CCM_CITask -namespace root\ccm\citasks -Filter "TaskState='Failure'"; $query| rwmi}"
I had some clients which did not want to install any software. After searching for a while I found broken entries in the CCM_CITask, which can be filtered and removed. Finally the client go the missing software after a year
Source: https://support.microsoft.com/en-us/topic/fix-application-installation-fails-post-upgrade-of-the-configuration-manager-client-from-version-1606-to-version-1610-or-1702-3e413ceb-7cc8-72bd-78ac-a9c699bc891f
Not sure if it is something that may be should be added to the check:
powershell -executionpolicy bypass -noprofile -command "& {$query=gwmi -class CCM_CITask -namespace root\ccm\citasks -Filter "TaskState='Failure'"; $query| rwmi}"I had some clients which did not want to install any software. After searching for a while I found broken entries in the CCM_CITask, which can be filtered and removed. Finally the client go the missing software after a year
Source: https://support.microsoft.com/en-us/topic/fix-application-installation-fails-post-upgrade-of-the-configuration-manager-client-from-version-1606-to-version-1610-or-1702-3e413ceb-7cc8-72bd-78ac-a9c699bc891f