It's been reported allot, and Microsoft are aware of it and without doubt Piriform are as well. The one instance where it is actually helpful is after you've had MSE installed for a long time, cleaning those logs after a long period of time can really regain allot of free disk space.
Who on earth is Megan? There was no Megan who posted in here.
I find this problem also quite annoying; we shouldn't have to uncheck programs because CCleaner removes something that it shouldn't.
Perhaps someone should post this in the Bugs subforum.
A bit annoying yes, especially for new users who don't know to use Analyze first to get a temporary report.
I wouldn't necessarily call it a "bug" myself since like I mentioned in my previous post it can really help regain allot of MB from old scan logs after MSE has been installed and used for a long amount of time. Although it's really one of those things that needs to be off by default, and also when someone enables it a warning box needs to be shown.
The funny thing is when using it myself it didn't always cause MSE to prompt for a system scan immediately afterwards.
I wonder if there's at least one file (maybe more) to exclude which would stop MSE thinking it hasn't scanned? Maybe some important main file or whatever, whereas the logs themselves could be removed.
program would need to provide log emptying API for that to work. And I don't want a world where my antivirus is presenting, to malware, exploitable hooks into itself on purpose
I will do some testing over the next few days; erasing the MSE files manually, but let the latest one stand. See if this will correct MSE's behaviour of complaining that no scan had been run lately.
I never had that happen either, and to this day don't.
Perhaps there is a difference in how your system is set up.
I suggest the possibility that MSE wants to see its last scan log.
It might want this log to be continuously present,
or it might just need to see it when it is started up / launched / used / whatever.
If it is continuously running for real-time protection then it may create a new log file as part of "business as normal" subsequent to CCleaner removing old log files,
hence the latest log will be present upon the next system power up hence MSE will not complain.
If real-time protection is not active then there will be no new log file to detect upon the next scan-on-demand, and the warning is issued.
Another possibility might be that whilst MSE is active it may still retain write/append authority over the latest log file so that Windows will protect against deletion because the file is "in use".
Finally, could the "... older than 24 hours" option be protecting the latest log file for those who have no MSE warning ?
Perhaps this MSE problem only exists for those that have not enabled this protection.
I believe "Windows Temp folders" includes more than %TEMP% so wonder if MSE log files are in a folder that qualifies for such protection.
I remember discussions in the past about whether 24 hours had a duration of 23 hours 59 minutes or all of today plus yesterday,
Well I get a mixed behaviour using it regardless if MSE's real-time protection is on/off. I also never use that 24 hour rule.
It would be nice if Piriform moved the MS AntiMalware cleaner into the Advanced area and have it unticked by default, and have a warning on it when enabled - it's really about time they do something about it because there's always topics like this being started.
