CCleaner x64 gets installed into wrong folder

CCleaner for Windows CCleaner Windows Bug Reporting
1

Searched older post, but couldn't find this one, so I apologize if someone already reported it.

CCleaner x64 gets installed into Program Files (x86) instead into Program Files. Even if manually changing this, on the next update it will still want to install to the wrong one.

Defraggler installer however does this correctly so it seems to be CCleaner setup specific and it doesn't detect properly x86 vs. x64.

It would also be nice if it can detect existing version and its folder.

BTW why is it always installing both 32bit and 64bit?

2

BTW why is it always installing both 32bit and 64bit?

The installation folder/path is "Program Files (x86)" probably because of the 32bit version. I don't mind installing both, though usually use just portable version of CCleaner.

3

uninstall CCleaner, then reinstall it to \Program Files\

It should retain the behavior. That worked for me when the first released it in x64

4

Will try that, but have to export bunch of custom imports first :(

Though, if that works then it relies on the value of this key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner]

@="C:\\Program Files (x86)\\CCleaner"

Thanks ;)

5

You can export your settings easily by saving them to CCleaner.ini (found in ccleaner settings)

6

You can export your settings easily by saving them to CCleaner.ini (found in ccleaner settings)

You mean "Save all settings to INI file" option?

It was easier to dump the whole reg. key and re-import :)

Anyway, this did resolve the problem, and it appears there was bunch of other keys as it was installed for all users and most of them got deleted after uninstall.

However, I noticed a weird issue with installer as the offered option to open readme.html opened it in Chrome!

Chrome was not assigned to any file or protocol, and all URLs and HTML pages are opened in the default browser except for Piriform's installer.

Is it using chromeHTML:// URI handler or something else?

This is the only case when a web page starts my Chrome which I rarely use so that's why it doesn't have any file/content/protocol assignments.

7

Same with mine, it also opened in Chrome.

8

Same with mine, it also opened in Chrome.

Interesting. So it's not just my box. I though initially something is messed up, but only Piriform's installer was opening it in Chrome, so I wasn't sure and wanted to ask if there's something special about how it's opening URL and though it might be related to chromeHTML as that one is specific to Chrome and is the only one assigned to Chrome in my class root.