Jump to content

APMichael

Experienced Members
  • Posts

    984
  • Joined

  • Last visited

Everything posted by APMichael

  1. Since we are trying to avoid duplicate Keys, I would suggest that we add a separate entry and remove the Keys from all CyberLink entries: [CyberLink Common Cache *] LangSecRef=3021 Detect=HKCU\Software\CyberLink Default=False FileKey1=%AppData%\CyberLink\MediaCache|*.*|RECURSE RegKey1=HKCU\Software\CyberLink\DSSharedMediaInfo\SharedInfoCache RegKey2=HKCU\Software\CyberLink\MediaCache\Data4 RegKey3=HKCU\Software\CyberLink\MediaCache\Thumbnail4 RegKey4=HKCU\Software\CyberLink\MediaCache5\Data5 RegKey5=HKCU\Software\CyberLink\MediaCache5\Thumbnail5
  2. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/0847286a1fa4285162d033fd2fbd2510edd63544
  3. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/3e191d5d00c465eae5c8eff2b1898c9cde05377e
  4. Thank you very much for your fast replies.
  5. Thank you for your fast reply. Ok, then I will change the FileKeys of the entry [Internet Cache *] as mentioned. (This will include the .ldb and .log files from "Default".)
  6. Thanks for your clarification. This 0000X.log file is also a database file. But we could change the FileKeys, as mentioned in my other post: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=298&tab=comments#comment-301811. This should work, because the other subfolders of "User Data" do not contain LevelDB files yet. Is that ok for you? Yes, after the installation the profile folder name is "Default". However, if you add an additional user, the profile folder name for that new user is "Profile 1" (and that also adds a folder named "System Profile"). If you are using the guest mode, the profile folder name is "Guest Profile".
  7. I think SMalik means that he wants to protect the profile folder, because there are other (not profile) folders that could contain usual log files (*.log). My suggestion would be to rename the existing entry to [LevelDB Logs *] and add a new entry [Logs *] with ExcludeKeys for the profile folders: FileKeyX=%LocalAppData%\Google\Chrome*|*.log|RECURSE ExcludeKeyX=PATH|%LocalAppData%\Google\Chrome*\User Data\Default\|*.* ExcludeKeyX=PATH|%LocalAppData%\Google\Chrome*\User Data\*Profile*\|*.* (As far as I know, Google Chrome names the profile folders "Default", "Profile X" or "XYZ Profile".)
  8. We cannot add the *.log files because all the *.log files are not usual log files. They are important database files! (I don't understand why Google chose this file extension for an important database file!?) The usual log files are only LOG and LOG.old. Please check the links provided by Winapp2.ini. The *.ldb and MANIFEST-* files are also database files. But if you are 100% sure that this database only stores traces, we could remove all database related files from the folder, e.g.: FileKey14=%LocalAppData%\Google\Chrome*\User Data\*|*.ldb;*.log;CURRENT;LOCK;MANIFEST-*;Network Persistent State;Origin Bound Certs (If you want to clean a LevelDB, you should always remove all related files.)
  9. Are the RegKeys 1-4 really useful? I never had this problem. Or should we split the RegKeys into separate entries like [MS Notepad *] and [MS Notepad Window Size*], because not everyone always wants to reset the window size?
  10. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/1a1ac67f7f89373deae283ffb4022adefa3359b9 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/c40255ec03cf0a64d915f76862bb2aed81bd4f6a
  11. Thank you very much for this important note. Yes, if the entry breaks the update function, it should be moved to Winapp3.ini.
  12. Thanks for your fast reply. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/83d58d505f25fee9c1937e7b76e9587372038a83 https://github.com/MoscaDotTo/Winapp2/commit/7207c52f72cbb7405ebab3a0c158d8d057ff0fe0
  13. Thank you for your revised and new entries. Own entry? Or should we add the FileKey to [Windows Subsystems *]?
  14. I think you misunderstood the post from Nergal. If you have checked "MyappName" at least once, CCleaner ignores the "Default=" value and uses the stored user settings instead. You can delete these user settings in the registry: - Close CCleaner (also Smart Cleaning, if enabled). - Open "regedit" and navigate to "Computer\HKEY_CURRENT_USER\Software\Piriform\CCleaner". - Delete the entry "(App)MyappName". Now CCleaner should respect the "Default=" value. The "Default=" values are only used for the preselection. If you have ever (un-)checked a cleaning rule, the "Default=" values are overwritten with the stored user settings. That is the desired behavior.
  15. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/3579f1321c50ef4ae55749384bda5eb9461bde14
  16. It is in Winapp2.ini already: [Auslogics Registry Defrag *]. If you additionally want to delete Registry backups, we could add this to Winapp3.ini. Or did you have an issue with the Winapp2.ini entry?
  17. The issue with the cleaning rule Chrome [Logs *] should now be resolved. Now the rule only deletes usual informational logs and not important database files anymore. (If you update the FAQ you should add the rule Chrome [Extensions Databases *], because this rule resets all extensions.)
  18. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/8ef6d450791bb1a788639f6a72ca0751d642ca13 https://github.com/MoscaDotTo/Winapp2/commit/18e82c6f5031bc6805b9f0776397da28a29e5701
  19. Strange! Only an older version of CCleaner had an issue that prevented disabling "Smart Cleaning". Are the checkboxes under "Smart Cleaning" still unticked? You could check if there is a startup entry for CCleaner under "Tools" > "Startup" > "Windows" and disable/delete it.
  20. As far as I know, CCleaner does not have a rule named "chrome logs". It seems that you are using a file for extended cleaning, like the file "winapp2.ini". You should check if there is an updated version of that file.
  21. Thanks for your reply and the information. Yes, the bug still occurs. But I found out that the bug depends on the window size. If the window has the standard size of 800x600 the bug occurs. If you change the window width to 802 (or wider) the bug doesn't occur anymore.
  22. Thanks for the new version. The following FileKey seems to be wrong: FileKey38=%SystemDirectory%\config\systemprofile\AppData\Local\Microsoft\CLR_v3.0_32|*.log|RECURSE I think it should be: FileKey38=%SystemDirectory%\config\systemprofile\AppData\Local\Microsoft\CLR_v2.0_32|*.log|RECURSE And sadly, the following two bugs are still not fixed: https://forum.piriform.com/topic/52696-ccleaner-beta-v548001/?tab=comments#comment-300227
×
×
  • Create New...

Important Information

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