Jump to content
CCleaner Community Forums

Winapp2.ini

Beta Testers
  • Content Count

    6,393
  • Joined

  • Last visited

Community Reputation

0 Neutral

2 Followers

About Winapp2.ini

  • Rank
    Friendly neighborhood addon manager
  • Birthday 25/01/1993

Contact Methods

  • Website URL
    http://www.mosca.to
  • ICQ
    0

Profile Information

  • Gender
    Not Telling
  • Location
    Long Island, New York
  • Interests
    Sleeping

Recent Profile Visitors

7,010 profile views
  1. 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
  2. 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
  3. 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?)
  4. 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
  5. @dvdbane this should be fixed in the latest beta build, sorry it took so long!
  6. 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.
  7. Perhaps a check for wildcards (and semicolons) in ExcludeKeys with the FILE switch will suffice
  8. https://github.com/MoscaDotTo/Winapp2/#how-to-use-winapp2ini-for-the-following-cleaners
  9. This is an error, I'll look into it when I've some time this week
  10. 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.
  11. 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
  12. @dvdbane Do the keys that are not in wow64node exist on your system too?
  13. Thanks for pointing this out, I'll look into it when I get some time
  14. It may be worth looking into the fact that although Easy Clean doesn't support winapp2.ini, it does seem to be doing expensive work when a winapp2.ini file is present
×
×
  • Create New...