[issue22329] Windows installer can't recover partially installed state
Ethan Henderson added the comment: I have the same issue on 3.4.3 x64 on Windows 10 x64. I set PYTHONHOME and PYTHONPATH (Just to C:/Python34), but that didn't fix the problem. -- nosy: +Zbee ___ Python tracker <http://bugs.python.org/issue22329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22329] Windows installer can't recover partially installed state
Ethan Henderson added the comment: I deleted those variables and tried running a repair but still got the "specified account already exists" schpeel. I then tried running an uninstall and got the same error as last time there too. There's presently no pip at all; there is no python folder on C:/. -- ___ Python tracker <http://bugs.python.org/issue22329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22329] Windows installer can't recover partially installed state
Ethan Henderson added the comment: Running that in my command prompt outputs "Access is denied," even after disabling UAC. Running that in bash just gives me a popup for Windows Installer. Is the UUID going to be different for 3.4.3 intel x64 (I have intel, not amd)? -- ___ Python tracker <http://bugs.python.org/issue22329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22329] Windows installer can't recover partially installed state
Ethan Henderson added the comment: My log.txt: http://puu.sh/jqLWR.txt Turns out that my antivirus was blocking that command from running before. -- ___ Python tracker <http://bugs.python.org/issue22329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22329] Windows installer can't recover partially installed state
Ethan Henderson added the comment: I managed to resolve the issue following these steps: 1. Installing Python 3.4.3 on another computer (not even the same architecture) 2. Copying the Python34 folder from that other computer to the computer I broke 3. Running the uninstaller for Python 3.4.3 4. Reinstalling Python 3.4.3 normally as it is now removed correctly I also replicated this error in 2.7.10 and fixed it with only slightly different steps: 1. Installing Python 2.7.10 on another computer (again, not even the same architecture as the broken computer) 2. Copying the Python27 folder from that other computer to the computer I broke 3. Running the repair tool for Python 2.7.10 4. Running the uninstaller for Python 2.7.10 5. Reinstalling Python 2.7.10 normally as it is now removed correctly I replicated the issue in 2.7.10 again afterwards, and it does appear that step 3 is required. -- ___ Python tracker <http://bugs.python.org/issue22329> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
