Several months ago, I was tasked with finding as many causes for Patch Scan Failures. Well, the status messages coming back from the Scan are great in reporting the scan engine failure codes, but determining what to do about some of them was not fun; a lot of trial and error, a lot of research. And there are still several errors codes for which I don't know the fix, or the fix I've tried is questionable.
Nevertheless, to hopefully save some of you from the same research, attached is a .zip file, which contains a report mof file, which you would import into classic reporting (right-click on Reporting in your console, import). If you use SRS, grab the sql once imported. You’ll need to modify the report code to reflect your environment’s UpdateSource_UniqueID:
in your sql, run this to get your correct uniqueID:
Select UpdateSource_UniqueID From v_SoftwareUpdateSource
One report is simply a summary of all of the counts of the types of errors that have been reported in your environment from your clients (see screen shot below).
If you wish, you could link report #1 to the 2nd report, using the error. The 2nd report will give you which computers reported that error during scan.
Hopefully, some of the error explanations, and the fixes I found outlined in the ( ) will help you find and fix patch scan failures!
fyi, just in case someone thinks "that's a lot of failures"... this report comes from a large environment. Those failures represent 0.3%; in other words, 99.7% of all clients scan successfully. I think that's pretty decent!