When I click the Analyze button (in Cleaner) the scan immediately starts at 39% and just hangs there. I've let the scan run for more than an hour but it doesn't change. I've uninstalled CCleaner, done routine maintenance (disk cleanup, defrag, etc.), rebooted, reinstalled CCleaner. Problem did not go away. If I click Cancel (while in Analysis scan) I will get the prompt :
ANALYSIS CANCELLED - (38.861 secs) (or whatever time the scan was running)
I am using 2.18.878 on all systems in my signature and am not having that problem. That's not to say that you are doing something wrong. You could have a legitimate bug going on. Where did you download your copy from?
When 2.18.878 was released I received the usual prompt that a newer version was available after I opened the CCleaner main program window. I used the automatic upgrade installer. When I uninstalled CCleaner earlier today, I used the FileHippo site to reinstall (after linking to it from the CCleaner home page.) When that didn't work I uninstalled again, used Windows built in search feature to find any unremoved (orphan) CCleaner and/or Piriform files. Also used another search tool (Copernic Desktop Search.) Finally used regedit to clean registry of all CCleaner and Piriform entries. Used FileHippo again to reinstall. Problem still exists with Cleaner module only. Registry module has always worked perfectly in both Scan and Fix modes.
When 2.18.878 was released I received the usual prompt that a newer version was available after I opened the CCleaner main program window. I used the automatic upgrade installer. When I uninstalled CCleaner earlier today, I used the FileHippo site to reinstall (after linking to it from the CCleaner home page.) When that didn't work I uninstalled again, used Windows built in search feature to find any unremoved (orphan) CCleaner and/or Piriform files. Also used another search tool (Copernic Desktop Search.) Finally used regedit to clean registry of all CCleaner and Piriform entries. Used FileHippo again to reinstall. Problem still exists with Cleaner module only. Registry module has always worked perfectly in both Scan and Fix modes.
Hmm.... Sorry to hear that you have had to go through all of that... The best thing I can tell you right now is to list your full system specs and hope that a developer sees your post because this is definitely an usual, probably isolated situation.