The problem that I am experiencing is similar to that post.
I usually run ccleaner from the shortcut on my desktop with no additional command added. It used to work without any problems, in fact I used it to clean my system before I upgraded to the newer version. The problem began immediately after I upgraded to the newer version.
The sequence of events varies......
Sometimes I just double-click the CCleaner shortcut, click "run Cleaner" from the splash screen and wait for it to complete its process, and then I click "Run Cleaner" again to repeat the process once again.
Other times, I may perform the above steps and then click "Registry" -> "Scan for Issues" -> "Fix Issues"
To sum it all up in a nutshell,... Everything was working fine until I upgraded to the newer version.
CCleaner's default installation turns on "System Monitoring", and "Active Monitoring".
I turned those settings off through Options -> Monitoring -> "Un-checking" "Enable System Monitoring" AND "Un-checking" "Enable Active Monitoring" (Note: These two settings are currently enabled by default)
However, I have always turned those settings off ever since they added them to the CCleaner Program (Besides, the disabled settings have never caused an issue before)
As for the question, have I saved all settings to ini file at any time... that settings is Not checked. I have had that setting un-checked for a very long time. I have checked and I do check regularly for any changes after I upgrade CCleaner to ensure that the update didn't change any of my personalized settings. Sometimes an update/upgrade will change my settings upon installation, other times it keeps my settings... This particular update to version 5.22.5724 (64-bit) did not make any changes to my previous settings. However, during my troubleshooting of this problem, I performed a completely uninstalled CCleaner. I then downloaded a fresh company from Piriform's web page and installed it... after the installation completed, I had to manually change all of the default settings back to my previous settings as would be expected from a fresh install. In any case, the issue remains; the fresh install made no difference.