Jump to content
CCleaner Community Forums

MeganCCleaner

Admin
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MeganCCleaner

  • Rank
    CCleaner Staff

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Would you be willing to disable the legacy version of Edge, using the following steps, to see if this would be a viable workaround? Open the "Run" dialog in Windows (On the keyboard, hold/release the Windows () and "R" keys simultaneously) Type: C:\Windows\SystemApps\ > click OK Right-click on the folder named as "Microsoft.MicrosoftEdge_8wekyb3d8bbwe" Click "Rename" Type "LEGACY" at the end of the folder name (i.e. Microsoft.MicrosoftEdge_8wekyb3d8bbweLEGACY) > click Enter
  2. Both of these log files show that it is taking an extended amount of time to clean the Legacy version of Edge, whereas the timestamps indicate that the Chromium version of Edge is being cleaned much more quickly. Specifically, I believe this is attributed to the following: This means that there was 101 failed attempts to unlock the ESE/JET Blue database (i.e. the spartan.edb file) - Furthermore, I saw the following error in both of the logs: I'll be investigating this but meanwhile, can you please see if the problem persists when running CCleaner with administrative pri
  3. Thanks for verifying that. I'll ask our support team to contact you now. They'll send an email from support@ccleaner.com.
  4. Thanks for sharing that. This crash event occurred in 5.68.0.7820 of CCleaner. Do you see any similar events associated with more recent versions of CCleaner - v6.69-v5.71? Also, has this problem persisted in the new version of CCleaner we released today, v5.72? If so, would our support team have your permission to contact you directly via email, using your forums account address?
  5. To help us investigate further, can you please post the log file that is created when running CCleaner in debug mode, using the following steps? Open the "Run" dialog in Windows (On the keyboard, hold/release the Windows () and "R" keys simultaneously) Type: CCleaner.exe /debug > click OK When CCleaner opens, use Custom Clean to replicate the problem Close out of CCleaner Afterwards, a log file will be generated in the C:\Program Files\CCleaner folder and it will be named in the format of "CCleaner_[version]_[date]_[time].log". Please attach this file.
  6. That's an excellent point and something I had not previously considered; it does seem as though if Smart Cleaning crashed without cleaning any 'junk' files whatsoever, and a manual 'junk' file cleaning operation had not been performed afterwards, the same amount (likely more) 'junk' files would still exist, therefore Smart Cleaning would run/crash again immediately upon being relaunched. The only possible explanation I could provide outside of that would be if a certain amount of junk files were successfully removed via a manual cleaning operation, or via Smart Cleaning before the 'crash
  7. I'm curious if this is happening as a result of CCleaner crashing during the automated cleaning operation. Are you able to find any crash related events for CCleaner when reviewing the Event Viewer Application logs, using the following steps? Open the "Run" dialog in Windows (On the keyboard, hold the "Windows" ( ) and "R" keys simultaneously) Type: eventvwr.msc > click OK Expand "Windows Logs" > click Application From the Menu Bar, click Action > Find... Type "CCleaner" > click "Find Next" Please continue to click on the "Find Next" button to
×
×
  • Create New...