Bug #42423 Windows x64 installer creates registry in WOW6432Node
Submitted: 28 Jan 2009 14:18 Modified: 31 Mar 2014 9:20
Reporter: Jason R. Coombs Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.1.43 GA OS:Windows (Vista 64-bit)
Assigned to: CPU Architecture:Any
Tags: x64 AMD64 EMT64T WOW WOW6432

[28 Jan 2009 14:18] Jason R. Coombs
Description:
I just ran the 64-bit installer.  After installing, I went to check for the registry setting (which Python-Mysql needs to locate the installation), but found it wasn't where I expected it (HKLM\Software\MySQL AB).  It was, however, found in (HKLM\Software\Wow6432Node\MySQL AB).

This is probably an unintended artifact of the installer being a 32-bit application and so when it mounts HKLM\Software, Microsoft subtly replaces the key with the WOW6432Node key.

How to repeat:
Install mysql-5.1.30-winx64.

Suggested fix:
Either build the installer as a native 64-bit application, or search the API to find if there's a way to have the 32-bit installer write to the 64-bit (native) section of the registry.
[28 Jan 2009 22:11] MySQL Verification Team
Thank you for the bug report.
[16 Feb 2010 19:45] Jason R. Coombs
I just confirmed this problem (originally reported against 5.1.30) persists with the latest MSI installer (mysql-5.1.43-winx64.msi, md5 4608343b3fa94304d3b6928fa3a3af31).
[27 Jul 2011 21:21] Martin von Gagern
Still a problem with 5.5.14, affecting not only Python but also RMySQL.
[31 Mar 2014 9:20] Yngve Svendsen
Posted by developer:
 
Thank you for the bug report. We are closing this report now for two related reasons:
* MySQL Server 5.1 is an obsolete version of MySQL Server
* For recent MySQL Server versions, the config wizard is no longer available, and the MySQL Installer for Windows is the recommended way to install MySQL Server on Windows