Jump to content

APMichael

Experienced Members
  • Posts

    984
  • Joined

  • Last visited

Everything posted by APMichael

  1. Piriform only supports the cleanup rules built into CCleaner. The Winapp2.ini is only a tolerated extension of CCleaner users. If you deviate from a standard system and redirect folders, it is questionable whether Piriform will correct this. You will probably have no choice but to use your own Winapp2.ini in which you rewrite the problematic cleanup rules. Correct, CCleaner does not show deleted folders, it never has. Obviously, users are not interested enough. But there have been one or two requests for it here. But Piriform has not yet implemented it. You can possibly make a post in the "CCleaner Suggestions" forum.
  2. As far as I can remember, this behavior has always been like this. If a folder is empty (and no longer contains any files), it is always deleted by REMOVESELF. The exclude rule only protects the contents of a folder, but not the folder itself. However, deleting an empty folder should not be a problem in most cases. But if it is, the FileKeys of the Winapp2.ini entry must be adjusted accordingly. It is therefore not really a bug, but rather an overly "aggressive" FileKey.
  3. Great! I'm glad I could help.
  4. DetectOS uses the version number, as Windows 11 also has a version number starting with 10, the build number must also be specified. This is how it should work: DetectOS=|10.0.21999 From version 10.0.22000 it is Windows 11: DetectOS=10.0.22000|
  5. The entry was moved to Winapp3.ini at the time, as it can cause problems with a few extensions. Winapp3.ini, Version: 220615: [Edge Indexed Database Extended *] Section=Dangerous Edge Chromium DetectFile=%LocalAppData%\Microsoft\Edge* Warning=This may cause some extensions to not work as intended. FileKey1=%LocalAppData%\Microsoft\Edge*\User Data\*\IndexedDB|*.*|RECURSE
  6. @nukecad: Many thanks for the good and detailed explanation. I hope Leandro can solve the problem with it.
  7. It could be the "Performance Optimizer" ... - Check in CCleaner under "Performance Optimizer" if the affected applications are in sleep state. If so, wake them all up again. ... or the antivirus program. - Which antivirus program do you use? Perhaps Avira? If so, the following folder should be excluded: "C:\Windows\Temp\sentry_temp"
  8. You can try disabling the following cleanup rules: CCleaner built-in: Windows > Windows Explorer > [Network Passwords] Winapp2.ini (v230901): Applications > Windows > [Windows Credential Manager Saved Credentials *] Applications > Windows > [Windows Mail and Calendar *]
  9. There are a few extensions that lose their data after the "Internet Cache" has been cleared. Please try whether one of these workarounds works for you: https://community.ccleaner.com/topic/32310-winapp2ini-additions/?do=findComment&comment=336417 https://community.ccleaner.com/topic/32310-winapp2ini-additions/?do=findComment&comment=310357
  10. This issue has been fixed. Thank you for the quick fix!
  11. Thank you very much for your answer and the information. I have tried it with both releases of version 6.18. I can recreate the crashes at any time by simply deleting the "Piriform\CCleaner" registry key under "HKLM\SOFTWARE". I am aware of Piriform's lack of interest in bug fixes. There are still numerous reports of problems and bugs here in the forum that have never been fixed. JMHO: It's a real shame that CCleaner is being bloated with one unnecessary feature after another and that the basic idea of CCleaner has been completely lost.
  12. On a clean system on which "CCleaner" has never been run, "CCleaner v6.18 Portable" crashes immediately (not even the GUI appears). However, if an HKLM registry key from a previous version is present on the system, "CCleaner v6.18 Portable" works without errors.
  13. The following FileKey matches the folder and removes it: Version: 230901 [Microsoft Edge Caches *] FileKey17=%LocalAppData%\Microsoft\Edge*\User Data\*Cache*|*|REMOVESELF
  14. It seems that CCleaner is now ignoring symbolic links. Earlier versions followed these and were able to clean up "redirected" folders. The current version no longer does this. Is this intentional or is it a bug?
  15. As far as I know, @Winapp2.ini has abandoned the "Microsoft Store" category and sorted the applications into their respective categories. (I guess it has already been questioned why the "Microsoft Store Apps" were given their own category, although they could have simply been sorted into the existing categories.) The entries are still there, but @Winapp2.ini has merged some of them. The easiest way to find them is to search for "DetectFile=%LocalAppData%\Packages\".
  16. The email seems to be probably genuine: https://www.heise.de/news/MOVEit-Sicherheitsluecke-Auch-Kunden-von-CCleaner-betroffen-9345032.html (Report from a trusted German website.)
  17. No, I just check the support forum from time to time, as possible problems with Winapp2.ini are also reported there.
  18. This is already cleaned up by CCleaner's built-in cleanup rule [Thumbnail Cache]. Sometimes the files are locked, but basically they can be cleaned with it.
  19. I would strongly advise against searching for or even deleting duplicate files in the system folders, such as "Program Files" or "Windows". Many programs and also Windows unfortunately have the habit of creating files multiple times, however, in the vast majority of cases deleting these files leads to damage, so that a repair or reinstallation becomes necessary.
  20. JFYI: @Winapp2.ini has released another Winapp2.ini update (v230901).
  21. @Winapp2.ini Thank you for your reply.
  22. I don't have time to test it at the moment, but I suspect that deleting the entire contents of the "\AC\" subfolder is too aggressive. The previously separate FileKeys for "\AC\" have been merged into one FileKey in the overhauled version. If I remember correctly, the login of an app was stored in the subfolder "\AC\Microsoft\Crypto\", this should be excluded. For the problem with the deleted profile picture, I have not yet been able to locate a suspicious entry. To narrow down the problem someone would have to figure out which entry, presumably a [Windows ... *] entry, is responsible for the deletion.
  23. Does this problem occur only in a web browser? If so, the following cleanup rules might be problematic: ["Browser" Cookies *] ["Browser" Login Data *] Unfortunately, I have no more ideas at the moment.
×
×
  • Create New...

Important Information

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