Hi there
In the change log for CCleaner v2.21.940 I read the following:
- Added support for:Adobe Reader 9.0, Adobe Photoshop CS3,
Adobe Photoshop CS4, Adobe Illustrator CS4,
Nero Burning ROM 9, OpenOffice 3.1,
AVG AntiVirus 8.0, AntiVir Desktop
I have OpenOffice 3.1 installed (not full installation but rather Calc, Impress and Writer) but in Cleaner->Applications I do not see a OpenOffice entry and a checkbox. Is this normal? Is OO3.1 supported in latest version of CCleaner?
According to the changelog, yes, but for the moment only one of the developers could confirm that, as here on the forum we don't yet have access to the latest CCleaner embedded ini file.
But for the moment, I would take note of the info in this post in case it affects you.
Thanks for your answer. Basically, I saw the topic you posted and this is why I asked, because I was trying to deactivate cleaning for OO3.1. But I can't find anything and so far I haven't used CCleaner in case it messes up my OO installation.
I now have a copy of the embedded ini for CCleaner 2.21.940, and Openffice 3.1 is indeed in there.
These are the areas included, taken from the embedded ini.
[OpenOffice 3.1]
ID=2143
LangSecRef=3021
Detect=HKLM\SOFTWARE\OpenOffice.org\OpenOffice.org\3.1
Default=True
FileKey1=%appdata%\OpenOffice.org\3\user\registry\data\org\openoffice\Office|Common.xcu
I can't confirm whether or not it should be showing in CCleaner, as I don't have the program, but hopefully someone who has may confirm that either way.
Thank you Aethec.
I think we have a problem here. The registry key in embedded ini looks in HKLM\SOFTWARE\OpenOffice.org\OpenOffice.org\3.1. This is assuming that the user installed the software, in our case OO3.1 for all users.
However, I installed OO3.1 only for the current user. Therefore OpenOffice DOES NOT put an entry in HKLM but rather in HKCU, that is HKEY_CURRENT_USER. This is why CCleaner misses the key and therefore ignores OpenOffice3.1 cleanup.
Basically, I believe that CCleaner should check both places. I am not sure if this is possible (I believe it is), but the way it behave now, it misses the case of a user-specific OO3.1 installation. I am not sure if I can (or someone else) push this is a future request but I believe it deserves a try.