Menu

#731 PyWin mismatch error

v1.0 (example)
open
None
5
2017-01-19
2016-09-22
No

I downloaded/installed the latest Python for 64 bit system
(python-3.6.0b1-amd64) for use on a Win10 system.

figuring that this is now the latest/greatest Python, I then download PyWin
(pywin32-220.win-amd64-py3.6)

I get the following error - what combination should I be using?

1 Attachments

Discussion

  • Ivan Van Laningham

    I'm getting the exact same error. Looks like the 64-bit version is mistakenly expecting the 32-bit version of Python3.6 in the registry. See also https://sourceforge.net/p/pywin32/bugs/702/

    I've added a simple registry hack to work around the problem. If your installation is in a different location (i.e., not on C:, and/or not for all users), you'll have to edit it to take that into account. Hope this helps.

     

    Last edit: Ivan Van Laningham 2016-10-30
    • Guillaume

      Guillaume - 2017-01-09

      Worked as expected, thanks a lot for this fix Ivan!

       
  • markt

    markt - 2016-12-23

    Also getting the same error. Python 3.6-amd64 was installed for "all users", but pywin32-220.win-amd64-py3.6 won't install, expecting 32-bit.

     
  • DJ

    DJ - 2017-01-08

    Same as markt with the additon of installing in C:\python36
    The error is "Python version 3.6-32 required, which was not found in registery"

    It shouldn't be looking for this registery entry since it is not 3.6-32, it's only 3.6

    HKLM/SOFTWARE/Python/PythonCore/3.6/PythonPath exists and the value is C:\Python36\Lib\;C:\Python36\DLLs\

    The install path is correct as well.

    Also, After failing to install the next window has place to insert the two paths but you can't type or paste into them.

     

    Last edit: DJ 2017-01-08
  • Guillaume

    Guillaume - 2017-01-09

    Problem solved using Ivan fix

     
  • Héctor D.

    Héctor D. - 2017-01-12

    Why not repair the install package? This fix introduces rubbish in the registry that can impact on other python packages. And you have to remove the keys manually after the installation. It would be better change directly the installation package to solve this problem and to let next users don't worry about the problem.

     
  • tonioant

    tonioant - 2017-01-19

    I have simply renamed the path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\3.6-32

    To:

    HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\3.6

    Apparently everything works correctly: shell, import, pip... and installation of pywin32

     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.