-
Posts
6,470 -
Joined
-
Last visited
Posts posted by Winapp2.ini
-
-
A new winapp2.ini version is available: 210920 that includes the updated DVDFab * entry. You can get it from github or via winapp2ool!
-
Posting here is fine, pull requests are better!
-
I'll be here to maintain winapp2.ini
Be aware that the winapp2ool code signing certificate has expired and I won't be renewing it until my legal name change is complete, so any updates to winapp2ool in the somewhat immediate future will be unsigned and may possibly be flagged as malware. Rest assured that they are not and that the entire source code is always available to you on the repo :)
-
1 hour ago, wiggletiggle475 said:
I was sad to come back and see this deleted after so long, so here's a copy I've had backed up for a while now in case anyone is looking for this in the future:
At a glance, I think much of what this file includes is in winapp3.ini now
-
On 03/09/2020 at 08:12, Winapp2.ini said:
Yes, sorry! Version 1.5.x.y will be the next non-beta release, hopefully by this weekend. Most of the recent work on winapp2ool has been to make the docs easier to maintain, and I'm nearly through with that process
I regret saying this I haven't had time for winapp2ool as I am a teacher in NYC and things are... hectic to say the least.. lol
-
3 hours ago, SMalik said:
Looks like there is no option to edit the posts after a certain time.
The Edit option is in the overflow menu on the upper right corner of posts now
-
13 hours ago, siliconman01 said:
Is version 1.4.7550.20152 still considered "beta"?
Yes, sorry! Version 1.5.x.y will be the next non-beta release, hopefully by this weekend. Most of the recent work on winapp2ool has been to make the docs easier to maintain, and I'm nearly through with that process
-
-
Yes, you can call
winapp2ool.exe -2 -d -s
to download and trim the latest winapp2.ini from github without needing to interact with the menus at all
The winapp2ool docs are currently a little outdated but you can read more here: https://github.com/MoscaDotTo/Winapp2/tree/master/winapp2ool#command-line-arguments -
hey neat, this thread is a decade old
-
5.68 is another watershed version to be lauded as unupgradeable how could we forsake the
-
If you use a temporary-containers style of browsing in firefox (new containers spawned and destroyed per-tab-tree if the initial url isn't pre configured to open in a specific container already) take care that they're not being retained
I recently discovered that something had caused my multi-account containers to retain several hundred containers that were meant to be destroyed when their last tab had been closed. It was causing some severe overhead on startup and when opening new tabs until I removed them manually
-
On 01/06/2020 at 11:58, Winapp2.ini said:
I purchased a code signing certificate on May 16 to help with this issue and have not been verified yet
Beta versions (and all future release versions) of winapp2ool are now digitally signed. This should help prevent things like anti virus' deleting it from your machines or browsers blocking the download
-
2 hours ago, APMichael said:
@siliconman01 The AV vendors are really getting on my nerves. After weeks of silence they suddenly start flagging Winapp2ool again...
@godfreythemasterbaiter Thank you for the hint and the description.
Winapp2.ini update:
https://github.com/MoscaDotTo/Winapp2/commit/4fd8ec6ddf25251f7aebcbcf6acc47e49af870c7Winapp3.ini update:
https://github.com/MoscaDotTo/Winapp2/commit/0081c771f684d2465dda06d43baf4295e86aac7cI purchased a code signing certificate on May 16 to help with this issue and have not been verified yet
-
1 minute ago, siliconman01 said:
No, the one I get from the Beta download URL is 1.4.7427.18038.
Try a force clear of your browser cache or updating through winapp2ool beta. If you don't see an update notification, you can type forceupdate into the main menu to make winapp2ool update itself anyway
-
-
Unfortunately I can only go by VirusTotal and it currently shows clear.
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)
-
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=FalseUPDATE: 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
-
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
-
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!
-
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!
-
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.
-
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
-
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
Winapp2.ini additions
in CCleaner
Posted
I noticed some things:
RegEditX entry seems to contain RegKeys for RCrawler
Is there any reason we shouldn't merge the two Acrobat Distiller entries into one?
[Adobe Acrobat Distiller DC *] LangSecRef=3021 Detect=HKCU\Software\Adobe\Acrobat Distiller\DC FileKey1=%LocalAppData%\Adobe\Acrobat\Distiller DC|*.log FileKey2=%LocalAppData%\Adobe\Acrobat\Distiller DC\Cache|*.* RegKey1=HKCU\Software\Adobe\Acrobat Distiller\PrinterJobControl [Adobe Acrobat Distiller XI *] LangSecRef=3021 Detect=HKCU\Software\Adobe\Acrobat Distiller\11.0 FileKey1=%AppData%\Adobe\Acrobat\Distiller 11|*.log FileKey2=%AppData%\Adobe\Acrobat\Distiller 11\Cache|*.* RegKey1=HKCU\Software\Adobe\Acrobat Distiller\PrinterJobControl