Jump to content
CCleaner Community Forums

Winapp2.ini

Beta Testers
  • Content Count

    6,406
  • Joined

  • Last visited

Everything posted by Winapp2.ini

  1. I purchased a code signing certificate on May 16 to help with this issue and have not been verified yet
  2. 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
  3. The hash of your copy of winapp2ool is different from the one I posted, are you using the latest version? 1.4.7427.18862
  4. 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)
  5. I can't reproduce the behavior described in the update
  6. 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
  7. 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!
  8. 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.
  9. This hasn't shown up on VirusTotal yet but I'll submit it to them through their False Positive page, thanks for the TrojanID
  10. 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
  11. 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
  12. They're being used by the Connected Devices Platform (user) service. Stopping it should allow the files to be deleted. Not sure if you'd need to stop the parent service (Connected Devices Platform) too
  13. I think this might just be a build configuration issue, I'll tinker with visual studio and see if I can get it built correctly
  14. DeleteMe keys are definitely caused by winapp2ool, I'll look into it! the beta version supports keys without a value so it may be worth checking out whether that fixes the issue Edit: This issue is not present in the beta, but it WILL break any intended functionality of the LCD keys which are not formatted the same way as other keys (though if I had to guess this is a ccleaner bug?)
  15. wow! does this build work? https://github.com/MoscaDotTo/Winapp2/blob/Branch1/winapp2ool/winapp2oolXP.exe I thought it might be a quick fix so I just targeted that one change, this version of winapp2ool xp may be otherwise unpolished. if things seem weird let me know, and definitely let me know if it crashes still
  16. @dvdbane this should be fixed in the latest beta build, sorry it took so long!
  17. You can try running the Trim function of winapp2ool to rid yourself of these entries, however if CCleaner is detecting them and showing them to you, it means the removed software left whatever aspect of itself winapp2.ini is using to detect it. You have two options for ridding yourself of these "leftover" entries: manually delete the entry from winapp2.ini (be aware that it may return if the detect criteria are still present on the computer - which it sounds like they may be!) or manually delete the detect criteria from the computer. This will prevent CCleaner from detecting the entry as valid and will cause winapp2ool to actually Trim these entries out of your file after you've done it.
  18. Perhaps a check for wildcards (and semicolons) in ExcludeKeys with the FILE switch will suffice
  19. https://github.com/MoscaDotTo/Winapp2/#how-to-use-winapp2ini-for-the-following-cleaners
  20. This is an error, I'll look into it when I've some time this week
  21. Generally what I expected, the limitations of the (front end) scripting interface are pretty apparent when you consider some of the problems we try to tackle with winapp2.ini (and increasingly lean on code generation from winapp2ool to handle). barring some major rewrite of their ini interface, i would expect increasingly many future additions to the application to rely on these.
  22. The changelogs used to be more specific about winapp and winsys changes. the best option is to diff the built in ini files between versions
×
×
  • Create New...