It appears to be a scanning optimization technology. Since I NEVER scan, I’ve turned it off. I have real-time scanning set to Stateful. So any image access post A/V defs updates gets scanned on initial access since A/V def update. Subsequently its never scanned on any access. I rely on HIPS D+ to alert me that whatever arbitrary image may have been changed; nothing can be accessed or modified without the something doing that having access permissions to do so. So, to me, the whole scheduled - or even manual - scanning issue is moot.
Besides, whenever something IS scanned, the last access date is altered, and THAT upsets my defrag disk-layout scheme, i.e., sorting files based on last access date becomes a moot point if EVERY file on the drive suddenly has the same last accessed date-time stamp.
not good for my hdd. 6 hours writing!
how to avoid this bad behaviour? thanks.
can I shutdown the PC?
PS: ok today I leave it running for hours and hours (as the past week), but then I hope to resolve this embarrassing behaviour caused by CIS quarantine (empty).
Thanks on both users, much appreciated. Now I serach about scheduled tasks (not scheduled by me, perhaps by default?)
a full scan requires 45 minutes, so its strange that a scheduled task employes at least 3 hours!
Ok I will try it.
Yes, I did so. Now I wait for next sunday night.
A doubt: if the “issue” is due to the scheduled complete scan, why CIS stops writing in the quarantine/temp folder after intensive 3-5 hours instead after intensive “normal” 45 minutes ( = the time required by a complete scan) ?