The scan detection logic is correct. The issue comes from installing via command line. We have attempted to work with the vendor to correct this issue, albeit unsuccessfully thus far. We have succeeded in resolving this issue in our NetChk Protect product, but are unable to implement the same solution with SCUpdates due to limitations within SCCM.
Please feel free to submit your suggestion as follows: