Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This is not uncommon with installers (e.g. Numpy) that depend on or look for a previously installed 64 bit core application (e.g. Python x64). The problem and solution are easy to explain.</p> <p><strong>PROBLEM</strong> IMHO this is an error on the part of the developer of the already-installed 64 bit applicaiton by placing the registry entry in the 32 bit node rather than (or in addition to) the 64 bit node. Actually, the developer of the installer could also code it to look in both locations as well, rather than just assuming the 64 bit application registry entry will be in \Wow6432Node, as a way of avoiding this problem of the original developer's oversight; however, if the installer bases its decision on whether the app is 32- or 64 bit based on the location of the registry entry (not a good idea), this could be problematic.</p> <p>Occassionally with 64 bit applicaitons a registry entry will be created in...</p> <pre><code>HKLM\SOFTWARE\[applicaion name] </code></pre> <p>However, a corresponding registry entry is not created in...</p> <pre><code>HKLM\SOFTWARE\Wow6432Node\[application name] </code></pre> <p><strong>SOLUTION</strong> The easiest way to resolve this with any applicaiton is to...</p> <ol> <li>Open the registry editor (START --> RUN --> regedit)</li> <li>Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ [applicaiton name] (in this case "Python")</li> <li>Right click on the applicaiton ("Python")</li> <li>Select "Export" and save the file somewhere as "[application name].reg" ("Python.reg")</li> <li>Open the saved file with your editor of choice (I like Notepad++)</li> <li>On each entry right after "[HKEY_LOCAL_MACHINE\SOFTWARE" but before \ [applicaiton name] ("\Python"), add "\Wow6432Node" (without the quotes, obviously)</li> <li>Save the edited file as "[application name]_64.reg" (Python_64.reg")</li> <li>Close the editor and double-click on the newly created file, answer "Yes" to the Registry Editor verification popup.</li> </ol> <p>Now you should have duplicate entries in HKLM\SOFTWARE\ [applicaiton name] and HKLM\SOFTWARE\Wow6432Node\ [applicaiton name]. Alternatively, you could manually create all the missing entries under HKLM\SOFTWARE\Wow6432Node\ [applicaiton name] to match what is in HKLM\SOFTWARE\ [application name], but that's really the long way around.</p> <p>When you re-run the Numpy installer, it will now properly detect your 64 bit installation of Python.</p> <p><strong>CAVEAT</strong> There is a caveat to all this.</p> <p>The duplicate entries in HKLM\SOFTWARE and HKLM\SOFTWARE\Wow6432Node are not a problem and will not affect normal operation of an application; however, as the developer missed creating the Wow6432Node registry entry, it's unlikely that any future updates that modify the registry entries will be populated in both locations. You may occassionally have to either perform this operation again or manually add new registry entries to the Wow6432Node in order to keep them consistent. An example where you might run into this is with the installation of Python modules that add an entry under HKLM\SOFTWARE\Python\PythonCore\2.x\Modules\ . You can export just the added entry and edit the .reg file to include "\Wow6432Node" only, export the entire \Python node and edit all entries (importing the edited .reg file will overwrite existing entries), or just manually add the new entry - whatever seems simpler to you.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload