I have had occasions with 2,6 where a System Scan will begin usi9ng 50% CPU and not progress any further, Twuce ut has happened , and the scan says 100.0% complete. Other times it hangs earlier. When this happens, I cannot stop the scan using the provided button; I have to cancel via the Task Manager. The windows says "scan stopped", but the SDScan.exe executable still uses 50% CPU. If I restart the scan after cancelling, the scan runs to completion.

When the scan hangs, is there any diagnostic to I can use to get more diagnostic information on what may be happening? In March I ran a SysInternals ProcessMonitor scan, and no records were captured.