How to completely remove Python from a Windows machine?











up vote
61
down vote

favorite
11












I installed both Python 2.7 and Python 2.6.5. I don't know what went wrong, but nothing related to Python seems to work any more. e.g. "setup.py install" for certain packages don't recognize the "install" parameter and other odd phenomena...



I would like to completely remove Python from my system.

I tried running the 2.7 and 2.6 msi files and choosing remove Python and then running only 2.6 and reinstalling it. Still stuff don't work.



How do I completely remove Python - from everything? (!)



I would not like to reinstall my entire machine just because of the Python install...










share|improve this question






















  • I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
    – Jonathan
    Aug 24 '10 at 12:45















up vote
61
down vote

favorite
11












I installed both Python 2.7 and Python 2.6.5. I don't know what went wrong, but nothing related to Python seems to work any more. e.g. "setup.py install" for certain packages don't recognize the "install" parameter and other odd phenomena...



I would like to completely remove Python from my system.

I tried running the 2.7 and 2.6 msi files and choosing remove Python and then running only 2.6 and reinstalling it. Still stuff don't work.



How do I completely remove Python - from everything? (!)



I would not like to reinstall my entire machine just because of the Python install...










share|improve this question






















  • I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
    – Jonathan
    Aug 24 '10 at 12:45













up vote
61
down vote

favorite
11









up vote
61
down vote

favorite
11






11





I installed both Python 2.7 and Python 2.6.5. I don't know what went wrong, but nothing related to Python seems to work any more. e.g. "setup.py install" for certain packages don't recognize the "install" parameter and other odd phenomena...



I would like to completely remove Python from my system.

I tried running the 2.7 and 2.6 msi files and choosing remove Python and then running only 2.6 and reinstalling it. Still stuff don't work.



How do I completely remove Python - from everything? (!)



I would not like to reinstall my entire machine just because of the Python install...










share|improve this question













I installed both Python 2.7 and Python 2.6.5. I don't know what went wrong, but nothing related to Python seems to work any more. e.g. "setup.py install" for certain packages don't recognize the "install" parameter and other odd phenomena...



I would like to completely remove Python from my system.

I tried running the 2.7 and 2.6 msi files and choosing remove Python and then running only 2.6 and reinstalling it. Still stuff don't work.



How do I completely remove Python - from everything? (!)



I would not like to reinstall my entire machine just because of the Python install...







python installation uninstall






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 18 '10 at 18:59









Jonathan

34k69200305




34k69200305












  • I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
    – Jonathan
    Aug 24 '10 at 12:45


















  • I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
    – Jonathan
    Aug 24 '10 at 12:45
















I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
– Jonathan
Aug 24 '10 at 12:45




I've discovered that the "odd phenomena" occurred due to a 3rd python installation that was installed without my notice by a buildout script...
– Jonathan
Aug 24 '10 at 12:45












9 Answers
9






active

oldest

votes

















up vote
18
down vote



accepted










You will also have to look in your system path. Python puts itself there and does not remove itself: http://www.computerhope.com/issues/ch000549.htm



Your problems probably started because your python path is pointing to the wrong one.






share|improve this answer

















  • 6




    And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
    – S.Lott
    Aug 18 '10 at 19:50






  • 1




    I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
    – Jonathan
    Aug 18 '10 at 22:20










  • Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
    – Daniel Möller
    May 28 '17 at 15:16


















up vote
36
down vote













Here's the steps (my non-computer-savvy girlfriend had to figure this one out for me, but unlike all the far more complicated processes one can find online, this one works)




  1. Open Control Panel

  2. Click "Uninstall a Program"

  3. Scroll down to Python and click uninstall for each version you don't want anymore.


This works on Windows 7 out of the box, no additional programs or scripts required.






share|improve this answer

















  • 4




    If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
    – Ross Smith II
    Jul 21 '17 at 14:27




















up vote
5
down vote













Run ASSOC and FTYPE to see what your py files are associated to. (These commands are internal to cmd.exe so if you use a different command processor ymmv.)



C:> assoc .py
.py=Python.File

C:> ftype Python.File
Python.File="C:Python26.w64python.exe" "%1" %*

C:> assoc .pyw
.pyw=Python.NoConFile

C:> ftype Python.NoConFile
Python.NoConFile="C:Python26.w64pythonw.exe" "%1" %*


(I have both 32- and 64-bit installs of Python, hence my local directory name.)






share|improve this answer



















  • 1




    -1: none of my consoles recognize this command. Please provide references for how you obtained it.
    – ArtOfWarfare
    Aug 24 '13 at 20:48










  • @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
    – dash-tom-bang
    Aug 28 '13 at 21:05










  • Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
    – ArtOfWarfare
    Aug 29 '13 at 1:18






  • 2




    Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
    – dash-tom-bang
    Sep 3 '13 at 3:35










  • I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
    – ArtOfWarfare
    Sep 3 '13 at 19:46


















up vote
3
down vote













I had window 7 (64 bit) and Python 2.7.12,
I uninstalled it by clicking the python installer from the "download" directory then I selected remove python then I clicked “ finish”.

I also removed the remaining python associated directory & files from the c: drive and also from “my documents” folder, since I created some files there.






share|improve this answer




























    up vote
    2
    down vote













    Almost all of the python files should live in their respective folders (C:Python26 and C:Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.






    share|improve this answer




























      up vote
      0
      down vote













      Windows 7 64-bit, with both Python3.4 and Python2.7 installed at some point :)



      I'm using Py.exe to route to Py2 or Py3 depending on the script's needs - but I previously improperly uninstalled Python27 before.



      Py27 was removed manually from C:pythonPython27 (the folder Python27 was deleted by me previously)



      Upon re-installing Python27, it gave the above error you specify.

      It would always back out while trying to 'remove shortcuts' during the installation process.



      I placed a copy of Python27 back in that original folder, at C:PythonPython27, and re-ran the same failing Python27 installer. It was happy locating those items and removing them, and proceeded with the install.



      This is not the answer that addresses registry key issues (others mention that) but it is somewhat of a workaround if you know of previous installations that were improperly removed.



      You could have some insight to this by opening "regedit" and searching for "Python27" - a registry key appeared in my command-shell Cache pointing at c:pythonpython27 (which had been removed and was not present when searching in the registry upon finding it).



      That may help point to previously improperly removed installations.



      Good luck!






      share|improve this answer






























        up vote
        0
        down vote













        I know it is an old question, but I ran into this problem with 2.7 and 3.5. Though 2.7 would not show up in my default windows uninstall list, it showed up fine in the ccleaner tools tab under uninstall. Uninstalled and reinstalled afterwards and it has been smooth coding ever since.






        share|improve this answer




























          up vote
          0
          down vote













          Uninstall the python program using the windows GUI.
          Delete the containing folder e.g if it was stored in C:python36 make sure to delete that folder






          share|improve this answer




























            up vote
            0
            down vote













            It's actually quite simple.
            When you installed it, you must have done it using some .exe file (I am assuming). Just run that .exe again, and then there will be options to modify Python. Just select the "Complete Uninstall" option, and the EXE will completely wipe out python for you.



            Also, you might have to checkbox the "Remove Python from PATH". By default it is selected, but you may as well check it to be sure :)






            share|improve this answer





















              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














               

              draft saved


              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f3515673%2fhow-to-completely-remove-python-from-a-windows-machine%23new-answer', 'question_page');
              }
              );

              Post as a guest
































              9 Answers
              9






              active

              oldest

              votes








              9 Answers
              9






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              18
              down vote



              accepted










              You will also have to look in your system path. Python puts itself there and does not remove itself: http://www.computerhope.com/issues/ch000549.htm



              Your problems probably started because your python path is pointing to the wrong one.






              share|improve this answer

















              • 6




                And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
                – S.Lott
                Aug 18 '10 at 19:50






              • 1




                I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
                – Jonathan
                Aug 18 '10 at 22:20










              • Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
                – Daniel Möller
                May 28 '17 at 15:16















              up vote
              18
              down vote



              accepted










              You will also have to look in your system path. Python puts itself there and does not remove itself: http://www.computerhope.com/issues/ch000549.htm



              Your problems probably started because your python path is pointing to the wrong one.






              share|improve this answer

















              • 6




                And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
                – S.Lott
                Aug 18 '10 at 19:50






              • 1




                I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
                – Jonathan
                Aug 18 '10 at 22:20










              • Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
                – Daniel Möller
                May 28 '17 at 15:16













              up vote
              18
              down vote



              accepted







              up vote
              18
              down vote



              accepted






              You will also have to look in your system path. Python puts itself there and does not remove itself: http://www.computerhope.com/issues/ch000549.htm



              Your problems probably started because your python path is pointing to the wrong one.






              share|improve this answer












              You will also have to look in your system path. Python puts itself there and does not remove itself: http://www.computerhope.com/issues/ch000549.htm



              Your problems probably started because your python path is pointing to the wrong one.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Aug 18 '10 at 19:32









              Alex Bliskovsky

              2,12761937




              2,12761937








              • 6




                And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
                – S.Lott
                Aug 18 '10 at 19:50






              • 1




                I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
                – Jonathan
                Aug 18 '10 at 22:20










              • Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
                – Daniel Möller
                May 28 '17 at 15:16














              • 6




                And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
                – S.Lott
                Aug 18 '10 at 19:50






              • 1




                I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
                – Jonathan
                Aug 18 '10 at 22:20










              • Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
                – Daniel Möller
                May 28 '17 at 15:16








              6




              6




              And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
              – S.Lott
              Aug 18 '10 at 19:50




              And you may have to cleanup the Windows Registry to remove the Registry Key that's there. See this effbot.org/zone/python-register.htm and this: docs.python.org/using/windows.html#finding-modules
              – S.Lott
              Aug 18 '10 at 19:50




              1




              1




              I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
              – Jonathan
              Aug 18 '10 at 22:20




              I'm flagging this as the answer as this is closest to what my problem was... I found out that my .py association was changed by a buildout installation of python. This is why it seemed I couldn't get Python out of my system - I actually had a hidden installation inside one of the projects...
              – Jonathan
              Aug 18 '10 at 22:20












              Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
              – Daniel Möller
              May 28 '17 at 15:16




              Actually, all my python files were kept where they were installed. Also, all package data created in the users folder were also kept.
              – Daniel Möller
              May 28 '17 at 15:16












              up vote
              36
              down vote













              Here's the steps (my non-computer-savvy girlfriend had to figure this one out for me, but unlike all the far more complicated processes one can find online, this one works)




              1. Open Control Panel

              2. Click "Uninstall a Program"

              3. Scroll down to Python and click uninstall for each version you don't want anymore.


              This works on Windows 7 out of the box, no additional programs or scripts required.






              share|improve this answer

















              • 4




                If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
                – Ross Smith II
                Jul 21 '17 at 14:27

















              up vote
              36
              down vote













              Here's the steps (my non-computer-savvy girlfriend had to figure this one out for me, but unlike all the far more complicated processes one can find online, this one works)




              1. Open Control Panel

              2. Click "Uninstall a Program"

              3. Scroll down to Python and click uninstall for each version you don't want anymore.


              This works on Windows 7 out of the box, no additional programs or scripts required.






              share|improve this answer

















              • 4




                If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
                – Ross Smith II
                Jul 21 '17 at 14:27















              up vote
              36
              down vote










              up vote
              36
              down vote









              Here's the steps (my non-computer-savvy girlfriend had to figure this one out for me, but unlike all the far more complicated processes one can find online, this one works)




              1. Open Control Panel

              2. Click "Uninstall a Program"

              3. Scroll down to Python and click uninstall for each version you don't want anymore.


              This works on Windows 7 out of the box, no additional programs or scripts required.






              share|improve this answer












              Here's the steps (my non-computer-savvy girlfriend had to figure this one out for me, but unlike all the far more complicated processes one can find online, this one works)




              1. Open Control Panel

              2. Click "Uninstall a Program"

              3. Scroll down to Python and click uninstall for each version you don't want anymore.


              This works on Windows 7 out of the box, no additional programs or scripts required.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Aug 25 '13 at 15:08









              ArtOfWarfare

              12.4k783131




              12.4k783131








              • 4




                If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
                – Ross Smith II
                Jul 21 '17 at 14:27
















              • 4




                If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
                – Ross Smith II
                Jul 21 '17 at 14:27










              4




              4




              If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
              – Ross Smith II
              Jul 21 '17 at 14:27






              If you installed files with pip, you may want to remove its cache in %LOCALAPPDATA%pip
              – Ross Smith II
              Jul 21 '17 at 14:27












              up vote
              5
              down vote













              Run ASSOC and FTYPE to see what your py files are associated to. (These commands are internal to cmd.exe so if you use a different command processor ymmv.)



              C:> assoc .py
              .py=Python.File

              C:> ftype Python.File
              Python.File="C:Python26.w64python.exe" "%1" %*

              C:> assoc .pyw
              .pyw=Python.NoConFile

              C:> ftype Python.NoConFile
              Python.NoConFile="C:Python26.w64pythonw.exe" "%1" %*


              (I have both 32- and 64-bit installs of Python, hence my local directory name.)






              share|improve this answer



















              • 1




                -1: none of my consoles recognize this command. Please provide references for how you obtained it.
                – ArtOfWarfare
                Aug 24 '13 at 20:48










              • @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
                – dash-tom-bang
                Aug 28 '13 at 21:05










              • Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
                – ArtOfWarfare
                Aug 29 '13 at 1:18






              • 2




                Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
                – dash-tom-bang
                Sep 3 '13 at 3:35










              • I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
                – ArtOfWarfare
                Sep 3 '13 at 19:46















              up vote
              5
              down vote













              Run ASSOC and FTYPE to see what your py files are associated to. (These commands are internal to cmd.exe so if you use a different command processor ymmv.)



              C:> assoc .py
              .py=Python.File

              C:> ftype Python.File
              Python.File="C:Python26.w64python.exe" "%1" %*

              C:> assoc .pyw
              .pyw=Python.NoConFile

              C:> ftype Python.NoConFile
              Python.NoConFile="C:Python26.w64pythonw.exe" "%1" %*


              (I have both 32- and 64-bit installs of Python, hence my local directory name.)






              share|improve this answer



















              • 1




                -1: none of my consoles recognize this command. Please provide references for how you obtained it.
                – ArtOfWarfare
                Aug 24 '13 at 20:48










              • @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
                – dash-tom-bang
                Aug 28 '13 at 21:05










              • Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
                – ArtOfWarfare
                Aug 29 '13 at 1:18






              • 2




                Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
                – dash-tom-bang
                Sep 3 '13 at 3:35










              • I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
                – ArtOfWarfare
                Sep 3 '13 at 19:46













              up vote
              5
              down vote










              up vote
              5
              down vote









              Run ASSOC and FTYPE to see what your py files are associated to. (These commands are internal to cmd.exe so if you use a different command processor ymmv.)



              C:> assoc .py
              .py=Python.File

              C:> ftype Python.File
              Python.File="C:Python26.w64python.exe" "%1" %*

              C:> assoc .pyw
              .pyw=Python.NoConFile

              C:> ftype Python.NoConFile
              Python.NoConFile="C:Python26.w64pythonw.exe" "%1" %*


              (I have both 32- and 64-bit installs of Python, hence my local directory name.)






              share|improve this answer














              Run ASSOC and FTYPE to see what your py files are associated to. (These commands are internal to cmd.exe so if you use a different command processor ymmv.)



              C:> assoc .py
              .py=Python.File

              C:> ftype Python.File
              Python.File="C:Python26.w64python.exe" "%1" %*

              C:> assoc .pyw
              .pyw=Python.NoConFile

              C:> ftype Python.NoConFile
              Python.NoConFile="C:Python26.w64pythonw.exe" "%1" %*


              (I have both 32- and 64-bit installs of Python, hence my local directory name.)







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Sep 3 '13 at 3:36

























              answered Aug 18 '10 at 20:40









              dash-tom-bang

              14.2k23549




              14.2k23549








              • 1




                -1: none of my consoles recognize this command. Please provide references for how you obtained it.
                – ArtOfWarfare
                Aug 24 '13 at 20:48










              • @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
                – dash-tom-bang
                Aug 28 '13 at 21:05










              • Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
                – ArtOfWarfare
                Aug 29 '13 at 1:18






              • 2




                Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
                – dash-tom-bang
                Sep 3 '13 at 3:35










              • I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
                – ArtOfWarfare
                Sep 3 '13 at 19:46














              • 1




                -1: none of my consoles recognize this command. Please provide references for how you obtained it.
                – ArtOfWarfare
                Aug 24 '13 at 20:48










              • @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
                – dash-tom-bang
                Aug 28 '13 at 21:05










              • Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
                – ArtOfWarfare
                Aug 29 '13 at 1:18






              • 2




                Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
                – dash-tom-bang
                Sep 3 '13 at 3:35










              • I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
                – ArtOfWarfare
                Sep 3 '13 at 19:46








              1




              1




              -1: none of my consoles recognize this command. Please provide references for how you obtained it.
              – ArtOfWarfare
              Aug 24 '13 at 20:48




              -1: none of my consoles recognize this command. Please provide references for how you obtained it.
              – ArtOfWarfare
              Aug 24 '13 at 20:48












              @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
              – dash-tom-bang
              Aug 28 '13 at 21:05




              @ArtOfWarfare: a quick search on Google should show you that they are part of Windows. I don't know when they were introduced but I seem to remember them being there as a part of WinXP and they are a part of Win7, although perhaps they're left out of some editions; I'm not terribly knowledgeable about Windows edition differences).
              – dash-tom-bang
              Aug 28 '13 at 21:05












              Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
              – ArtOfWarfare
              Aug 29 '13 at 1:18




              Nor am I, nor is anyone else, I don't think. I have two computers running Windows 7... I forget what edition, but neither of them have any of those commands.
              – ArtOfWarfare
              Aug 29 '13 at 1:18




              2




              2




              Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
              – dash-tom-bang
              Sep 3 '13 at 3:35




              Curious, I looked it up. ftype and assoc are internal to cmd.exe. Perhaps you're using a third party command processor that doesn't support the full command set? ss64.com/nt/assoc.html
              – dash-tom-bang
              Sep 3 '13 at 3:35












              I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
              – ArtOfWarfare
              Sep 3 '13 at 19:46




              I attempted to use cmd just now and it found the commands. I had been using power shell as I was under the impression it did everything cmd did and more. My apologies. I have undone my downvote.
              – ArtOfWarfare
              Sep 3 '13 at 19:46










              up vote
              3
              down vote













              I had window 7 (64 bit) and Python 2.7.12,
              I uninstalled it by clicking the python installer from the "download" directory then I selected remove python then I clicked “ finish”.

              I also removed the remaining python associated directory & files from the c: drive and also from “my documents” folder, since I created some files there.






              share|improve this answer

























                up vote
                3
                down vote













                I had window 7 (64 bit) and Python 2.7.12,
                I uninstalled it by clicking the python installer from the "download" directory then I selected remove python then I clicked “ finish”.

                I also removed the remaining python associated directory & files from the c: drive and also from “my documents” folder, since I created some files there.






                share|improve this answer























                  up vote
                  3
                  down vote










                  up vote
                  3
                  down vote









                  I had window 7 (64 bit) and Python 2.7.12,
                  I uninstalled it by clicking the python installer from the "download" directory then I selected remove python then I clicked “ finish”.

                  I also removed the remaining python associated directory & files from the c: drive and also from “my documents” folder, since I created some files there.






                  share|improve this answer












                  I had window 7 (64 bit) and Python 2.7.12,
                  I uninstalled it by clicking the python installer from the "download" directory then I selected remove python then I clicked “ finish”.

                  I also removed the remaining python associated directory & files from the c: drive and also from “my documents” folder, since I created some files there.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 12 '16 at 14:15









                  Thelma

                  363




                  363






















                      up vote
                      2
                      down vote













                      Almost all of the python files should live in their respective folders (C:Python26 and C:Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.






                      share|improve this answer

























                        up vote
                        2
                        down vote













                        Almost all of the python files should live in their respective folders (C:Python26 and C:Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.






                        share|improve this answer























                          up vote
                          2
                          down vote










                          up vote
                          2
                          down vote









                          Almost all of the python files should live in their respective folders (C:Python26 and C:Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.






                          share|improve this answer












                          Almost all of the python files should live in their respective folders (C:Python26 and C:Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 18 '10 at 19:24









                          Nick T

                          13.4k55696




                          13.4k55696






















                              up vote
                              0
                              down vote













                              Windows 7 64-bit, with both Python3.4 and Python2.7 installed at some point :)



                              I'm using Py.exe to route to Py2 or Py3 depending on the script's needs - but I previously improperly uninstalled Python27 before.



                              Py27 was removed manually from C:pythonPython27 (the folder Python27 was deleted by me previously)



                              Upon re-installing Python27, it gave the above error you specify.

                              It would always back out while trying to 'remove shortcuts' during the installation process.



                              I placed a copy of Python27 back in that original folder, at C:PythonPython27, and re-ran the same failing Python27 installer. It was happy locating those items and removing them, and proceeded with the install.



                              This is not the answer that addresses registry key issues (others mention that) but it is somewhat of a workaround if you know of previous installations that were improperly removed.



                              You could have some insight to this by opening "regedit" and searching for "Python27" - a registry key appeared in my command-shell Cache pointing at c:pythonpython27 (which had been removed and was not present when searching in the registry upon finding it).



                              That may help point to previously improperly removed installations.



                              Good luck!






                              share|improve this answer



























                                up vote
                                0
                                down vote













                                Windows 7 64-bit, with both Python3.4 and Python2.7 installed at some point :)



                                I'm using Py.exe to route to Py2 or Py3 depending on the script's needs - but I previously improperly uninstalled Python27 before.



                                Py27 was removed manually from C:pythonPython27 (the folder Python27 was deleted by me previously)



                                Upon re-installing Python27, it gave the above error you specify.

                                It would always back out while trying to 'remove shortcuts' during the installation process.



                                I placed a copy of Python27 back in that original folder, at C:PythonPython27, and re-ran the same failing Python27 installer. It was happy locating those items and removing them, and proceeded with the install.



                                This is not the answer that addresses registry key issues (others mention that) but it is somewhat of a workaround if you know of previous installations that were improperly removed.



                                You could have some insight to this by opening "regedit" and searching for "Python27" - a registry key appeared in my command-shell Cache pointing at c:pythonpython27 (which had been removed and was not present when searching in the registry upon finding it).



                                That may help point to previously improperly removed installations.



                                Good luck!






                                share|improve this answer

























                                  up vote
                                  0
                                  down vote










                                  up vote
                                  0
                                  down vote









                                  Windows 7 64-bit, with both Python3.4 and Python2.7 installed at some point :)



                                  I'm using Py.exe to route to Py2 or Py3 depending on the script's needs - but I previously improperly uninstalled Python27 before.



                                  Py27 was removed manually from C:pythonPython27 (the folder Python27 was deleted by me previously)



                                  Upon re-installing Python27, it gave the above error you specify.

                                  It would always back out while trying to 'remove shortcuts' during the installation process.



                                  I placed a copy of Python27 back in that original folder, at C:PythonPython27, and re-ran the same failing Python27 installer. It was happy locating those items and removing them, and proceeded with the install.



                                  This is not the answer that addresses registry key issues (others mention that) but it is somewhat of a workaround if you know of previous installations that were improperly removed.



                                  You could have some insight to this by opening "regedit" and searching for "Python27" - a registry key appeared in my command-shell Cache pointing at c:pythonpython27 (which had been removed and was not present when searching in the registry upon finding it).



                                  That may help point to previously improperly removed installations.



                                  Good luck!






                                  share|improve this answer














                                  Windows 7 64-bit, with both Python3.4 and Python2.7 installed at some point :)



                                  I'm using Py.exe to route to Py2 or Py3 depending on the script's needs - but I previously improperly uninstalled Python27 before.



                                  Py27 was removed manually from C:pythonPython27 (the folder Python27 was deleted by me previously)



                                  Upon re-installing Python27, it gave the above error you specify.

                                  It would always back out while trying to 'remove shortcuts' during the installation process.



                                  I placed a copy of Python27 back in that original folder, at C:PythonPython27, and re-ran the same failing Python27 installer. It was happy locating those items and removing them, and proceeded with the install.



                                  This is not the answer that addresses registry key issues (others mention that) but it is somewhat of a workaround if you know of previous installations that were improperly removed.



                                  You could have some insight to this by opening "regedit" and searching for "Python27" - a registry key appeared in my command-shell Cache pointing at c:pythonpython27 (which had been removed and was not present when searching in the registry upon finding it).



                                  That may help point to previously improperly removed installations.



                                  Good luck!







                                  share|improve this answer














                                  share|improve this answer



                                  share|improve this answer








                                  edited Mar 9 '16 at 11:01

























                                  answered Mar 9 '16 at 10:50









                                  Jordan Stefanelli

                                  711166




                                  711166






















                                      up vote
                                      0
                                      down vote













                                      I know it is an old question, but I ran into this problem with 2.7 and 3.5. Though 2.7 would not show up in my default windows uninstall list, it showed up fine in the ccleaner tools tab under uninstall. Uninstalled and reinstalled afterwards and it has been smooth coding ever since.






                                      share|improve this answer

























                                        up vote
                                        0
                                        down vote













                                        I know it is an old question, but I ran into this problem with 2.7 and 3.5. Though 2.7 would not show up in my default windows uninstall list, it showed up fine in the ccleaner tools tab under uninstall. Uninstalled and reinstalled afterwards and it has been smooth coding ever since.






                                        share|improve this answer























                                          up vote
                                          0
                                          down vote










                                          up vote
                                          0
                                          down vote









                                          I know it is an old question, but I ran into this problem with 2.7 and 3.5. Though 2.7 would not show up in my default windows uninstall list, it showed up fine in the ccleaner tools tab under uninstall. Uninstalled and reinstalled afterwards and it has been smooth coding ever since.






                                          share|improve this answer












                                          I know it is an old question, but I ran into this problem with 2.7 and 3.5. Though 2.7 would not show up in my default windows uninstall list, it showed up fine in the ccleaner tools tab under uninstall. Uninstalled and reinstalled afterwards and it has been smooth coding ever since.







                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Mar 24 '16 at 14:14









                                          Ventian

                                          11




                                          11






















                                              up vote
                                              0
                                              down vote













                                              Uninstall the python program using the windows GUI.
                                              Delete the containing folder e.g if it was stored in C:python36 make sure to delete that folder






                                              share|improve this answer

























                                                up vote
                                                0
                                                down vote













                                                Uninstall the python program using the windows GUI.
                                                Delete the containing folder e.g if it was stored in C:python36 make sure to delete that folder






                                                share|improve this answer























                                                  up vote
                                                  0
                                                  down vote










                                                  up vote
                                                  0
                                                  down vote









                                                  Uninstall the python program using the windows GUI.
                                                  Delete the containing folder e.g if it was stored in C:python36 make sure to delete that folder






                                                  share|improve this answer












                                                  Uninstall the python program using the windows GUI.
                                                  Delete the containing folder e.g if it was stored in C:python36 make sure to delete that folder







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Aug 3 at 0:10









                                                  Patrick Mutuku

                                                  15718




                                                  15718






















                                                      up vote
                                                      0
                                                      down vote













                                                      It's actually quite simple.
                                                      When you installed it, you must have done it using some .exe file (I am assuming). Just run that .exe again, and then there will be options to modify Python. Just select the "Complete Uninstall" option, and the EXE will completely wipe out python for you.



                                                      Also, you might have to checkbox the "Remove Python from PATH". By default it is selected, but you may as well check it to be sure :)






                                                      share|improve this answer

























                                                        up vote
                                                        0
                                                        down vote













                                                        It's actually quite simple.
                                                        When you installed it, you must have done it using some .exe file (I am assuming). Just run that .exe again, and then there will be options to modify Python. Just select the "Complete Uninstall" option, and the EXE will completely wipe out python for you.



                                                        Also, you might have to checkbox the "Remove Python from PATH". By default it is selected, but you may as well check it to be sure :)






                                                        share|improve this answer























                                                          up vote
                                                          0
                                                          down vote










                                                          up vote
                                                          0
                                                          down vote









                                                          It's actually quite simple.
                                                          When you installed it, you must have done it using some .exe file (I am assuming). Just run that .exe again, and then there will be options to modify Python. Just select the "Complete Uninstall" option, and the EXE will completely wipe out python for you.



                                                          Also, you might have to checkbox the "Remove Python from PATH". By default it is selected, but you may as well check it to be sure :)






                                                          share|improve this answer












                                                          It's actually quite simple.
                                                          When you installed it, you must have done it using some .exe file (I am assuming). Just run that .exe again, and then there will be options to modify Python. Just select the "Complete Uninstall" option, and the EXE will completely wipe out python for you.



                                                          Also, you might have to checkbox the "Remove Python from PATH". By default it is selected, but you may as well check it to be sure :)







                                                          share|improve this answer












                                                          share|improve this answer



                                                          share|improve this answer










                                                          answered Nov 8 at 10:41









                                                          Anirudh Prabhakaran

                                                          84




                                                          84






























                                                               

                                                              draft saved


                                                              draft discarded



















































                                                               


                                                              draft saved


                                                              draft discarded














                                                              StackExchange.ready(
                                                              function () {
                                                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f3515673%2fhow-to-completely-remove-python-from-a-windows-machine%23new-answer', 'question_page');
                                                              }
                                                              );

                                                              Post as a guest




















































































                                                              Popular posts from this blog

                                                              Schultheiß

                                                              Verwaltungsgliederung Dänemarks

                                                              Liste der Kulturdenkmale in Wilsdruff