Jump to content
CCleaner Community Forums
Winapp2.ini

Winapp2.ini additions

Recommended Posts

 

A user posted this over at GitHub: https://github.com/MoscaDotTo/Winapp2/issues/42

 

What does everyone think? Some of them look a little too risky maybe?

The ones that delete old Windows installations, the $patchcache and the winsxs backup folder are definite no no's IMO (I do occasionally wipe the latter, but seen others have issues caused by it). In all my years of computing I've never seen a convincing/safe reason to delete the $patchcache, other than a last resort if running out of disk space. And the old installations files, seems common sense to not delete them, at least not as a matter of course in a cleaning program.

Share this post


Link to post
Share on other sites
 

 

 

A user posted this over at GitHub: https://github.com/MoscaDotTo/Winapp2/issues/42

 

What does everyone think? Some of them look a little too risky maybe?

 

 

The ones that delete old Windows installations, the $patchcache and the winsxs backup folder are definite no no's IMO (I do occasionally wipe the latter, but seen others have issues caused by it). In all my years of computing I've never seen a convincing/safe reason to delete the $patchcache, other than a last resort if running out of disk space. And the old installations files, seems common sense to not delete them, at least not as a matter of course in a cleaning program.

I'm with you on this one

Share this post


Link to post
Share on other sites

What about the Windows System Volume Tracking.log*? I think it's safe, but is there anyway a wildcard could be used instead of making all those FileKeys?

Share this post


Link to post
Share on other sites
What about the Windows System Volume Tracking.log*? I think it's safe, but is there anyway a wildcard could be used instead of making all those FileKeys?

I think that log has to do with restore points, but am unsure. Don't think there's a wildcard that could do it

Share this post


Link to post
Share on other sites

I suspect the System Volume Information is inaccessible on most user systems unless the user intentionally takes ownership of the folder (which is not frequently done).  

Share this post


Link to post
Share on other sites

I suspect the System Volume Information is inaccessible on most user systems...

 

Even outside of Windows using various boot CDs it's inaccessible.

Share this post


Link to post
Share on other sites

The ones that delete old Windows installations, the $patchcache and the winsxs backup folder are definite no no's IMO (I do occasionally wipe the latter, but seen others have issues caused by it). In all my years of computing I've never seen a convincing/safe reason to delete the $patchcache, other than a last resort if running out of disk space. And the old installations files, seems common sense to not delete them, at least not as a matter of course in a cleaning program.

 

By the way, if anyone wanted to clean the windows.old files, you can do this in Windows built in cleaner. Just select your drive, click properties, click disk cleanup, click clean up system files, then check Windows Old I believe it's called.

Share this post


Link to post
Share on other sites
@dvdbane: Temp Files* and SyncBackFree* are from the removed entries section (just saying cause it took me awhile to find these, lol), but thanks I corrected them, too.

 

https://github.com/MoscaDotTo/Winapp2/commit/efcfedc542d1b19e77f195efe4596588978ce43f

the keyword here "non-ccleaner winapp2.ini" :P

 

you need to be careful with Ghost's entries...he already posted the same entries here over and over again

now, he do it there

sorry Ghost, too risky but i like this one [useless File Extension 2.2*] :P

https://forum.piriform.com/index.php?showtopic=32310&page=257&do=findComment&comment=266881

 

did you test his entries before you update in winapp2.ini?

take [installer*] as an example from https://github.com/MoscaDotTo/Winapp2/commit/5fd04a149f1e764d9ccf72677095515ccfe0aef5

he remove the asterisk * from the filekey and from my test here with my computer, cc couldn't detect the file

and the reason why the original entry for [installer*] got asterisk like this Google\Chrome*\ because it is needed to support Chrome Sxs

if you don't understand what i mean, read here https://forum.piriform.com/index.php?showtopic=32310&page=259&do=findComment&comment=267339

 

FileKey4=%ProgramFiles%\Google\Chrome\Application\\Installer|.7z|RECURSE

 

you need to revert the entries back to before the update and please double check before update :)

Share this post


Link to post
Share on other sites

the keyword here "non-ccleaner winapp2.ini" :P

 

you need to be careful with Ghost's entries...he already posted the same entries here over and over again

now, he do it there

sorry Ghost, too risky but i like this one [useless File Extension 2.2*] :P

https://forum.piriform.com/index.php?showtopic=32310&page=257&do=findComment&comment=266881

 

did you test his entries before you update in winapp2.ini?

take [installer*] as an example from https://github.com/MoscaDotTo/Winapp2/commit/5fd04a149f1e764d9ccf72677095515ccfe0aef5

he remove the asterisk * from the filekey and from my test here with my computer, cc couldn't detect the file

and the reason why the original entry for [installer*] got asterisk like this Google\Chrome*\ because it is needed to support Chrome Sxs

if you don't understand what i mean, read here https://forum.piriform.com/index.php?showtopic=32310&page=259&do=findComment&comment=267339

 

FileKey4=%ProgramFiles%\Google\Chrome\Application\\Installer|.7z|RECURSE

 

you need to revert the entries back to before the update and please double check before update :)

 

His previous name on GitHub was winapp2, he deleted his account so people wouldn't think he was winapp2 owner. I felt like he was a user here who got banned (tho I was thinking of a different user who got banned).

 

Anyways, there is no revert button, so can you tell me which and where needs to be fixed?

 

Also, you can't rely on just me know to know everything works. I posted the log here 2 days ago to make sure everyone was OK and I didn't include the ones that everyone disagreed with.

Share this post


Link to post
Share on other sites

i know there is no Revert button

use the changelog and replace the + entries with - entries

[Argus Monitor*]
LangSecRef=3024
Detect=HKCU\Software\Argotronic\Argus Monitor
Default=False
FileKey1=%Documents%\|ArgusMonitor_EventLog.txt;ArgusMonitor_CSVLog.csv
FileKey2=%LocalAppData%\VirtualStore\Program Files*|ArgusMonitor_EventLog.txt;ArgusMonitor_CSVLog.csv
FileKey3=%ProgramFiles%\|ArgusMonitor_EventLog.txt;ArgusMonitor_CSVLog.csv
- siliconman01 fix #5747

[Foxit Reader 8.0*]
LangSecRef=3021
Detect=HKCU\Software\Foxit Software\Foxit Reader 8.0
Default=False
RegKey1=HKCU\Software\Foxit Software\Foxit Reader 8.0\Preferences\History\LastOpen
RegKey2=HKCU\Software\Foxit Software\Foxit Reader 8.0\Preferences\History\LastSession
RegKey3=HKCU\Software\Foxit Software\Foxit Reader 8.0\Preferences\Others|csInitialOpenDir
RegKey4=HKCU\Software\Foxit Software\Foxit Reader 8.0\MRU\File MRU
RegKey5=HKCU\Software\Foxit Software\Foxit Reader 8.0\MRU\Place MRU
FileKey1=%LocalAppData%\Foxit Reader\|*_old.DMP
FileKey2=%AppData%\Foxit Software\Foxit Reader\Foxit Cloud\DownloadCache|*.cache
FileKey3=%AppData%\Foxit Software\Foxit Reader\Foxit Cloud\FileIDCache|*.fcd
FileKey4=%AppData%\Foxit Software\Foxit Reader\Foxit Cloud|foxitcloud.log
FileKey5=%CommonAppData%\Foxit Software|*.log|RECURSE
- my entry #5736

[Installer*]
LangSecRef=3029
SpecialDetect=DET_CHROME
Default=False
Warning=Running this may remove Chrome's ability to automatically update to future versions on some computers.
FileKey1=%LocalAppData%\Google\Chrome*\Application\*\Installer|*.7z|RECURSE
FileKey2=%LocalAppData%\Google\Update\*\*\Installer|*.7z|RECURSE
FileKey3=%ProgramFiles%\|GUT*tmp
FileKey4=%ProgramFiles%\Google\Chrome*\Application\*\Installer|*.7z|RECURSE
FileKey5=%ProgramFiles%\Google\Update\*\*\Installer|*.7z|RECURSE
- siliconman01 fix #5747

[InstallShield*]
LangSecRef=3024
Detect=HKCU\Software\InstallShield
Default=False
FileKey1=%ProgramFiles%\|_ISTMP1.DIR
FileKey2=%SystemDrive%\|_ISTMP*.DIR
- siliconman01 fix #5747

btw, you should really double check before you update to prevent something like this happened again

 

fix missing trailing backlash

https://forum.piriform.com/index.php?showtopic=32310&page=288&do=findComment&comment=276329

 

update on Ghost entries that undo the fix

https://forum.piriform.com/index.php?showtopic=32310&page=288&do=findComment&comment=276386

 

i know we need to help you to maintain this project but if this problem happened again, we might missed some of it

no pressure, just a reminder

 

 

 

@all

do we really need this entry?
cc Memory Dumps already support both location
or change fk1 to FileKey1=%WinDir%\LiveKernelReports|*.dmp|RECURSE ???

incase if the entry stay inside winapp2.ini or transfer to non-ccleaner winapp2.ini, i've fix the entry

 

[Live Kernel Watchdog*]
LangSecRef=3025
Detect=HKCU\SOFTWARE\Microsoft
Default=False
FileKey1=%WinDir%\LiveKernelReports\WATCHDOG|*.dmp
FileKey2=%WinDir%\LiveKernelReports|*.dmp|RECURSE
- fix fk2 based on Ghost's update

Share this post


Link to post
Share on other sites

From winapp2.com's download page:

 Winapp2.ini

A set of over 2500 extensions for CCleaner, System Ninja, BleachBit, and Avira System Speedup.
Current version: 5.19.160702

Is this site not getting updated any more with the move to GitHub?

Share this post


Link to post
Share on other sites

From winapp2.com's download page:

 Winapp2.ini

A set of over 2500 extensions for CCleaner, System Ninja, BleachBit, and Avira System Speedup.
Current version: 5.19.160702

Is this site not getting updated any more with the move to GitHub?

 

I don't know what Robert is planning on doing to his website. I don't have control over it, so I can't do anything on my end.

 

To get the most up-to-date copy, you should grab them off GitHub.

Share this post


Link to post
Share on other sites

You can remove following entry because it's included in CCleaner v5.22 now: [Live Kernel Watchdog*]

The subfolder WATCHDOG (FileKey2) is covered by RECURSE of CCleaners entry.

Share this post


Link to post
Share on other sites

New:

[AIMP Classic*]
LangSecRef=3023
DetectFile=%ProgramFiles%\AIMP Classic\cAIMP.exe
Default=False
FileKey1=%ProgramFiles%\AIMP Classic\Data|*.bak|RECURSE

Modified:

[AIMP 2*]
LangSecRef=3023
DetectFile=%ProgramFiles%\AIMP2\AIMP2.exe
Default=False
FileKey1=%AppData%\AIMP|*.bak
FileKey2=%LocalAppData%\VirtualStore\Program Files*\AIMP2\Data|*.bak|RECURSE
FileKey3=%ProgramFiles%\AIMP2\Data|*.bak|RECURSE

Edit FileKey2, Filekey3

Share this post


Link to post
Share on other sites

The files which CCDump creates are also exported with

 

C:> CCleaner /Export <folder to store files in>

 

%ProgramFiles\CCleaner.exe /Export "%UserProfile%\Documents\CCleaner\"

 

No need for CCDump.exe ....

Share this post


Link to post
Share on other sites

 

Thanks for the fast updates!

 

Some small fixes:

- Winapp2.ini: "# of entries" should stay 2,569 (one new entry but also one removed).

- Non-CCleaner / Removed entries: [Memory Dumps] has no asterisk (*) and "# of removed entries" should be 51.

- Non-CCleaner / Winapp2.ini: [Memory Dumps] has no asterisk (*) and "# of entries:" should be 2,569 + 51.

Share this post


Link to post
Share on other sites

Thanks for the fast updates!

 

Some small fixes:

- Winapp2.ini: "# of entries" should stay 2,569 (one new entry but also one removed).

- Non-CCleaner / Removed entries: [Memory Dumps] has no asterisk (*) and "# of removed entries" should be 51.

- Non-CCleaner / Winapp2.ini: [Memory Dumps] has no asterisk (*) and "# of entries:" should be 2,569 + 51.

 

Corrected them:

https://github.com/MoscaDotTo/Winapp2/commit/5c39e23c891371091d2b2340808fef2264b2e310

https://github.com/MoscaDotTo/Winapp2/commit/891f0075c97777e8deea9f1465fe31e448bfbe11

https://github.com/MoscaDotTo/Winapp2/commit/6b628404bce7569c3bbc0fbc5abe9f50f3ac4c4b

 

Ill try harder not to make these mistakes in the future.

Share this post


Link to post
Share on other sites

[Revo Uninstaller Backups*]
LangSecRef=3024
DetectFile=%LocalAppData%\VS Revo group
Default=False
FileKey1=%LocalAppData%\VirtualStore\Program Files*\VS Revo Group\Revo Uninstaller Pro|*.bak
FileKey2=%LocalAppData%\VS Revo Group\Revo Uninstaller Free\BackupsData|*.*|RECURSE
FileKey3=%LocalAppData%\VS Revo Group\Revo Uninstaller Pro\BackupsData|*.*|RECURSE
FileKey4=%ProgramFiles%\VS Revo Group\Revo Uninstaller Pro|*.bak
- remove rupilogs.rupldb from fk1 and fk4

Share this post


Link to post
Share on other sites

Reason?

seem like i misunderstood rupilogs.rupldb's function

i thought they stored cleaning rule inside that db, it's just list of available removal log

but rupilogs.rupldb should be remove from that entry and place in [Revo Uninstaller Pro*]

 

[Revo Uninstaller Pro*]

LangSecRef=3024

Detect=HKCU\Software\VS Revo Group\Revo Uninstaller Pro

Warning=You need to manually download rupilogs.rupldb via Log Database in Option if you disable "Check for update on startup"

Default=False

FileKey1=%AppData%\ruplp\log|*.log

FileKey2=%ProgramFiles%\VS Revo Group\Revo Uninstaller Pro|rupilogs.rupldb

FileKey3=%LocalAppData%\VS Revo Group\Revo Uninstaller Pro|RUPLogsData.ini

FileKey4=%LocalAppData%\VS Revo Group\Revo Uninstaller Pro\Logs\*|*.*|REMOVESELF

RegKey1=HKCU\Software\VS Revo Group\Revo Uninstaller Pro\Uninstaller\Traced\LogsUSs

 - fk2 for log downloaded

 - fk3 for list of log downloaded, doesn't change when fk2 cleaned

 - regkey same as fk3

 - change detect to HKCU\Software\VS Revo Group

 - add warning

Share this post


Link to post
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

×