CCleaner 3.05.1408 and MySQL 5.1

Hello all,

I am using Windows 7 64 bit with MySQL 5.1.56 32 bit.

CCleaner detects the following as a registry issue:

Invalid file reference ImagePath - "c:\program files (x86)\mysql\mysql server 5.1\bin\mysqld" --defaults-file="c:\program files (x86)\mysql\mysql server 5.1\my.ini" mysql HKLM\SYSTEM\CurrentControlSet\services\MySQL

This is somewhat problematic as if I do remove the issue, it effectively deletes the Windows service, and on the next boot I have to reinstall the service. I can avoid checking for issues related to Windows services, or just uncheck the issue in the found issues list, but this is a false positive, and it would be nice if CCleaner could avoid considering it as an issue.

Yes, I've been using CCleaner for at least 2-3 years and I recommend this application to many of my friends, telling them registry clean-up never gave me any problem. (which is truth!) They dare remove junk files but they think cleaning up registry is problematic. I always assure them telling them my experience.

What I learned today was quite surprising. Kindly fix this as I still like to recommend this to people. :)

Keep up the good work and all the best~

-KZee

Thanks, we'll look into this.

Hello - I can confirm that this is also happening on version 3.05.1409 - 32bit Windows Vista.

In case that helps at all.

Regards

Wow, I just wanted to login and confirm this for MySQL v5.1 and v5.5...

its a doozie... didnt even recognize the old instance when I reset it up (MySQL data location is STILL broken... it IGNORES the selection in the instance setup wizard... bug is been open for 6 months now over @ MySQL), thank god for daily backup's however :P

I love MySQL, and made to add this exclusion for each developer I help with monthly autoruns :D, love CCleaner as well :P

Cheers!

The same problem in MySQL 4.1 - Windows XP 32 bit

have the same problem.

yesterday i've installed ccleaner 3.05.1409 ans since then i cant connetc to my local mysql database :(

please fix it ASAP !!

You must install again MySQL...

Don't forget to backup your DB and settings.

Folder "Data"

and file my.ini

it seems to be the only solution, the problem is why does it's happening ?

For the time being, I think you should all add this to your whitelist, to avoid problems.

No need to re-install MySQL, you just need to re-create the service in Windows. For example, you can run the MySQLInstanceConfig.exe for that, which you will find in:

C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin

under Windows 7 64 bit, assuming you kept the default path. Or if you're familiar enough with both Windows and MySQL configuration (not my case), there's probably a command to create the service from the command line...

The same problem with MySQL 5.5.9.0

// -------------------------------------------------------------------------------

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MySQL]

"Type"=dword:00000010

"Start"=dword:00000002

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,\

00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,4d,00,79,00,53,00,51,00,\

4c,00,5c,00,4d,00,79,00,53,00,51,00,4c,00,20,00,53,00,65,00,72,00,76,00,65,\

00,72,00,20,00,35,00,2e,00,35,00,5c,00,62,00,69,00,6e,00,5c,00,6d,00,79,00,\

73,00,71,00,6c,00,64,00,22,00,20,00,2d,00,2d,00,64,00,65,00,66,00,61,00,75,\

00,6c,00,74,00,73,00,2d,00,66,00,69,00,6c,00,65,00,3d,00,22,00,43,00,3a,00,\

5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,\

00,73,00,5c,00,4d,00,79,00,53,00,51,00,4c,00,5c,00,4d,00,79,00,53,00,51,00,\

4c,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,20,00,35,00,2e,00,35,00,5c,\

00,6d,00,79,00,2e,00,69,00,6e,00,69,00,22,00,20,00,4d,00,79,00,53,00,51,00,\

4c,00,00,00

"DisplayName"="MySQL"

"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MySQL\Security]

"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,\

02,00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,\

00,00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,\

00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,\

00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,\

00,00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,\

01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MySQL\Enum]

"0"="Root\\LEGACY_MYSQL\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

// -------------------------------------------------------------------------------

And with Oracle 11g

// -------------------------------------------------------------------------------

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OracleOraDb11g_home1TNSListener]

"Type"=dword:00000010

"Start"=dword:00000003

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):43,00,3a,00,5c,00,4f,00,72,00,61,00,63,00,6c,00,65,00,5c,\

00,70,00,72,00,6f,00,64,00,75,00,63,00,74,00,5c,00,31,00,31,00,2e,00,32,00,\

2e,00,30,00,5c,00,64,00,62,00,68,00,6f,00,6d,00,65,00,5f,00,31,00,5c,00,42,\

00,49,00,4e,00,5c,00,54,00,4e,00,53,00,4c,00,53,00,4e,00,52,00,20,00,00,00

"DisplayName"="OracleOraDb11g_home1TNSListener"

"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OracleOraDb11g_home1TNSListener\Security]

"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,\

02,00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,\

00,00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,\

00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,\

00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,\

00,00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,\

01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OracleOraDb11g_home1TNSListener\Enum]

"0"="Root\\LEGACY_ORACLEORADB11G_HOME1TNSLISTENER\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

// -------------------------------------------------------------------------------

just installed pro version v.5.17.5590 and ran the registry tool. now mysql is broken. looks like this BUG is still not fixed.

try the latest version, 5.19, but based on the age of the problem, I doubt it's fix in the latest version either.

so as @Winapp2.ini suggested ealier, add that key as an exception for the time being.

but that's the potential downside with any reg cleaning, things break, it's just a known, fairly common, side-effect.

which is why the backup option is offered.