Jump to content
Piriform Community Forums

Winapp2.ini

Beta Testers
  • Content count

    6,363
  • Joined

  • Last visited

Everything posted by Winapp2.ini

  1. Winapp2.ini additions

    Welcome! *** Please Read *** The entries contained in winapp2.ini are not endorsed or supported in any way by the developers of CCleaner. This file is very large in its complete form and can cause significant delays when launching CCleaner. You can tailor the file to your system configuration and optimize CCleaner's launch time using winapp2ool's Trim module. While we do our best to ensure that submitted entries are not harmful, it is possible that some entries can impact the normal functionality of your system or applications. Winapp2.ini is provided "as is" and as such, neither I nor Piriform hold any liability for damage done to your machine in the event of an issue. If you have any questions, comments, concerns, or issues, please either file an issue on GitHub or make a post in this thread. *** Thank you *** GitHub Direct Download Enjoy! Notes: Now available: winapp2ool v1.0 Looking for old content? Our litany of old scripts/programs have been replaced with functions in winapp2ool. Check it out!
  2. Winapp2.ini additions

    This would affect the "Microsoft.XboxOneSmartGlass_8wekyb3d8bbwe" package, is it part of the Xbox app too?
  3. Winapp2.ini additions

    Happy holidays!
  4. Winapp2.ini additions

    the tools folder and its now-deprecated contents are also removed from the repo, with the exception of the winappool executable and its version file for watershedding.
  5. Winapp2.ini additions

    winapp2ool is released! 1.0 https://github.com/MoscaDotTo/Winapp2/releases/tag/v1.0 Users of the beta should be able to update from their old builds to a watershed beta build (0.99) which should then prompt them to update to 1.0 (this is necessary because the files have moved around on the repo with this release). Alternatively, you can simply download the 1.0 build from the release page here. Thank you for all your feedback over the last year on winappdebug, ccinidebug, and winapp2ool as a whole
  6. Winapp2.ini additions

    I've made available a draft of a readme for winapp2ool.exe that should apply to the upcoming 1.0 release. It is not entirely accurate for 0.85 which is the current master version on the GitHub https://github.com/MoscaDotTo/Winapp2/blob/73f02f7009a1f2123194d080bed34eb4b7617cdd/winapp2ool/Readme.md
  7. Winapp2.ini additions

    Off to the removed entries.ini with them!
  8. The Firefox/Mozilla Thread

    I understood this to mean to the new doorhangers calling attention to features like content blocking, I use nightly and haven't seen any advertisements (yet..?)
  9. Winapp2.ini additions

    A new winapp2ool for your consideration: https://github.com/MoscaDotTo/Winapp2/pull/318/commits/976dd4c0885ba3d47e04330b062956dc2e8f5e75
  10. Winapp2.ini additions

    The LevelDB Logs generated by Google Chrome extensions are not logs in the conventional sense we usually approach with intention to delete. They hold buffer data for the LevelDB storage. https://github.com/google/leveldb/blob/master/doc/impl.md https://github.com/MoscaDotTo/Winapp2/issues/320
  11. Winapp2.ini additions

    I think these FileKeys should be folded into either Windows Logs * or Windows Subsystems * rather than have their own entry, good find
  12. Winapp2.ini additions

    A new version of winapp2ool.exe is available for testing (not yet pushed to master) Should be of particular interest to WindowsXP users, as there is now a version that should work on your system. Please let me know if anything jumps out as super broken. https://github.com/MoscaDotTo/Winapp2/pull/318
  13. Winapp2.ini additions

    This error wasn't happening in my development environment (probably due to the nature of debugging applications) but it should be fixed in the next winapp2ool update. The application is intended to be usable when offline (with the exception of online functions) If using .NET 4.5.2 you should also see a message on the menu informing you that the tool requires .NET 4.6 but 4.6 is only required to use TLS 1.2 for downloading the executable. Everything else should work as expected
  14. Winapp2.ini additions

    I think items associated with VirtualStore locations are related to how Windows handles sandboxing / security when the UAC is enabled.
  15. Winapp2.ini additions

    Are the files process locked?
  16. The Firefox/Mozilla Thread

    Chrome has a similar feature that I've noticed but never seen discussed, so does Windows Explorer! I think this is something Microsoft is trying to take on as a UX problem (ie. unexpected restarts interrupt a user's workflow in a very destructive way) Timeline on Windows 10 and the upcoming (or released? I'm not sure) "Sets" feature I've seen talked about seem to be about remembering the context of your open applications and restoring them when appropriate.
  17. Winapp2.ini additions

    At this point yes, the features are mostly in their final state under the new menu system. I'll be working on creating documentation for it all soon. On a related note, I have intention to create likely one more module that executes combinations of the other modules tasks, so simplify the tool further.
  18. Winapp2.ini additions

    Winapp2ool has been (officially) updated to v0.85beta, existing previous versions should inform users of this.
  19. Winapp2.ini additions

    I created a "redux" version of Trim called TrimXP which targets .NET Framework 4: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/TrimXP This should be useful to anyone on WindowsXP who cannot otherwise run winapp2ool due to the .NET 4.6 Requirement The only concern I have is that I have never tested environment variable expanding on WindowsXP and don't know how/if some will work.
  20. Winapp2.ini additions

    A build of winapp2ool.exe with this fixed is available: https://github.com/MoscaDotTo/Winapp2/pull/245 It's not yet on the master as I've made significant changes to the code and want to make sure everything is still functional before pushing. Everything in my tests seemed OK though
  21. Winapp2.ini additions

    This is a bug (oversight regarding expanding wildcards) in Trim and will be fixed in an upcoming major update to the tool Thanks for pointing this out
  22. Winapp2.ini additions

    I think it'd be a better user experience to use a tool like Everything to do broad recursive searches for filetypes
  23. Winapp2.ini additions

    300 posts? There's over 7000! (but I suppose you probably meant pages) I don't think the thread needs cleaning. That's a lot of work for moderators and now that winapp2 itself is on GitHub it's a lot easier to track which changes actually make it into the file (when I was maintaining it alone and by hand, any changes I missed would be lost to the ages unless someone specifically audited for those changes and pointed out that I'd missed them). Overall I think that it'd be fitting for winapp3 contributions to be kept exclusively on GitHub. This is the winapp2 thread, and I think it'd be less confusing for everyone if it stayed that way.
  24. Winapp2.ini additions

    I don't think winapp3 is substantive enough yet to warrant its own thread or really even much discussion on this one besides update notifications. Any discussion about it is likely best kept to GitHub for the sake of keeping this thread on topic for now.
  25. Winapp2.ini additions

    This is the intended behavior. I had been working on finding unneeded parameterizations (eg log*.txt;log.txt -> log.txt is not needed because log*.txt covers it) but I didn't complete that work yet so I had intended to disable it. In the meanwhile, any wholly duplicate parameters should be caught properly by WinappDebug. Anything with wildcards is hit/miss (mostly miss) still. It should be noted that those errors are actually accurate in your output FileKey1=%CommonAppData%\CanonBJ\IJPrinter\CNMWindows|drvlog*;drvlog*.*;plmlog*.*;plmlog.*|RECURSE between plmlog*.* and plmlog.*, only plmlog*.* is needed
×