Bug #43265 QB and WorkBench installer is suggesting wrong target device

Description:
Today, I've experienced problem with the latest installer for both MySQL Query Browser (1.2.17) and MySQL WorkBench (5.0.30) that the default suggested drive (C:\Program Files\MySQL\) to install the programs on, was another than the one the existing program existed on (E:\Program Files\MySQL).

The installer might be confused, by the fact that the MySQL Server is running from C:\Program Files\MySQL.

But on the other hand, a simple scan through the MS registry (yes, that messy repository... ;-) revealed that the current version of each of these products were actually running on the E:\Program Files\MySQL.

How to repeat:
1. Make sure to have at least a C:\Program Files\MySQL catalog
   (Maybe also the MySQL Server should be running here?)

2. Then make sure to have an older version of either Workbench or Query Browser
   existing on an other drive (e.g. E:\Program Files\MySQL\)

3. Start the latest installer, and note where it will suggest as default target.

Changing category isn't Server install issue.

Sorry, but I am not able to see the error here.

The installation path is:

C:\<language based name for programs>\MySQL\MySQL Tools for 5.0

and 

C:\<language based name for programs>\MySQL\MySQL Workbench 5.0 OSS

Ok - I must express the problem better:

1. The (old version) of the product which is reinstalled must exist on an other drive, but NOT C: (e.g. E: or whatever...)

2. When the installer is running, it will NOT detect the fact, that the product (in this case the "MySQL Query Browser") existed on E:, but will now try to put on the "default" C:-drive.

3. As I also noted, was that even though the old one (E:\Program Files\MySQL\MySQL Tools for 5.0\MySQLQueryBrowser.exe) was located in E, there actually exist an path named "C:\Program Files\MySQL\MySQL Tools for 5.0\", but this did NOT have any MySQLQueryBrowser.exe in it....

Verified as described

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL GUI Tools into MySQL Workbench. We won't fix this anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/

Sorry, wrong bug number. Of course this is a Workbench bugs that needs fixing.

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.