[CCEnhancer & MBAE]

Sorry to double post but I forgot to reply to a post and I can't seem to edit mine.

 

 

 

 More than likely it's because the default paths for log files have been changed in MBAE and MBAM. It's in %ProgramData%, not in %LocalAppData% or %CommonAppData%.

%CommonAppData% is a CCleaner variable (supported kindly by Shane and Andrew for System Ninja and BleachBit respectively) and points to %ProgramData% on Windows Vista+ and either %AllUsersProfile% or %AllUsersProfile%\Application Data on Windows XP

[CCEnhancer & MBAE]

Hiya, I maintain Winapp2.ini on the Piriform Forums (/winapp2.com), and I wrote this entry. The Piriform copy of the file is used as the CCEnhancer definitions.  I'm going to reply to several posts at once, though I'm currently at work so I may get distracted

 

Hi Pedro, this is what's in my winapp2.ini Configuration settings folder located at C:\Program Files\CCleaner\winapp2, same as satrow's.
[Malwarebytes Anti-Exploit Beta*]
LangSecRef=3024
DetectFile=%CommonAppData%\Malwarebytes\Malwarebytes Anti-Exploit
Default=False
FileKey1=%CommonAppData%\Malwarebytes\Malwarebytes Anti-Exploit|*.log
FileKey2=%LocalAppData%\VirtualStore\ProgramData\Malwarebytes\Malwarebytes Anti-Exploit|*.log

 

It appears the script is for deleting the log files of course.  Satrow, you tried the script and CCleaner reports nothing was cleaned? Is that correct?

 

The script does indeed target the log files generated by running MBAE, at least whichever version it was on when I wrote the entry. If the path has changed, it wont delete anything.

 

I went through my usual Analyze routine with CCleaner after selecting only the 3 Malwarebytes entries and nothing was selected for deletion, Ritchie; same result after I ran a MBAM scan.

 

Seems like the winapp2's not working as intended, imo, a good thing, I dislike tools that remove logged data that might be useful in later troubleshooting.

 

Winapp2.ini is essentially a database and all entries are opt-in (disabled by default), users are encouraged to exercise caution when cleaning (analyze first!). No entries are intended to disrupt the functionality of any programs, possibly with the exception of the Steam Installers* entry, which prevents games from launching if they haven't been initialzed before their installers are deleted.

 

 

Thanks for the details guys. It seems from the content of those scripts that it is deleting the MBAE logs. It's not a big deal (it won't break MBAE functionality), but it is completely unnecessary and might prevent troubleshooting an MBAE issue if the logs are gone.

 

I agree 100% with satrow's last comment. These tools that need to somehow show that they are doing something useful by deleting small but useful logs are in fact are just potentially harming troubleshooting abilities. There is absolutely no need to run this scripts unless your hard drive is so full and you are in desperate need of a few KB of extra disk space. So in essence it's completely useless.

 

WRT deleting many small files - it adds up, and some people like to purge all "useless" (to the end user) files before they do an image backup or whatever. As you said, it doesn't break the functionality of the program, it's really just an opt-in for folks who deem the files useless (we do vet what is and is not useless (most recently, here: http://forum.piriform.com/index.php?showtopic=32310&p=250202 and down))

 

...........But CCleaner and CCEnhancer are NOT the same thing, are they?

 

<just sayin'>

 

Nope, and if you mention CCEnhancer on the Piriform Forums, no one will talk to you about it (per the developers request). Any inquiries about the script can be left in the winapp2.ini thread I linked above, any CCEnhancer questions can be posted on the Singular Labs forums http://singularlabs.com/forums/

 

Hi all,

 

I use Ccleaner and the additional winapp2.ini enhancement,  every element that could be cleaned by Ccleaner has a check box next to it that has to be clicked to include it in the cleaning routine (it's opt in not opt out).

 

It would be foolish to click an option for inclusion without knowing exactly what will be deleted.

 

Regards.

 

Aye, everything is defaulted to opt-in (default=false) so nothing is cleaned without the user explicitly opting in to it (though a few times a few default=trues have snuck in, I've tried to maintain opt-in since 2010)
 

If there are any other questions about anything, I'd be glad to answer them.