Jump to content
Piriform Community Forums


  • Content count

  • Joined

  • Last visited

Posts posted by Andavari

  1. I'm using the newest CCleaner version as well, in my opinion it's not worth keeping an old version with those known bugs that could damage Windows (Font Cache cleaning, and Windows.old cleaning) as you're well aware and have been told about before.

    Perhaps give Chrome Portable by PortableApps.com a try instead of using the installed version, it should behave and fully exit when told to do so.

  2. Misspelled entry in winapp2.ini:
    [Geek Unistaller *]
    Detect=HKCU\Software\Geek Uninstaller
    FileKey1=%AppData%\Geek Uninstaller|*.log;*cache.dat

    [Geek Uninstaller *]
    Detect=HKCU\Software\Geek Uninstaller
    FileKey1=%AppData%\Geek Uninstaller|*.log;*cache.dat

  3. I never once had the issue before until just today, which was later on after Automatic Updates had installed KB4023057. After the update I restarted the laptop myself, since the update didn't request I do so. Then I used the laptop for a few minutes, and then closed the laptop lid.

    Came back about 1 hour later and there was some weird USB drive anomaly/failure where it wouldn't recognize or mount my USB 3.0 portable hard disk (it gave no prompts, nothing), and the USB stick plugged in only had a generic name but not the actual disk label. Oddly enough my USB mouse never had any issue during all of this.

    Fully remedied by restarting the computer again!

    Didn't give it much thought at the time, but I've sent them a bug report through Feedback Hub.

  4. You shouldn't take it personal in my opinion, yes nobody likes seeing cleaners they've took the time to make get removed or reduced in "effectiveness." but with that stated what's in winapp2.ini should be safe for the whole community instead of possibly causing an issue that not everyone will have the expertise to repair.

    That's why whenever I submit a cleaner I've made that's too aggressive for the community (mostly in the past with some Firefox cleaners) and would make someone furious and that would get rejected for submission or later removed I just neuter it from the get-go and then submit a safe version of it.

    It's another reason to sit on a cleaner we make instead of getting in a hurry to submit something without testing it more thoroughly, especially if it involves cleaning something built into Windows we may not know the full effect of.

  5. Most SSD manufacturers just use the compatibility that's already built into Windows (unless you find some ancient version of their software that may have had the Trim feature). You may need to find some third-party tool that can do it (if one exists I don't know) rather it be freeware or commercial, and then if it actually supports WinXP itself would be the next hurdle.

    Wouldn't it be so much simpler if the Trim command was just built right into the SSDs themselves and they'd automatically perform the Trim by themselves, then there'd be true support for older systems and even game consoles so the SSDs don't prematurely fail.

  6. New entry. Includes both Detect, and DetectFile because CCleaner's registry cleaner will remove the empty Detect= key HKCU\Software\APR.

    [Autoplay Repair *]
    DetectFile=%ProgramFiles%\Autoplay Repair\Autoplay Repair.exe

  7. CCleaner's registry cleaner not finding anything to remove does not mean your system has an issue in of itself, it doesn't mean anything in actuality. It's not indicative of CCleaner having a bug in regards to registry cleaning either, it just means it didn't find anything it deemed as invalid to remove.

    If you're trying to fix other system related issues it's probably best to completely avoid possible additional issues that registry cleaning in general can cause - this is with any registry cleaning tool. Reason being most registry cleaner's including the one in CCleaner never bother to actually fix anything whatsoever, whereas they have the potential of causing issues.

    Registry cleaner's that don't fix anything remove what they deem to be non-existent invalid references, now rather they're invalid or not has to be first investigated before allowing them to clean which has always been my philosophy when using any registry cleaner and even then after investigation some of what they want to remove should always be avoided, i.e.; like references pointing to Microsoft .NET Framework (which is pre-installed on Windows), Microsoft Office (especially if it's installed), etc.

  8. I've just discovered something inadvertently when I copied my own maintained winapp2.ini file to my mother's laptop, and it's a good thing I clicked Analyze first or I would've been reinstalling her installed version of Firefox Quantum.

    So I would say to anyone don't trust your own cleaners just because you've made them for your own personal systems and then expect them to work safely as intended on another system they've never been used on before. Especially if like me you primarily use the portable version of software because it has the potential to wreak havoc on another system that uses the installed version of a software.

    Since I use Firefox Portable I have a cleaner that will remove its AppData files if it ever crashes, I've used that cleaner and Firefox Portable for years. Now if that cleaner is ran against an installed version of Firefox it will damage it by incorrectly targeting files that should exist.

    This is my error that I luckily avoided (would've been a really bad screw up since I had Default=True)::(
    [Crash Cleanup *]
    Section=Firefox ESR Portable

  9. 6 hours ago, APMichael said:

    What a strange error! Since the file "Windows.edb" is not really crap (only if you have disabled the service "Windows Search", but this is not the system default), removing the FileKey should not be a problem.

    I'm wondering if some of the discoveries of things to remove from cleaners that cause issues would instead be better serviced by instead changing them into an ExcludeKey. The ideal behind this is if/when someone decides to "update" the cleaner it will be obvious they shouldn't add in something that's already being excluded. Just an ideal.

  10. 6 hours ago, CSGalloway said:

    Please share the batch script you mentioned.....

    Don't remember the download site for it, but since it has no copyright info inside it here you go:

    1. What it does: Repairs Cortana/Search in Windows 10 after a cleaning program unintentionally breaks the functionality.

    2. Copy+Paste this into Notepad:

    @echo off
    net stop wsearch
    REG ADD "HKLM\SOFTWARE\Microsoft\Windows Search" /v SetupCompletedSuccessfully /t REG_DWORD /d 0 /f
    del "%ProgramData%\Microsoft\Search\Data\Applications\Windows\Windows.edb"
    net start wsearch
    IF NOT %ERRORLEVEL%==0 (goto :wsearch) ELSE goto :END

    3. Save as a useful name such as:
    Reset And Rebuild Search Index (Requires Admin Priveleges).bat

    4. When using the .bat file right click and: Run as administrator

    5. After using the .bat file you must restart your computer for the repair to work.

  11. The computer being brand new however doesn't get you off the hook, there could in theory be a hard disk issue.

    Now if there is or isn't a hard disk issue I don't know, that's why there's tools like ChkDsk and hard drive confidence tests to take the guess work out. Then again it could just be a software issue such as something running that's interfering or Defraggler itself.

  12. 4 hours ago, APMichael said:

    We revised the entry [Cortana *] a few weeks ago because it always broke the search for settings. We fixed that by adding an ExcludeKey for a cache file ("SettingsCache.txt"). But now it looks like the other files ("AppCache###.txt") should not be deleted either. I think we should then exclude the entire folder ("\LocalState\DeviceSearchCache").

    (An easy way to restore Cortana: Right-click on the Cortana icon and click on "More" and then on "App Settings". Now click on "Reset" and wait a few seconds.)

    Does this look right to exclude that whole path you refer to?

    Couldn't get it to exclude using a path, however I got this to work as intended:

    Also the way you suggest to restore Cortana functionality does not work if Cortana is purposely disabled by the user, and the user is instead just using it as a normal local search, hence the reason I use a batch script to restore the functionality.