2 replies to this topic

[viaTech]

Just installed CCleaner v2.23.993 update over v2.29 on a HP TouchSmart tx2z running Windows Vista Ultimate x64, and the Registry Cleaner stopped responding for longer than five (5) minutes and never recovered in two successive attempts. Confirmed "NOT RESPONDING" status in Task Manager, ending task in each case.

I'd never experienced a terminal failure or prolonged cleaning time even remotely close to this in any of the previous versions.

Ironically, this was also the first time I've seen more than a handful of errant Registry entries listed in the analysis phase... the Registry Backup files for the two failed sessions are 1,074,482 KB at 12:31:16 pm and 53,311 KB at 12:42:05 pm, respectively. In contrast, the largest single Registry Backup file among all previous versions is 46 KB.

I am aware (from the release notes) that the latest build (v2.23.993) includes a number of x64 enhancements and can't help wondering what, if any, bearing they might have on this uncharacteristic lockup/freeze. On the other hand, the size difference between Registry Backups some 10 minutes and 49 seconds apart would suggest that a substantial number of Registry entries had actually been cleaned up in the earlier session.

Has anyone else experienced a similar apparent freeze in v2.23.993?

Great product, none the less — thanks!


Chima.

[MrRon]

I'd be really interested too to hear if anyone can recreate this.

MrRon

[Keithuk]

@MrRon does CC have the ability to run in ...\ccleaner.exe /debug mode the same as Recuva and Defraggler do? I don't see it listed in the help docs.