I reported recently that CCleaner was locking up in both XP Home and Window 7 64-bit.
I had hoped that the answer I had 'not to secure erase certain temp files less than 24 hours old'.
All is well in XP Home - that works. However in Windows 7, the cleaning is very slow, stalling at 40% every time. That doesn't matter as eventually it will complete, but if an attempt is made to do anything in CCleaner other than minimising it, the machine locks up. That's v3.26.1888 (64-bit) on Windows 7 Pro 64-bit SP-1.
The settings are identical on both machines (a one-pass wipe with the 24-hour temp files parameters).
Possibly CCleaner would lock up on the XP machine if I tried to cancel or stop it - I haven't tried it!
Does it lock up during ANALYZE or only whilst erasing ?
It can be either. The XP machine also crashed twice in CCleaner this evening.
As regards the Window-7: it's running now, locked up in ANALYSE at 2% Internet Explorer History. (I seldom if ever use Internet Explorer, so there should be little history to clear!).
The XP machine has started misbehaving in much the same way at 40% - it was OK for over a week. This one locks the whole system up when it stalls ar 40% and has to be rebooted - neither Task Manager nor any other application can be started.
The Windows 7 one's been stalled at 2% for over an hour, jbut doesn't stop other programmes being launched. I halted it in Task Manager. Restarted it and it completes ANALYSE in less than a second and CLEAN in about 10 seconds. There was no system lockup this time and everything seems to be running normally.
Yes. That said, the lockups will happen (on the XP machine certainly) whether or not the other machine on the network is running.
Is your security software up to date and all scan clean? What is the security software you use?
The machine's clean. Bitdefender Internet Security 2013, Malwayre Bytes Pro run weekly, Vipre Rescue Scanner is also run weekly (although that's not what it's designed for, it does work as a scanner)
.
What happens if you open Internet options from the Control Panel and select to clean all browsing history?
It just goes back to the [General] tab without saying anything. I'm using Firefox 18.0.1 in private browsing mode. Maybe there's nothing to delete in that. Could that be the problem?
Fine, but if the machine locks up, will a log be saved?
Should I let CCleaner run to completion or should I try to cancel or close it?
Regards,
Geo.
How can it run to completion if it locks up? When it locks up, use task manger to crash (end task) ccleaner, then post the log here. It is unclear what you mean by "certain temp files"
instead of arguing the finer points of "secure erase good vs bad" please realize that @Alan_B was attempting to suggest you turn it off in order to rule out it as a cause.
How can it run to completion if it locks up? When it locks up, use task manger to crash (end task) ccleaner, then post the log here.
I can't run Task Manager: when CCleaner locks up NOTHING CAN BE RUN, not even Task Manager, only a restart gets me out of that.
It is unclear what you mean by "certain temp files"
Windows' and Firefox's temporary files,
Thank you and I look forward to your log
I'll try, but if it locks up there's no possibility of a log as the SYSTEM will crash. Catch 22. I suppose I can manage without the overwrite; there are other tools available for that, although it rather defeats the object of an all-in-one CCleaner.
I can't run Task Manager: when CCleaner locks up NOTHING CAN BE RUN, not even Task Manager, only a restart gets me out of that.
I experienced that when I had XP Home on a single core processor Laptop.
Then I overcame it.
I launched Task Manager and selected the processes Tab BEFORE doing whatever caused the lockup,
and with Task Manager active and on the screen I was able to (slowly) select the relevant process and right click to "End Process" or "End Process Tree" as appropriate.
P.S.
As Nergal has already told you
I want you to NOT over-write because that adds a complication that may be totally needless.
Please keep it simple.
Do NOT complicate with the over-write unless your problem only manifests during over-write.
This in no way stops you from using over-write once the problem has been identified and fixed.
I experienced that when I had XP Home on a single core processor Laptop.
Then I overcame it.
I launched Task Manager and selected the processes Tab BEFORE doing whatever caused the lockup,
and with Task Manager active and on the screen I was able to (slowly) select the relevant process and right click to "End Process" or "End Process Tree" as appropriate.
P.S.
As Nergal has already told you
I want you to NOT over-write because that adds a complication that may be totally needless.
Please keep it simple.
Do NOT complicate with the over-write unless your problem only manifests during over-write.
This in no way stops you from using over-write once the problem has been identified and fixed.
As I recall, on both Windows 7 and XP Home the problem only occurs in overwrite mode. Anyway I can't now get it to stall in non-overwrite mode.