Jump to content

Winapp2.ini

Beta Testers
  • Posts

    6,420
  • Joined

  • Last visited

Posts posted by Winapp2.ini

  1. I noticed some things:

    RegEditX entry seems to contain RegKeys for RCrawler
     

    [RegEditX *]
    LangSecRef=3024
    Detect=HKLM\Software\DCSoft\RegEditX
    RegKey1=HKLM\Software\4Developers\RCrawler\History
    RegKey2=HKLM\Software\4Developers\RCrawler\Settings|LastSearch
    


    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

     

  2. 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 :)

  3. 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

  4. 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 :)

  5. 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

  6. 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

  7. 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/4fd8ec6ddf25251f7aebcbcf6acc47e49af870c7

    Winapp3.ini update:
    https://github.com/MoscaDotTo/Winapp2/commit/0081c771f684d2465dda06d43baf4295e86aac7c

    I purchased a code signing certificate on May 16 to help with this issue and have not been verified yet

  8. 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

  9. 49 minutes ago, siliconman01 said:

    VirusTotal is showing Kaspersky and ZoneAlarm flagging Winapp2ool.exe as a trojan.

     

    VirusTotal.png

    The hash of your copy of winapp2ool is different from the one I posted, are you using the latest version? 1.4.7427.18862

  10. 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

  11. 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

  12. 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!

  13. 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!

  14. 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.

  15. 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

  16. 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

×
×
  • Create New...

Important Information

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