Jump to content

An always false key for making our own cleaners


Andavari

Recommended Posts

  • Moderators

I'd like to see the implementation of an "AlwaysFalse" key for making our own cleaners in winapp2.ini. Basically what it would do is always have such cleaners with "AlwaysFalse" as the default setting to automatically get disabled/unticked when restarting CCleaner.

 

Example:

[some App (Logs)*]

LangSecRef=3024

Detect=HKCU\Software\Some App

Default=AlwaysFalse

FileKey1=%appdata%\Some App\Logs|*.*

Link to comment
Share on other sites

  • 2 weeks later...

Default=False

You have to tick that entry first time you run CCleaner, and doesn't get unticked after closing/restarting CCleaner.

Default=AlwaysFalse

Entry resets to false/unticked everytime CCleaner is closed/restared.

Did this help? At least that's how I understood it.

Link to comment
Share on other sites

  • Moderators

naw, by "custom cleaner" he means win*2.ini entries

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT  https://support.piriform.com/hc/en-us and  https://www.ccleaner.com/docs

Pro users file a PRIORITY SUPPORT request at https://support.piriform.com/hc/en-us/requests/new

link to WINAPP2.INI explanation

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.