SAS causes my CPU temp to spike when running a scan, but drops back to normal once the scan completes. Recently, however, I notice that my CPU temp is holding steady at the spike temp even though SAS completes its scan. I went into task manager and noticed a bunch of cacls.exe processes running that were using in excess of 50% my CPU. Terminating these processes results in the temp going back down to normal. Any idea why SAS all of a sudden does not terminate these cacls.exe processes. and instead I must terminate them manually?