[[Template core/front/global/favico is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] Jump to content
CCleaner Community Forums

Winapp2.ini additions


Recommended Posts

On 24/04/2020 at 03:25, don_dolarson said:

The previously proposed application Caprine left over some files in C:\Users\%USERPROFILE%\AppData\Roaming\Caprine after it's uninstallation, and disappeared from CCleaner. About 70MB of data.

 

We can change the detection, but CCleaner will still only delete the folders and files defined in Winapp2.ini after uninstalling the application. A complete removal of all leftovers after an uninstall will always require manual work or a special uninstaller tool.

 

On 24/04/2020 at 07:20, siliconman01 said:

... [NetworkList *] ...

Testing this entry, on reboot of the system, it causes an alert message to appear in the Notification tray asking if the user wants to make the network discoverable.  The default value is Yes.  This could be a bit discerning for users to who are running multiple computers on a network.  

 

Right! This entry deletes the data and few but important settings of all networks ever connected. This may not be a big problem on a stationary PC with only one network connection, but on a Notebook with many changing network connections (different private, business and public networks) this must be set again for each network as desired.

Windows saves the network/firewall category (Public, Private, Domain) there, hence the request after a reboot. Also, some people change the name of a LAN there (under Windows 7 this was even possible via the Control Panel).

Link to post
Share on other sites

Hopefully this version doesn't suffer from the same false positive problem the previous ones have but if it does we'll use the release version on the page above as the watershed release to have vendors whitelist

Link to post
Share on other sites
11 hours ago, Winapp2.ini said:

Hopefully this version doesn't suffer from the same false positive problem the previous ones have but if it does we'll use the release version on the page above as the watershed release to have vendors whitelist

KIS 2020 is not barking at the new version yet. 😀

Link to post
Share on other sites
12 hours ago, Winapp2.ini said:

Hopefully this version doesn't suffer from the same false positive problem the previous ones have but if it does we'll use the release version on the page above as the watershed release to have vendors whitelist

MS Antivirus did flag the latest version

Question: What happened to the Default entries and how how do I add them back using winapp2ool?

Link to post
Share on other sites
2 hours ago, ricktendo64 said:

MS Antivirus did flag the latest version

Question: What happened to the Default entries and how how do I add them back using winapp2ool?

 

The VirusTotal summary is still clean:
https://www.virustotal.com/gui/file/59467eb6dac8716afbd617f7e01b1b32dc00056ad2dd92f4016ae721809fd1af/detection
Did you possibly mean blocking by SmartScreen?

About your question:
https://github.com/MoscaDotTo/Winapp2/issues/412
You could use the previous version 1.02 for this. Select "WinappDebug" (1) and enable "Toggle Autocorrect" (3). When you execute "Run" (1) the lines will be inserted automatically again.

Link to post
Share on other sites

Hi

i just notice some of the cleaning entries were missing from my ccleaner

did anyone else experience this?

Win 8.1

ccleaner v5.65

Untitled1.png

 

[Search Charm History]
ID=2411
LangSecRef=3025
Default=True
DetectOS=6.3|6.3
FileKey1=%LocalAppData%\Microsoft\Windows\ConnectedSearch\History|*.lnk

and this entry missing from my ccleaner too but i think this is cc bug or is it just me?

Link to post
Share on other sites
On 26/04/2020 at 00:47, dvdbane said:

... i just notice some of the cleaning entries were missing from my ccleaner ...

 

This problem is not caused by Winapp2.ini, it is definitely a bug in the current CCleaner version.

A DetectOS according to the scheme "DetectOS=from|to" does not work anymore.

Edit: https://community.ccleaner.com/topic/58081-detectos/

Link to post
Share on other sites
On 25/04/2020 at 02:20, ricktendo64 said:

MS Antivirus did flag the latest version

Question: What happened to the Default entries and how how do I add them back using winapp2ool?

 

Winapp2ool isn't able to do this but you can add the defaults back in very easily using a find&replace that supports extended characters or regex like notepad++

Replace "]" with "]\nDefault=False" in winapp2.ini using Notepad++ set to Extended to add the "Default=False" line back into every entry automatically

Link to post
Share on other sites
On 25/04/2020 at 01:37, siliconman01 said:

KIS 2020 is not barking at the new version yet. 😀

KIS 2020 suddenly started quarantining V1.4.7419.18289 of Winapp2ool.exe :(   Had to add to KIS 2020 exclusions.

KIS 2020 blocks it as VHO:Trojan.Win32.Sdum.gen

Edited by siliconman01
Added Trojan ID
Link to post
Share on other sites
32 minutes ago, siliconman01 said:

KIS 2020 suddenly started quarantining V1.4.7419.18289 of Winapp2ool.exe :(   Had to add to KIS 2020 exclusions.

KIS 2020 blocks it as VHO:Trojan.Win32.Sdum.gen

This hasn't shown up on VirusTotal yet but I'll submit it to them through their False Positive page, thanks for the TrojanID

Link to post
Share on other sites
On 25/04/2020 at 02:20, ricktendo64 said:

MS Antivirus did flag the latest version

Question: What happened to the Default entries and how how do I add them back using winapp2ool?

winapp2ool beta now has a feature in WinappDebug that allows you to override the empty default value and specify the one you'd like, inserting it into entries who are missing it.

Link to post
Share on other sites
Posted (edited)
15 hours ago, Winapp2.ini said:

This hasn't shown up on VirusTotal yet but I'll submit it to them through their False Positive page, thanks for the TrojanID

HitManPro also detects the Trojan as long as Kaspersky is falsely detecting it.

HitmanPro.png.a8be3212456a5f4d424d19619c6ba5f9.png

UPDATE as of 01-May-2020 04:30 am EDT.  It appears that Kaspersky has corrected the false positive.  Both KIS 2020 and HitmanPro now scan clear.

Edited by siliconman01
False Positive Corrected
Link to post
Share on other sites
6 hours ago, siliconman01 said:

UPDATE as of 01-May-2020 04:30 am EDT.  It appears that Kaspersky has corrected the false positive.  Both KIS 2020 and HitmanPro now scan clear.

Hooray!

Link to post
Share on other sites
50 minutes ago, Winapp2.ini said:

Hooray!

Apparently, Kaspersky uses the Build and Version number of Windows 10 to issue corrections on False Positives.  Kaspersky has not caught up with the latest Insider Build 19619.1000 Version 2004 and is continuing to flag Winapp2ool.exe on my Insider test computer. 🤨

Link to post
Share on other sites

the latest winapp2ool beta build includes support for adding a whitelist and a blacklist to the trim process.

simply fill a whitelist.ini and/or blacklist.ini file with the headers (you don't need the whole entry, just the [Header *] of entries you want to never trim or always trim

entries in whitelist.ini will always be kept in the file, irrespective of whether or not the detection criteria are met

entries in blacklist.ini will never be kept in the file, likewise.

The menu might be a little wonky!

Link to post
Share on other sites
18 minutes ago, Winapp2.ini said:

the latest winapp2ool beta build includes support for adding a whitelist and a blacklist to the trim process.

simply fill a whitelist.ini and/or blacklist.ini file with the headers (you don't need the whole entry, just the [Header *] of entries you want to never trim or always trim

entries in whitelist.ini will always be kept in the file, irrespective of whether or not the detection criteria are met

entries in blacklist.ini will never be kept in the file, likewise.

The menu might be a little wonky!

Is the beta version 1.4.7426.13493 ??

Link to post
Share on other sites
2 minutes ago, siliconman01 said:

Is the beta version 1.4.7426.13493 ??

Any build with 1.4.7426.xxxxx was built today, I've been working actively on the beta today so as of the time of this post the latest build is 1.4.7426.15697. A link is available in the first post, or you can toggle beta participation from a non-beta build in the settings

Link to post
Share on other sites

I have a Whitelist.ini and Blacklist.ini in my CCleaner folder.  Using Winapp2ool.exe v1.4.7426.15696, the Whitelist.ini and Blacklist.ini appear to be honored.  

Link to post
Share on other sites
Posted (edited)

Winapp2ool.exe v1.4.7426.15696 does not save the useblacklist=TRUE status in winapp2ool.ini when using both a Whitelist and Blacklist in the CCleaner folder.

[Trim]
MergeFile1_Name=winapp2.ini
MergeFile1_Dir=C:\Program Files\CCleaner
MergeFile3_Name=winapp2.ini
MergeFile3_Dir=C:\Program Files\CCleaner
DownloadFileToTrim=False
ModuleSettingsChanged=True
TrimFile1_Name=whitelist.ini
TrimFile1_Dir=C:\Program Files\CCleaner
TrimFile2_Name=whitelist.ini
TrimFile2_Dir=C:\Program Files\CCleaner
TrimFile3_Name=winapp2.ini
TrimFile3_Dir=C:\Program Files\CCleaner
TrimFile4_Name=blacklist.ini
TrimFile4_Dir=C:\Program Files\CCleaner
UseWhiteList=True
useBlackList=False

UPDATE:  If UseWhiteList=True and useBlacklist=True at the same time, a TRIM removes all of the Winapp2.ini entries and leaves only the Whitelist entries....weird.

Edited by siliconman01
UPDATE
Link to post
Share on other sites
5 hours ago, siliconman01 said:

Winapp2ool.exe v1.4.7426.15696 does not save the useblacklist=TRUE status in winapp2ool.ini when using both a Whitelist and Blacklist in the CCleaner folder.

[Trim]
MergeFile1_Name=winapp2.ini
MergeFile1_Dir=C:\Program Files\CCleaner
MergeFile3_Name=winapp2.ini
MergeFile3_Dir=C:\Program Files\CCleaner
DownloadFileToTrim=False
ModuleSettingsChanged=True
TrimFile1_Name=whitelist.ini
TrimFile1_Dir=C:\Program Files\CCleaner
TrimFile2_Name=whitelist.ini
TrimFile2_Dir=C:\Program Files\CCleaner
TrimFile3_Name=winapp2.ini
TrimFile3_Dir=C:\Program Files\CCleaner
TrimFile4_Name=blacklist.ini
TrimFile4_Dir=C:\Program Files\CCleaner
UseWhiteList=True
useBlackList=False

UPDATE:  If UseWhiteList=True and useBlacklist=True at the same time, a TRIM removes all of the Winapp2.ini entries and leaves only the Whitelist entries....weird.

 

I can't reproduce the behavior described in the update

Link to post
Share on other sites

I'm not seeing that behavior either on Beta version 1.4.7427.18038.  It seems to be working okay

[Trim]
TrimFile1_Name=winapp2.ini
TrimFile1_Dir=C:\Program Files\CCleaner
TrimFile2_Name=whitelist.ini
TrimFile2_Dir=C:\Program Files\CCleaner
TrimFile3_Name=winapp2.ini
TrimFile3_Dir=C:\Program Files\CCleaner
TrimFile4_Name=blacklist.ini
TrimFile4_Dir=C:\Program Files\CCleaner
DownloadFileToTrim=False
UseWhiteList=True
useBlackList=True
ModuleSettingsChanged=True

Link to post
Share on other sites

Also, please keep in mind that Kaspersky and HitmanPro continue to flag these new betas as VHO:Trojan.Win32.Sdum.gen.  (false positive needs fixed before a new public release of Winapp2ool.exe).  Kaspersky even blocks a VirusTotal submission as a malicious website.

VirusTotalKaspersky.png

Link to post
Share on other sites

Unfortunately I can only go by VirusTotal and it currently shows clear.

https://www.virustotal.com/gui/file/5ba3effd47aed9b57a31d3398fcd35168be2d83001f78653c74ce6f141e8c9e2/detection

It seems kaspersky is being particularly hostile here, but I'm not sure why as none of these vendors provide tremendous information on their flagging motivations (for good reasons I suppose)

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
×
×
  • Create New...