Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #77265 > unrolled thread

Manually uninstall python 3.4.1 x64

Back to article view | Back to comp.lang.python

Contents

  Manually uninstall python 3.4.1 x64 Curtis Clauson <LlelanD@TheSnakePitDev.com> - 2014-08-29 01:19 -0700
    Re: Manually uninstall python 3.4.1 x64 Tim Golden <mail@timgolden.me.uk> - 2014-08-29 20:53 +0100
      Re: Manually uninstall python 3.4.1 x64 "Llelan D." <LlelanD@TheSnakePitDev.com> - 2014-08-29 20:26 -0700
      Re: Manually uninstall python 3.4.1 x64 Terry Reedy <tjreedy@udel.edu> - 2014-08-30 01:13 -0400
        Re: Manually uninstall python 3.4.1 x64 Curtis Clauson <LlelanD@TheSnakePitDev.com> - 2014-09-02 17:34 -0700
          Re: Manually uninstall python 3.4.1 x64 Terry Reedy <tjreedy@udel.edu> - 2014-09-02 22:01 -0400

#77265 — Manually uninstall python 3.4.1 x64

Python v3.4.1 x64 on Windows 7 x64.

I've a situation where the c:/Python34 directory was irrecoverably deleted.

When I run the python-3.4.1.amd64.msi installer and choose Remove, it 
gives me a dialog saying a required file is missing about halfway 
through. It gives me no clue as to what this file is.

If I choose Repair, it gives me a dialog saying "The specified account 
already exists" about halfway through. Totally cryptic.

If I choose Change and either select that all features or no features 
will be installed, it gives me a dialog saying "The specified account 
already exists" about halfway through.

I've tried hunting down and deleting every reference to the installation 
directory in the registry but it doesn't change this problem. I am 
completely unable to install, uninstall, or repair python.

Is there a resource that will completely uninstall python without 
requiring that any of the previously installed files exist, or that 
gives complete instructions on how to manually remove enough so that the 
installer will work again?

Any assistance with this issue would be greatly appreciated.

[toc] | [next] | [standalone]

#77284

On 29/08/2014 09:19, Curtis Clauson wrote:
> Python v3.4.1 x64 on Windows 7 x64.
>
> I've a situation where the c:/Python34 directory was irrecoverably deleted.
>
> When I run the python-3.4.1.amd64.msi installer and choose Remove, it
> gives me a dialog saying a required file is missing about halfway
> through. It gives me no clue as to what this file is.
>
> If I choose Repair, it gives me a dialog saying "The specified account
> already exists" about halfway through. Totally cryptic.
>
> If I choose Change and either select that all features or no features
> will be installed, it gives me a dialog saying "The specified account
> already exists" about halfway through.
>
> I've tried hunting down and deleting every reference to the installation
> directory in the registry but it doesn't change this problem. I am
> completely unable to install, uninstall, or repair python.
>
> Is there a resource that will completely uninstall python without
> requiring that any of the previously installed files exist, or that
> gives complete instructions on how to manually remove enough so that the
> installer will work again?

Unfortunately I don't think there's a simple answer to this one. (Altho' 
I'm not an MSI expert and I'd be very happy to be overruled). 
msiexec.exe, which is the program which actually runs the MSIs, has a 
number of options you can invoke, including a verbose logging option. 
You can see them all by doing:

   msiexec /?

or, presumably some MSDN page with the same information.

Some things which might be worth trying include:

   msiexec /log whatever.log python-xx-yy.msi

to log verbosely, in the hope that some missing or present file or 
registry might show up. And/or playing with the Repair Options to narrow 
things down.

TJG

[toc] | [prev] | [next] | [standalone]

#77312

On 8/29/2014 12:53 PM, Tim Golden wrote:
> On 29/08/2014 09:19, Curtis Clauson wrote:
>
> Unfortunately I don't think there's a simple answer to this one. (Altho'
> I'm not an MSI expert and I'd be very happy to be overruled).
> msiexec.exe, which is the program which actually runs the MSIs, has a
> number of options you can invoke, including a verbose logging option.
> You can see them all by doing:
>
>    msiexec /?
>
> or, presumably some MSDN page with the same information.
>
> Some things which might be worth trying include:
>
>    msiexec /log whatever.log python-xx-yy.msi
>
> to log verbosely, in the hope that some missing or present file or
> registry might show up. And/or playing with the Repair Options to narrow
> things down.
>
> TJG

Actually, I do know more than a little about the Windows MSI service and 
application, and had already perused the logs to no avail. All of the 
listed registry keys were deleted without changing the problem. The 
missing file is of no importance since I already know the installation 
directory is deleted. It's just that the installer should normally 
supply that information.

The error messages are Windows System errors that are being caused by 
requirements of the MSI installer file and not the msiexec.exe 
application. The problem is with how the installer is written and not 
the MSI system.

There's always a simple answer to things like this. It's just that the 
simple answers are harder to find in poorly written code.

I randomly poked around the registry a lot more, deleting anything I 
could find referring to Python34 and then the string "Python 3.4.1". I 
finally got desperate enough to delete the python installer entries 
under the Windows Installer key (the list of installed applications in 
the Windows "Uninstall or Change a Program" Control Panel). You know, 
the registry keys you are *NEVER* to use as an indication if the 
application is currently installed because MS constantly corrupts this 
list and can leave your installation in an un-installable, 
un-repairable, and un-removeable state?

Well it worked. The Python installer no longer sees the application as 
installed and happily performs a full installation. I did that, a full 
removal to get rid of any other problems, and a clean installation and 
everything works fine now.

This installer is seriously screwed up and desperately needs a re-write. 
It should use its own key to indicate whether the application is 
installed but should not depend on it in case of a partially 
installed/removed state, should not require any installed file to fully 
repair or remove the application, and should query the user if any 
information required is missing from the installation or registry. In 
other words, the normal MSI installer guidelines.

I hope this is of help to someone out there.

[toc] | [prev] | [next] | [standalone]

#77315

On 8/29/2014 11:26 PM, Llelan D. wrote:

> Actually, I do know more than a little about the Windows MSI service and
> application, and had already perused the logs to no avail. All of the
> listed registry keys were deleted without changing the problem. The
> missing file is of no importance since I already know the installation
> directory is deleted. It's just that the installer should normally
> supply that information.
>
> The error messages are Windows System errors that are being caused by
> requirements of the MSI installer file and not the msiexec.exe
> application. The problem is with how the installer is written and not
> the MSI system.
>
> There's always a simple answer to things like this. It's just that the
> simple answers are harder to find in poorly written code.
>
> I randomly poked around the registry a lot more, deleting anything I
> could find referring to Python34 and then the string "Python 3.4.1". I
> finally got desperate enough to delete the python installer entries
> under the Windows Installer key (the list of installed applications in
> the Windows "Uninstall or Change a Program" Control Panel). You know,
> the registry keys you are *NEVER* to use as an indication if the
> application is currently installed because MS constantly corrupts this
> list and can leave your installation in an un-installable,
> un-repairable, and un-removeable state?
>
> Well it worked. The Python installer no longer sees the application as
> installed and happily performs a full installation. I did that, a full
> removal to get rid of any other problems, and a clean installation and
> everything works fine now.
>
> This installer is seriously screwed up and desperately needs a re-write.
> It should use its own key to indicate whether the application is
> installed but should not depend on it in case of a partially
> installed/removed state, should not require any installed file to fully
> repair or remove the application, and should query the user if any
> information required is missing from the installation or registry. In
> other words, the normal MSI installer guidelines.
>
> I hope this is of help to someone out there.

Please file an issue on the tracker reporting the problem (you are not 
the first!) and your suggested solutions and add steve.dower as nosy. He 
is a MS employee - Python volunteer who has very recently assumed 
maintenance of the msi installer.  He wants to upgrade it.

The installer is build with msilib.  Feel free to take a look at that.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#77458

On 8/29/2014 10:13 PM, Terry Reedy wrote:
> Please file an issue on the tracker reporting the problem (you are not
> the first!) and your suggested solutions and add steve.dower as nosy. He
> is a MS employee - Python volunteer who has very recently assumed
> maintenance of the msi installer.  He wants to upgrade it.
>
> The installer is build with msilib.  Feel free to take a look at that.
Done: http://bugs.python.org/issue22329

I'm assuming that by "the tracker" you meant "bugs.python.org". There is 
no link to it from the Python home page and it was difficult to locate.

I hope Mr. Dower finds it helpful.

[toc] | [prev] | [next] | [standalone]

#77462

On 9/2/2014 8:34 PM, Curtis Clauson wrote:
> On 8/29/2014 10:13 PM, Terry Reedy wrote:
>> Please file an issue on the tracker reporting the problem (you are not
>> the first!) and your suggested solutions and add steve.dower as nosy. He
>> is a MS employee - Python volunteer who has very recently assumed
>> maintenance of the msi installer.  He wants to upgrade it.
>>
>> The installer is build with msilib.  Feel free to take a look at that.
> Done: http://bugs.python.org/issue22329
>
> I'm assuming that by "the tracker" you meant "bugs.python.org". There is
> no link to it from the Python home page and it was difficult to locate.

Sorry, I am usually specific. Each doc main page, such as
https://docs.python.org/3/
has the Reporting Bugs document listed.

> I hope Mr. Dower finds it helpful.



-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web