Jump to content

Andavari

Moderators
  • Posts

    22,289
  • Joined

Everything posted by Andavari

  1. Sometimes that can be caused because the cleaners for particular software have been updated which is also now cleaning too much or even possibly the wrong file. One way to narrow down which files should be inputted as a personal exclusion in your CCleaner configuration is to clean only a little bit at a time, such as (example): Only clean Nvidia (or just click Analyse so it lists what could be cleaned) to try and figure out exactly what file/files being cleaned is breaking the program. Some may be file exclusions, and some may be registry exclusions. Registry exclusions are far more tricky to figure out though because when CCleaner cleans registry MRUs (recently opened files) it doesn't list them at all, it only lists the physical files like logs, etc., it has cleaned. It will likely be time consuming to figure out what needs to be excluded when dealing with multiple programs like in your situation. That's why it's important to only clean a little bit at a time and don't use CCleaner as you normally would until you figure out what exactly to exclude on your system. Excludes can be added in CCleaner at: Options > Exclude
  2. You could always try other file recovery tools, if needing your files back is critical don't get locked into using just one program to recover them. As for them showing up as unrecoverable: Even if nothing is ever touched by the user on a drive after storing files on it that doesn't mean that operating systems aren't doing something in the background which can make recovery difficult and what Windows does can make recovery an issue. It's important to always have at least 3 backups of important files, with 1 copy being off-sight such as being left at a relatives house or in a safety deposit box, etc.
  3. My experience with CCleaner and attempting to uninstall Windows Installer installations from .MSI led to the final conclusion a long time ago (probably over a decade ago) that CCleaner shouldn't be used to uninstall those at all because things would act weird, buggy, or whatever, and instead revert back to using what's built into Windows to uninstall them.
  4. I've successfully used Recuva on a floppy diskette maybe 10+ years ago, it got every file back that was accidentally deleted, but there weren't any bad sectors to deal with. With bad sectors your mileage may vary, if there aren't any files stored where there are bad sectors you may be able to get the files back, but floppies far too easily start getting bad sectors while just sitting around and not being used - the Earths magnetic field can't be all that good for them either over several years.
  5. They've actually earned it when it comes to me, and the long time usage from before version 4. I can't count how many times something has broken Windows XP (from back in the day with messed up Windows updates, to extra buggy or malicious in my views uninstallers that wanted a reboot and deleted too much) and Macrium has always saved the day in under 10 minutes. On that old XP system the last OS install was at the beginning of 2009. It has even saved my Win10 laptop a number of times from buggy Intel iGPU drivers corrupting the Windows 10 install, and Windows updates rearing it's ugly bug infested head a couple of times, etc.
  6. Any drive that has the recovery media on it needs to be updated each time Macrium Reflect is updated. With the free version there aren't too many updates remaining though. It will probably eventually stop working correctly with Windows due to becoming outdated. I will likely buy a license when that time arrives since I've been using it for free for a very long time (well over a decade), and the one and only hiccup I've ever had with it was what I posted as post 1 in this topic.
  7. Updated. Added: C:\Windows\%LOCALAPPDATA%\CrashDumps Added With FileKey4: FileKey4=%WinDir%\*LOCALAPPDATA*\CrashDumps|*dmp* Notes: * Has to be written as *LOCALAPPDATA*, since using %LOCALAPPDATA% won't work with there already being a leading path with %WinDir% in it. * Seems to only store Microsoft Defender Antivirus ("Windows Defender") crash dumps with names like these for example: MsMpEng.exe.4792.dmp, MsMpEng.exe.4804.dmp [Windows Error Reporting *] LangSecRef=3025 Detect=HKCU\Software\Microsoft\Windows\Windows Error Reporting FileKey1=%LocalAppData%\CrashDumps|*dmp* FileKey2=%LocalAppData%\PCHealth\ErrorRep\QSignoff|* FileKey3=%WinDir%\LiveKernelReports|*.dmp|RECURSE FileKey4=%WinDir%\*LOCALAPPDATA*\CrashDumps|*dmp* FileKey5=%WinDir%\pchealth\ERRORREP|*|RECURSE FileKey6=%WinDir%\pchealth\helpctr\DataColl|*.xml FileKey7=%WinDir%\pchealth\helpctr\OfflineCache|*|RECURSE FileKey8=%WinDir%\System32\config\systemprofile\AppData\Local\CrashDumps|*.dmp|RECURSE FileKey9=%WinDir%\System32\config\systemprofile\AppData\Local\CrashDumps|*dmp* FileKey10=%WinDir%\System32\config\systemprofile\Local Settings\Application Data\CrashDumps|*.dmp|RECURSE FileKey11=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\CrashDumps|*.dmp|RECURSE FileKey12=%WinDir%\SysWOW64\config\systemprofile\Local Settings\Application Data\CrashDumps|*.dmp|RECURSE RegKey1=HKLM\Software\Microsoft\Windows\Windows Error Reporting\FullLiveKernelReports|LastFullLiveReport RegKey2=HKLM\Software\Microsoft\Windows\Windows Error Reporting\FullLiveKernelReports\win32k.sys RegKey3=HKLM\Software\Microsoft\Windows\Windows Error Reporting\LiveKernelReports\win32k.sys RegKey4=HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps RegKey5=HKU\.DEFAULT\Software\Microsoft\Windows\Windows Error Reporting\Debug|StoreLocation
  8. Macrium Reflect Free Update v8.0.7783 Breaks Macrium Recovery If you allow Macrium Reflect Free to update itself to version 8.0.7783, and also update the drive C:\ Boot Menu you need to test that your system can still boot successfully into the Macrium Recovery boot media. On my system the update completely broke the ability to boot into Macrium Recovery. How To Fix And Re-Create The Macrium Recovery Boot Media: 1. In Macrium Reflect Free uninstall the boot menu. 2. Open and delete everything inside of "C:\Boot" that's where Macrium Reflect Free downloads, installs, and stores the Microsoft Windows PE boot media files ("WIM file, etc.,"). 3. Restart Windows. 4. In Macrium Reflect Free choose a Microsoft Windows PE boot media for it to download and install, and select for it to create the boot media on the C:\ drive. 5. It's now important to test that it actually works by booting into Macrium Recovery. Optionally: Create the boot media on an external USB drive, such as a USB Flash Drive. Or onto a USB HDD / USB SSD (that has a small first partition up to 2GB in size just for the boot media). Having it on a USB drive is another usable source to boot into Macrium Recovery. Test that it also works. Note: This would need to be made first and tested to see if it works, if it isn't made first it seems as though it's bypassed and the booting instead switches to the boot media already created and installed on drive C:\.
  9. If anyone cleans Windows Update logs in their own personal winapp2.ini file there's another area to clean them from now also: %CommonAppData%\PLUG\Logs|*.*|RECURSE I had a ton of stuff in there.
  10. If CCleaner's settings are saved in an .INI file "ccleaner.ini" change the warning settings from False to True in it and re-save it. I'm guessing it may be this one (could be another one altogether though), example: ShowEdgeCleanWarning=False Change to: ShowEdgeCleanWarning=True If that's just it, no need to uninstall then reinstall, or change all the settings. Those False/True settings should be in the Windows Registry if that's where CCleaner's settings are stored, but I have no advice on changing those since I only use the very easily editable .INI file ccleaner.ini.
  11. Two more. Don't know if it's from Microsoft Edge Chromium, or Windows Updates, or something else. Both created on November 8, 2023 within 7 minutes of each other. Contains telemetry data: C:\ProgramData\profile_count_updates.json Was empty: C:\ProgramData\UpdateLock-updates
  12. That explains why I couldn't find it, being it's a wildcard entry, and my winapp2.ini may have been outdated, don't know. BUT (a big BUT), I don't like deleting "REMOVESELF" cache folders, instead I clean them out, due to past issues of deleting them outright. How I clean that folder: %LocalAppData%\Microsoft\Edge*\User Data\GraphiteDawnCache|*.*|RECURSE
  13. If you use Custom Clean in CCleaner, otherwise this won't work at all: 1. You could input an exclude for the path. To figure out what CCleaner is deleting instead run Analyze first instead of Run Cleaner. Once you see what it's going to delete input the path/location in: Options > Exclude 2. Download a video so that it gets saved on the system. 3. Run CCleaner to make sure the exclude is working.
  14. That folder had cached files in it on my system. When looking at winapp2.ini online (direct download version), it didn't clean that folder, there was no reference of it. I also have Microsoft Edge Chromium (latest version). Edit: That "GraphiteDawnCache" folder was a relatively new creation, the creation stamp date states "Tuesday, ‎August ‎22, ‎2023", and I know it was not in there for very long because once in a while I go about snooping in there to see what they've added.
  15. See here for what they might do sometime in CCleaner v6.0's lifespan: https://community.ccleaner.com/topic/60017-share-your-ideas-for-ccleaner-60/?do=findComment&comment=331669
  16. My guess is it's likely the phoning home telemetry during the startup of their software that causes the very long delay. For example don't have an active Internet connection when starting their recovery software Recuva and it will take too long to open. Close it and then re-do the test again, and yet again it takes just as long to open the second time.
  17. The only time that would be necessary is when retiring an SSD to either stop using it when upgrading to a newer faster SSD, retiring an old SSD altogether since it's nearly out of life/reliability based on S.M.A.R.T. analysis, or to repurpose an old SSD with some life remaining for another system. Such as an old system could for example still greatly benefit from even a old now considered very slow SATA2 3 GB/s SSD. The wiping sanitation would be done with the official SSD manufacturer toolbox to wipe the drive clean - not with 3rd party cleaning tools.
  18. I found a new cache path that needs cleaned for Microsoft Edge Chromium: %LocalAppData%\Microsoft\Edge*\User Data\GraphiteDawnCache
  19. Sometimes just installing Windows over Windows will fix a ton of stuff, plus the settings and programs will remain. I don't particularly know about "borked" drivers being installed as has happened here though (I've only ran into that once with Intel iGPU drivers that corrupted a ton of stuff), so uninstalling those first may or may not help.
  20. Make Sure It's Enabled: 1. Open CCleaner. 2. Scroll all the way to the bottom. 3. Make sure 'Custom Files and Folders' is enabled/ticked, if it isn't custom cleaning won't work at all:
  21. Group Policy Editor ("GPE") is only in Win10/11 Pro, albeit there are ways to make it install and work on Home Editions because it's technically already installed on those systems too. I've had that box toggled to Enabled in GPE for ages at this point (so long ago I forgot when I did it since back then I didn't write a comment like "Enabled on: <date, time>"), and Windows ignores it. Problem with GPE is some things can get outdated and no longer used.
  22. May also try right-clicking the CCleaner shortcut, and choose: Run as administrator
  23. They'll eventually update CCleaner to clean it, they're always going to be playing catch up with changes to web browsers however.
  24. Didn't know anything about that but searching reveals there's an AVG version and Avast version - same company btw. Probably best to ask on either AVG or Avast since they're the people making it depending upon which one you installed since this forum is for CCleaner specifically.
×
×
  • Create New...

Important Information

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