This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jurko.Gospodnetić
Recipients Jurko.Gospodnetić
Date 2014-03-19.17:48:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395251284.98.0.0921676080974.issue20984@psf.upfronthosting.co.za>
In-reply-to
Content
Here is a possible 'workaround' for the issue, but it
will take someone more knowledgeable about the Windows
Installer infrastructure to say if the workaround can be
applied directly as a clean solution or if it could have
hidden consequences.

Each 32-bit installation on 64-bit Windows has its own
'Uninstall' registry key under:

> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

named after its Windows Installer assigned GUID, e.g.:

> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{A37F2D73-72D1-364D-BA5D-CEA430BCC040}

In that key there is a value named 'WindowsInstaller'
which for CPython installations has the value '1' (of
type REG_DWORD).

If you change that value to '0' (again, of type REG_DWORD),
the installation's 'Add/Remove Programs' dialog entry will
get displayed correctly, and user will be able to run the
installation (reinstall/change/uninstall) from there.
History
Date User Action Args
2014-03-19 17:48:05Jurko.Gospodnetićsetrecipients: + Jurko.Gospodnetić
2014-03-19 17:48:04Jurko.Gospodnetićsetmessageid: <1395251284.98.0.0921676080974.issue20984@psf.upfronthosting.co.za>
2014-03-19 17:48:04Jurko.Gospodnetićlinkissue20984 messages
2014-03-19 17:48:04Jurko.Gospodnetićcreate