Andavari

I remember the update memory hog issues on XP, interesting that they can't get it right in newer oses this long going. On XP one serious hog was when it would update the .NET Framework with security patches - like every single time, damn thing took forever (45 minutes or longer for me) with high CPU usage, etc.

Like a cool down function. I've seen something like that in Exact Audio Copy when ripping bad audio CDs to rest the drive.

Another exception is by using the winapp2.ini file, that's how I clean Firefox Portable and SRWare Iron portable which aren't on my C:\ system drive.

Been discussed before, and people have asked for it to be cleaned, but it's supposedly not safe.

Instead download here (worth bookmarking too): http://www.piriform.com/ccleaner/builds We have no control over the practices of a third-party download site.

Making corrections to [AVG Protection*] since it has FileKey number errors starting after FileKey7. ---------------------- Corrections: [AVG Protection*] LangSecRef=3024 Detect=HKLM\SOFTWARE\AVG\AV Default=False FileKey1=%CommonAppData%\Avg\AV\Antispam|*.tmp;*.tmp1;*.tmp2;*.gz FileKey2=%CommonAppData%\Avg\AV\SetupBackup|*.*|REMOVESELF FileKey3=%CommonAppData%\Avg\log\AV16|history.xml;*.log;*.log.*;*.log.lock FileKey4=%CommonAppData%\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey5=%CommonAppData%\MFAData|msistorg.dat.bkp;public_installation_log.xml FileKey6=%CommonAppData%\MFAData\logs|*.* FileKey7=%CommonAppData%\MFAData\pack|*.* FileKey8=%LocalAppData%\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey9=%LocalAppData%\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey10=%LocalAppData%\AvgSetupLog|*.*|REMOVESELF FileKey11=%LocalAppData%\MFAData\logs|*.* FileKey12=%ProgramFiles%\AVG\Av|updatecomps.bak;*.old FileKey13=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\av16\temp|*.* FileKey14=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey15=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey16=%WinDir%\System32\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF FileKey17=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\av16\temp|*.* FileKey18=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey19=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey20=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF ---------------------- Old, with errors (skips from FileKey7 to FileKey9, without any FileKey8): [AVG Protection*] LangSecRef=3024 Detect=HKLM\SOFTWARE\AVG\AV Default=False FileKey1=%CommonAppData%\Avg\AV\Antispam|*.tmp;*.tmp1;*.tmp2;*.gz FileKey2=%CommonAppData%\Avg\AV\SetupBackup|*.*|REMOVESELF FileKey3=%CommonAppData%\Avg\log\AV16|history.xml;*.log;*.log.*;*.log.lock FileKey4=%CommonAppData%\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey5=%CommonAppData%\MFAData|msistorg.dat.bkp;public_installation_log.xml FileKey6=%CommonAppData%\MFAData\logs|*.* FileKey7=%CommonAppData%\MFAData\pack|*.* FileKey9=%LocalAppData%\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey10=%LocalAppData%\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey11=%LocalAppData%\AvgSetupLog|*.*|REMOVESELF FileKey12=%LocalAppData%\MFAData\logs|*.* FileKey13=%ProgramFiles%\AVG\Av|updatecomps.bak;*.old FileKey14=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\av16\temp|*.* FileKey15=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey16=%WinDir%\System32\config\systemprofile\AppData\Local\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey17=%WinDir%\System32\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF FileKey18=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\av16\temp|*.* FileKey19=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\log\av16|history.xml;*.log;*.log.*;*.log.lock FileKey20=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Avg\log\fmw1|*.log;*.log.*;*.log.lock FileKey21=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF

The cleaning part is fine for junk files, I however avoid cleaning the registry on Win10 systems.

The way Win10 adds files back in immediately after running CCleaner it's of no surprise that there's always a level of unavoidable fragmentation and I'm not referring to locked in-use files, just the rubbish that Win10 relentlessly creates.

There's also the Portable ZIP version, doesn't include any installer whatsoever: http://www.piriform.com/ccleaner/builds

Installing a new version in the past has never removed an older version.

Can't reveal exact instructions (I'm sure you can find those on the web) because I don't have that laptop in my possession. I think it was in the Display Settings area somewhat similar to how you get there in XP by right-clicking to pull it up, although I don't know if I'm remembering correctly since that was months ago.

The only way I got the text size view-able without using binoculars on my mother's Win10 Dell laptop was to reduce it from 1080p HD down to 720p HD - much easier to do than fiddling with various other settings.

Last time I tried Avast which was many years ago it used to detect one of the Macrium Reflect .MSI files located in "C:\Windows\Installer", I had to exclude it.

Surge protection is the cheap way, but if you go that route buy a good name brand one that has a product replacement up to a certain dollar amount and they'll pay for anything damaged attached to it. The one I have will pay up to one hundred thousand dollars - not that my stuff is anywhere worth that amount. Even with a surge protector you'd still have to run chkdsk /f on all the hard disk(s) if a storm caused a power outage whilst the PC was on. As soon as I hear thunder I turn off all my computer based electronics (PC, PlayStation's, etc.,) that are plugged into wall outlets. Luckily I haven't had any power failures due to thunderstorms this year, yet, although I remember a few years ago when it was happening at least weekly.

Solution: When CCleaner won't download (Windows) Things to try: * Clean the cache ("Temporary Internet Files") in your web browser. * Try again in a few minutes or hours. * Try the HTTPS secure version of the main site, or download page. * Try a different web browser (if you don't want to install a different web browser you could instead use a portable edition of popular web browsers)

Things to try when this happens: * Use a different web browser. * Try again in a few minutes or hours. * Try the HTTPS secure version of the site download page: https://www.piriform.com/ccleaner/builds

I bet their biggest threat is people like me who have a filter to block everything Facebook related. But them trying to get around ad blocking wouldn't work in my case since they're also blocked via my HOSTS file, and in my hardware firewall to support devices (PS3, PS4, etc.,) without any ad blocking or HOSTS file capabilities.

It may have worked after that 20 minutes you mention, however telling what operating system could give a clue as cleaning Win10 issues are expected after the Win10 Anniversary Update.

One thing I did with the previous version when it wouldn't download was to change the site address to use secure HTTPS. So if you were downloading from the non-secure HTTP site try the secure HTTPS one instead: https://www.piriform.com/ccleaner/builds

You have 30 more than me then, I only use two add-ons; WOT and uBlock Origin.

Only problem I had with 48.0 was with WOT since may system cleaning batch file will nuke some non-English language files, never had an issue with it for several years prior. On a side note I wonder why the developers of WOT don't pack it into an XPI.

I wonder if installing Macrium over the pre-existing version would fix anything.

Got it. It's been 3 years since the free edition had an update.

Avast for Android has disinfected my mothers phone twice so far.

It's not actually CCleaner deleting the restore points. It's caused by Wipe Free Space filling up the hard disk which in turn causes Windows to automatically try to free up some available disk space which it does by deleting old restore points. I still think my solution in post 5 would work, but I seriously doubt they'll ever add in that functionality.