Jump to content

Winapp2.ini additions


Winapp2.ini

Recommended Posts

 

I don't think it's random at all if we look at Automatic Updates/Windows Updates as a culprit of where it unpacks files which is always the hard disk with the most free space available - it's a very Microsoft thing to do even if drive C:\ has more than enough room for temporary setup files which annoys the living piss out of me, we have a Temp folder on the system drive for a reason.

 

I personally don't know how to code a cleaner for winapp2.ini (file) to look on other hard disks without specifically specifying things like E:\, P:\, T:\, etc., which wouldn't be suited for everyone's system, unless of course we included all possible hard disk locations running the alphabetic drive gauntlet going from C:\ to Z:\

 

Edit:

I'll use this on my system since those are the hard disks I have, it should work as a template for others to modify for their own.

[VCRedist Temp Setup Files*]
Section=VCRedist Temp Setup Files
Default=False
DetectFile=%systemdrive%\VC_RED.cab
DetectFile2=%systemdrive%\VC_RED.MSI
DetectFile3=D:\VC_RED.cab
DetectFile4=D:\VC_RED.MSI
DetectFile5=E:\VC_RED.cab
DetectFile6=E:\VC_RED.MSI
FileKey1=%systemdrive%\|eula.1028.txt;eula.1031.txt;eula.1033.txt;eula.1036.txt;eula.1040.txt;eula.1041.txt;eula.1042.txt;eula.2052.txt;eula.3082.txt;globdata.ini;install.exe;install.ini;install.res.1028.dll;install.res.1031.dll;install.res.1033.dll;install.res.1036.dll;install.res.1040.dll;install.res.1041.dll;install.res.1042.dll;install.res.2052.dll;install.res.3082.dll;VC_RED.cab;VC_RED.MSI;vcredist.bmp
FileKey2=D:\|eula.1028.txt;eula.1031.txt;eula.1033.txt;eula.1036.txt;eula.1040.txt;eula.1041.txt;eula.1042.txt;eula.2052.txt;eula.3082.txt;globdata.ini;install.exe;install.ini;install.res.1028.dll;install.res.1031.dll;install.res.1033.dll;install.res.1036.dll;install.res.1040.dll;install.res.1041.dll;install.res.1042.dll;install.res.2052.dll;install.res.3082.dll;VC_RED.cab;VC_RED.MSI;vcredist.bmp
FileKey3=E:\|eula.1028.txt;eula.1031.txt;eula.1033.txt;eula.1036.txt;eula.1040.txt;eula.1041.txt;eula.1042.txt;eula.2052.txt;eula.3082.txt;globdata.ini;install.exe;install.ini;install.res.1028.dll;install.res.1031.dll;install.res.1033.dll;install.res.1036.dll;install.res.1040.dll;install.res.1041.dll;install.res.1042.dll;install.res.2052.dll;install.res.3082.dll;VC_RED.cab;VC_RED.MSI;vcredist.bmp

That's what I've done, just added detect and delete keys for the E drive as well. I'm guessing wildcards wouldn't work for drive letters?

Link to comment
Share on other sites

  • Moderators

That's what I've done, just added detect and delete keys for the E drive as well. I'm guessing wildcards wouldn't work for drive letters?

 

Never tried it, but even without trying it I doubt it would work for drives.

 

What we need is a new variable from the developers such as %roothdd% or something similar that would let CCleaner detect and delete from the root of hard disks, if instructed to via a winapp2.ini cleaner.

 

Edit:

Such a variable could help with stuff that isn't stored on drive C:\

Edited by Andavari
Link to comment
Share on other sites

New

the warning might need tweaking/rewording.

 

 

[Windows 8 Sharing MFU*]
DetectOS=6.2|
LangSecRef=3025
Detect=HKCU\Software\Microsoft\Windows
Default=False
Warning=This will remove the frequently shared list. e.g. email addresses that have been used to share. This does not remove the Apps listed under sharing.
RegKey1=HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\SharingMFU
Link to comment
Share on other sites

Since last update, "Windows media player ( database)" delete .wmdb in WMP, so make WMP empty of artists and we must wait the build of the files!!!

 

It's not crap files!!

 

Why always change what works?

Sorry about that. The change was posted on the forum and no one objected so I assumed it to be okay. I'll remove that in the next update.

Link to comment
Share on other sites

Revised Entry

Added FileKey1, FileKey2 and changed FileKey3 from REMOVESELF to RECURSE

 
[iMobie PhoneClean*]
LangSecRef=3024
Detect=HKCU\Software\Imobie\PhoneClean
Default=False
FileKey1=%AppData%\iMobie\PhoneClean\DeviceBackup\Backup|*.*|RECURSE
FileKey2=%AppData%\iMobie\PhoneClean\DeviceBackup\Restore|*.*|RECURSE
FileKey3=%AppData%\iMobie\PhoneClean\ErrorLog|*.*|RECURSE
Link to comment
Share on other sites

Since last update, "Windows media player ( database)" delete .wmdb in WMP, so make WMP empty of artists and we must wait the build of the files!!!

 

It's not crap files!!

 

Why always change what works?

does this entry only affect windows xp? based on filekey directory %SystemDrive%\Documents and Settings\ because i can't access it in win 7

in my windows 7+wmp 12, without filekey4,there nothing to delete

only filekey4 relevant to my system and detect 6 files : CurrentDatabase_372.wmdb,LocalMLS_0.wmdb,LocalMLS_1.wmdb,LocalMLS_2.wmdb,LocalMLS_3.wmdb,wmpfolders.wmdb

clean and it only clear library, playlist still intact and playable

the main db would be CurrentDatabase_372.wmdb

clean this and whole library gone

 

i ignore this update because of the warning for this entry

Warning=This will remove ratings, play counts, last played, etc.

i've seen other tool able to delete this db and welcome this changes to the new winapp2.ini but this is only my opinion

i don't know how the entry supposed to work but i'm gonna keep this if it is remove in the next update

 

Link to comment
Share on other sites

does this entry only affect windows xp? based on filekey directory %SystemDrive%\Documents and Settings\ because i can't access it in win 7

in my windows 7+wmp 12, without filekey4,there nothing to delete

only filekey4 relevant to my system and detect 6 files : CurrentDatabase_372.wmdb,LocalMLS_0.wmdb,LocalMLS_1.wmdb,LocalMLS_2.wmdb,LocalMLS_3.wmdb,wmpfolders.wmdb

clean and it only clear library, playlist still intact and playable

the main db would be CurrentDatabase_372.wmdb

clean this and whole library gone

 

i ignore this update because of the warning for this entry

Warning=This will remove ratings, play counts, last played, etc.

i've seen other tool able to delete this db and welcome this changes to the new winapp2.ini but this is only my opinion

i don't know how the entry supposed to work but i'm gonna keep this if it is remove in the next update

I'm on win8.1!! And it deletes the whole library!

In fact when we "analyse" ( wmp must be closed):

843666Capture.png

The 194 Mo is the whole library!!

Winapp2 is supposed to delete craps, for me: it's not craps and it takes a lot of time for rebuild it!

Link to comment
Share on other sites

Why always change what works?

Changes are made to enhance cleaning.

Sometimes the consequences may prove to be unfortunate.

 

Regrettably the only ways to avoid an unfortunate result are :-

To never update CCleaner.exe nor Winapp2.ini;

or to closely examine the ANALYZE results and understand potential consequences before they occur;

or to create backups to fall back on when it goes wrong.

Link to comment
Share on other sites

I'm on win8.1!! And it deletes the whole library!

In fact when we "analyse" ( wmp must be closed):

The 194 Mo is the whole library!!

Winapp2 is supposed to delete craps, for me: it's not craps and it takes a lot of time for rebuild it!

that why there is warning included with the entry

another way to prevent this from happening aside from what @Alan_B had wrote :

deselect all > select one by one every winapp2.ini update

or search inside winapp2.ini for warning

or go to http://winapp2.com/changes.html to check for any changes inside winapp2.ini

 

here another changes that might affect you

 

[Cached File Extensions*]

LangSecRef=3025

Detect=HKCU\Software\Microsoft\Windows

Default=False

Warning=Can cause issues on Windows 8.1!

RegKey1=HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts

RegKey2=HKCU\Software\Microsoft\Windows\Roaming\OpenWith\FileExts

RegKey3=HKU\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts

- Added Warning

Link to comment
Share on other sites

Winapp2 is supposed to delete craps, for me: it's not craps and it takes a lot of time for rebuild it!

For YOU it's not crap (your words), it may be for someone else. You don't have to use every entry (in fact it's encoraged NOT to). There are many entries I don't use because what they clean is valuable to me. I hate WMP adding stuff to libraries, playlists, ratings etc, so have no problem with the entry. If I used those functions, I'd simply not use that entry (or edit out the filekey for the item I wanted to keep). The entry does have a fairly clear warning and as winapp2 entries are user created extra care should ALWAYS be taken when adding them, Winapp2 (the member) simply cannot check every single item is safe and without him there would BE no entries.

Link to comment
Share on other sites

  • Moderators

I believe the WMDB was removed from the entry (after a ton of griping by me) when the devs adopted the entry and it started killing people's media library wholesale.Edit: found it

 

Agree with this. This was added to Winapp2.ini and I spokme out against it. Some how it seems to have crossed over without the proper removal of database removal or at least the warning that appears in Winapp2This is the offending ItemFileKey4=%LocalAppData%MicrosoftMedia Player|*.wmdb

 

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.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

  • Moderators

Regrettably the only ways to avoid an unfortunate result are :-

To never update CCleaner.exe nor Winapp2.ini;

or to closely examine the ANALYZE results and understand potential consequences before they occur;

or to create backups to fall back on when it goes wrong.

 

One other way which I prescribe to: Only pick and choose what you want from the winapp2.ini file.

 

Like you stated analyze first before ever committing to a clean. Even new versions of CCleaner should be treated in that way, analyze first!

Link to comment
Share on other sites

Hmm, but it's not a big problem, as you said: i can uncheck it!

 

But if i posted this problem, it was cause i thought it was a mistake! ( like it was, in the past, for "utorrent more" )

 

But you're right, for each new update, it's better to analyse first!! ;)

 

BTW: thx for the advertize for [Cached File Extensions*], i just uncheck it!! What's wrong with it? I wish that it's not too late!

Link to comment
Share on other sites

New entries:

[Aimersoft DRM Media Converter*]
LangSecRef=3023
Detect=HKLM\SOFTWARE\Aimersoft\351
Default=False
FileKey1=%ProgramFiles%\Aimersoft\DRM Media Converter\Log|*.*|REMOVESELF

[DiskBoss Logs*]
LangSecRef=3024
Detect=HKLM\SOFTWARE\Flexense\DiskBoss Ultimate
Default=False
FileKey1=%LocalAppData%\DiskBoss Ultimate\data\reports|*.*|REMOVESELF

[Green Ranch Log*]
Section=Games
Detect=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Green RanchFINAL
Default=False
FileKey1=%AppData%\Palaplay\GreenRanch_Survey|*.txt

[NowSmart Cut*]
LangSecRef=3023
Detect=HKLM\Software\NowSmart\Cut
Default=False
FileKey1=%LocalAppData%\Cut|log.txt;*.dmp

[Wondershare Video Converter Pro*]
LangSecRef=3023
Detect=HKLM\SOFTWARE\Wondershare\Wondershare Video Converter Pro
Default=False
FileKey1=%AllUsersProfile%\Documents\Wondershare|*.*|REMOVESELF
FileKey2=%CommonAppData%\Wondershare Video Converter*|*.dat.bak
FileKey3=%CommonAppData%\Wondershare Video Converter*\TempSiteIconDir
FileKey4=%CommonAppData%\Wondershare Video Converter*\TempThumbDir
FileKey5=%ProgramFiles%\Wondershare\Video Converter*\Log|*.*|REMOVESELF

Modified:

[Wondershare Helper Compact*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Wondershare\Wondershare Helper Compact
Default=False
FileKey1=%CommonProgramFiles%\Wondershare\Wondershare Helper Compact\Log|*.*|RECURSE

- Improved Detect

Link to comment
Share on other sites

New entries:

[Clam Sentinel*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{060FE577-1BDF-4330-ACCA-B6760AB07191}_is1
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|REMOVESELF
FileKey2=%ProgramFiles%\ClamSentinel|*.txt

[ClamWin*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\ClamWin
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|REMOVESELF
FileKey2=%ProgramFiles%\ClamWin\bin|*.txt
Link to comment
Share on other sites

  • Moderators

 

New entries:

[Clam Sentinel*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{060FE577-1BDF-4330-ACCA-B6760AB07191}_is1
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|RECURSE
FileKey2=%ProgramFiles%\ClamSentinel|*.txt

[ClamWin*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\ClamWin
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|RECURSE
FileKey2=%ProgramFiles%\ClamWin\bin|*.txt

 

Remember a while ago when ClamWin/Clam Antivirus was deeming just about every .exe on system as infected? If the log files were still intact the users could restore their files, if not their systems were hosed.

Link to comment
Share on other sites

Remember a while ago when ClamWin/Clam Antivirus was deeming just about every .exe on system as infected? If the log files were still intact the users could restore their files, if not their systems were hosed.

I see there are some previous concerns regarding 'ClamScanLog.txt' mentioned in their forum.

Damn, when I get home from work I'll reinstall ClamWin and test that scenerio to qualify the rule or not.

Thanks I didn't foresee that.

Link to comment
Share on other sites

Revised Entries

Changed LangSecRef from 3021 to 3023

CCleaner's CyberLink PowerDirector 12 entry is also under the Multimedia section (LangSecRef 3023).

 

[CyberLink PowerDirector 10*]

LangSecRef=3023

Detect=HKCU\Software\CyberLink\PowerDirector10

Default=False

FileKey1=%Documents%\CyberLink\PowerDirector\10.0|Snapshot(*).jpg

FileKey2=%Documents%\CyberLink\PowerDirector\10.0\MyTitles|*.*|RECURSE

FileKey3=%Documents%\CyberLink\PowerDirector\10.0\Preview Cache Files|*.*

FileKey4=%Documents%\CyberLink\PowerDirector\10.0\ShadowEditFiles|*.MPG

FileKey5=%Documents%\CyberLink\PowerDirector\10.0\SplitterIndex|*.maidx

 

[CyberLink PowerDirector 11*]

LangSecRef=3023

Detect=HKCU\Software\CyberLink\PowerDirector11

Default=False

FileKey1=%Documents%\CyberLink\PowerDirector\11.0|Snapshot(*).jpg

FileKey2=%Documents%\CyberLink\PowerDirector\11.0\MyTitles|*.*|RECURSE

FileKey3=%Documents%\CyberLink\PowerDirector\11.0\Preview Cache Files|*.*

FileKey4=%Documents%\CyberLink\PowerDirector\11.0\ShadowEditFiles|*.MPG

FileKey5=%Documents%\CyberLink\PowerDirector\11.0\SplitterIndex|*.maidx

Link to comment
Share on other sites

Remember a while ago when ClamWin/Clam Antivirus was deeming just about every .exe on system as infected? If the log files were still intact the users could restore their files, if not their systems were hosed.

After repeated testing, the entries below are fine as is...

ClamWin did quarantine several files; though false-positve.

The quarantine logs are now stored in the Quarantine folder. 'Quarantine Browser' aka 'QRecover' is used to view content, log, and delete, or restore files.

Deletion of the other log files had no bearing upon quarantined file recovery, etc. Everything restored fine after running the entry.

The restoration issues you mention date back to version 0.96.4 in 2010. This has been resolved. ClamScanLog.txt is no longer used for restoration.

Sidenote:

This AV used extremely low resources, but used 749 MB drive space (mostly AV definitions)  and has very aggressive heuristics.

[Clam Sentinel*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{060FE577-1BDF-4330-ACCA-B6760AB07191}_is1
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|REMOVESELF
FileKey2=%ProgramFiles%\ClamSentinel|*.txt

[ClamWin*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\ClamWin
Default=False
FileKey1=%AllUsersProfile%\.clamwin\log|*.*|REMOVESELF
FileKey2=%ProgramFiles%\ClamWin\bin|*.txt

New entries:

[Immunet (ClamAV)*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Immunet Protect
Default=False
Warning='Immunet' service must be stopped to remove log files.
FileKey1=%AllUsersProfile%\Immunet|*.log
FileKey2=%AppData%\Immunet|*.*|REMOVESELF
FileKey3=%ProgramFiles%\Immunet|*.log|RECURSE

[Trend Micro AntiRansomware Tool*]
LangSecRef=3021
DetectFile=%ProgramFiles%\AntiRansomware2.0
Default=False
FileKey1=%CommonAppData%\AntiRansomware|*.log
Link to comment
Share on other sites

Don't you just hate some programs. Just spent half an hour going through Steam directories and making an entry to remove all non-English language files, lots of them in various directories (20Mb worth), then find Steam reinstalls when you try to launch it. Go through the 11-12 filekeys to try to find the troublesome one only to find if you tounch ANY of them, Steam reinstalls when you start it! <_<

Link to comment
Share on other sites

Modified:

[Realtek (Logs)*]
LangSecRef=3021
Detect=HKLM\SOFTWARE\Realtek
Default=False
FileKey1=%ProgramFiles%\Realtek*|*.log;*.txt|RECURSE
ExcludeKey1=FILE|%ProgramFiles%\Realtek\*\InstCtrl.txt
ExcludeKey2=FILE|%ProgramFiles%\Realtek\*\setupctrl.txt

- Changed LangSecRef to 3021
- Added ExcludeKey1 and 2
- Modified FileKey1 to include additional installations log files

Recommend removal of Realtek Card Reader entry below. It becomes redundant:

[Realtek Card Reader*]
LangSecRef=3021
DetectFile=%ProgramFiles%\Realtek\Realtek USB 2.0 Card Reader
Default=False
FileKey1=%ProgramFiles%\Realtek\Realtek USB 2.0 Card Reader|rmb.log
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.