| msg281569 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-23 16:25 |
| While I am installing python when it gets towards the end of the installation the message appears "The program can't start because python35.dll is missing from your computer. Try reinstalling the program to fix this problem". Apart from this message the installation finishes successfully. When I type python into the command prompt the message appears again. I've tried as suggested installing again, it was installing to my local file C:\Users\myusername\AppData\Local\Programs\Python\Python35-32 so I thought it might be something to do with the path not being setting up correctly and have tried several locations. The installer doesn't seem to be adding the PATH file on installation to the system as well. This all started because pip stopped working and I was trying to re-install to resolve the problem. Any suggestions on a fix? Thanks, Mark |
|
|
| msg281580 - (view) |
Author: Steve Dower (steve.dower) *  |
Date: 2016-11-23 19:06 |
| Do you see a "Repair" option when running the installer again? If not, open Programs and Features and find Python there, double-click it and select "Repair". Otherwise, you should have a set of log files in your %TEMP% directory (sort by date and they all start with "Python"). If you can bundle those up and attach them to this issue, I can take a closer look. |
|
|
| msg281621 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-24 09:03 |
| Thanks for the message. I've tried using repair, reinstalling etc to no effect. I've ziped up the files I could find starting with Python in the temp file you mentioned. Thanks again for the help, Mark |
|
|
| msg281642 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-11-24 18:22 |
| Oh wow, I've never seen anything like this before. It looks like it's really confused about whether you've installed for all users or not. I wish I knew how you got into this state, because I'd like to be able to prevent it. I guess it's related to the current issue where the install registration is always for the current user, even when the install is for all users, but it still shouldn't be possible to get into this state. As far as cleaning up goes, try running the following commands from an elevated command prompt and then doing another install/repair. (Some of them may fail, which is okay.) msiexec /quiet /x {EB0611B2-7F10-4D97-BCF2-DCAAB1199498} msiexec /quiet /x {5DB2183B-62D3-407F-BBC1-EAD2F36283FA} msiexec /quiet /x {33B10015-A9B1-4210-B50A-26C6443979B0} msiexec /quiet /x {FCBB04F4-D2CF-4F55-BE92-B3898696B318} msiexec /quiet /x {9D50A6D7-410A-4469-87B7-35FA84CBD479} msiexec /quiet /x {1FBA5182-78DD-4940-9F06-96E5042B7061} msiexec /quiet /x {E6DEBF43-7ACF-4E88-9BBF-9B5945683281} msiexec /quiet /x {C1153533-FDC4-4922-892D-B71810F69566} msiexec /quiet /x {9ADF9987-3327-48C6-91B3-B10900366491} msiexec /quiet /x {7E08C4EE-B1C7-4138-8227-7CD3837636AA} reg delete HKCU\Software\Python\PythonCore\3.5-32\InstalledFeatures /f reg delete HKLM\Software\Python\PythonCore\3.5-32\InstalledFeatures /f /reg:32 |
|
|
| msg281689 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-25 09:29 |
| Hi Steve, Thanks looking into this for me. I tried the below and ran the lines in cmd with admin privileges. Then I tried running repair again. I'm afraid when I type python in the command prompt it has the same message as before about missing python35.dll. I know you said that not all the commands would work, however when I ran "reg delete HKLM\Software\Python\PythonCore\3.5-32\InstalledFeatures /f /reg:32" it couldn't find the file. I don't know if that helps at all. If you wanted to know how I caused this issue, I was having problems getting pip to work, so tried re-installing a few times(clicking generic user a few times in installation), into various locations, thinking it was something to do with the PATH. It didn't seem to be updating the path in the installation. Hence why it's a bit of a mess! Any suggestions on further cleaning I could do? Thanks again for all your help on this. |
|
|
| msg281736 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-11-25 20:08 |
| I was hoping that Repair wouldn't be an option after doing that cleaning. Maybe try uninstalling through Programs and Features, then run those commands again, go into the places you installed it and delete the files, and then run a fresh install. If you still get the Modify/Repair/Uninstall page when you run the installer, keep doing Uninstall until you get back to the Install/Customize page. |
|
|
| msg281849 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-28 09:39 |
| Hi Steve, I did as you suggested, removed following add remove programs, removed every instance of python I could find(folders etc.), cleared out the temp folder. Then I ran the commands you suggested(it couldn't find any of the registry keys this time), reinstalled from scratch and again when it was coming to the end of the installation the same message as before appeared "The program can't start because python35.dll is missing from your computer. Try reinstalling the program to fix this problem". I'm still getting the same issue. I was installing for all users, was that part of the problem? Thanks, Mark |
|
|
| msg281851 - (view) |
Author: Decorater (Decorater) * |
Date: 2016-11-28 09:53 |
| Normally when you install python systemwide it installs python35.dll in %SystemDrive%\Windows\System32\. Try looking there maybe you can use regsvr to register python35.dll in the registry or find where python.exe is and copy python35.dll to there. |
|
|
| msg281852 - (view) |
Author: Decorater (Decorater) * |
Date: 2016-11-28 10:02 |
| You could also download the embeded build which ships with python35.dll to put it in the folder you installed python to alongside python.exe. |
|
|
| msg281853 - (view) |
Author: Eryk Sun (eryksun) *  |
Date: 2016-11-28 10:05 |
| No, Python 3.5 is the first version to always place the interpreter DLL in the installation directory, beside python.exe. Installing for all users does not place python35.dll in "%SystemRoot%\System32". |
|
|
| msg281868 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-28 12:34 |
| Thanks for the advice, I downloaded the Python35.dll in the file located here https://www.python.org/downloads/release/python-352/ which was called "Windows x86 embeddable zip file". With this file when I enter python.exe the program crashes. I tried Windows x86-64 embeddable zip file however it said it was the wrong version. Am I using the wrong link? I tried repairing python and the installation processes deletes the python35.dll file in the directory and then the end of the installation says the same error as befere (python35.dll being missing etc.) Sorry about all the posts, would really like to get python working again! |
|
|
| msg281874 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-28 13:28 |
| Sorry realized I didn't say I put the python35.dll in the python 35-32 folder of the c drive with the above results. |
|
|
| msg281877 - (view) |
Author: Eryk Sun (eryksun) * |
Date: 2016-11-28 14:10 |
| Please zip and upload the installation logs since your most recent attempt in . They might help to figure out why it's doing a per-user uninstall that removes python35.dll. |
|
|
| msg281879 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-28 14:30 |
| I've attached all the files I could find in the temp file. Hope that helps. Mark |
|
|
| msg281902 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-11-28 18:05 |
| Looking at those logs, it seems like we think the per-user packages are already installed. When you go to do an all-users install, it "removes" the per-user packages, but passes in the same options as it does for the all user packages. Under the hood, these packages are actually identical, and we run them with different options depending on what sort of install you're doing. One of these options is the install directory. When we install the all users package to C:\Program Files, then remove the per user package from C:\Program Files, it's actually just removing itself immediately. I *think* the best way to deal with this, given that running the msiexec commands didn't work, is to do a Just for Me install first, and then uninstall that and do the All Users install. --- You can see in the main log file lines like this: [1B20:05AC][2016-11-28T11:44:53]i301: Applying execute package: core_AllUsers, action: Install, path: C:\ProgramData\Package Cache\{EB0611B2-7F10-4D97-BCF2-DCAAB1199498}v3.5.2150.0\core.msi, arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" TARGETDIR="C:\Program Files\Python35-32\" OPTIONALFEATURESREGISTRYKEY="Software\Python\PythonCore\3.5-32\InstalledFeatures"' [1064:274C][2016-11-28T11:44:59]i319: Applied execute package: core_AllUsers, result: 0x0, restart: None [1064:274C][2016-11-28T11:44:59]i329: Removed package dependency provider: {EB0611B2-7F10-4D97-BCF2-DCAAB1199498}, package: core_JustForMe [1064:274C][2016-11-28T11:44:59]i301: Applying execute package: core_JustForMe, action: Uninstall, path: (null), arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" TARGETDIR="C:\Program Files\Python35-32\" OPTIONALFEATURESREGISTRYKEY="Software\Python\PythonCore\3.5-32\InstalledFeatures"' [1064:274C][2016-11-28T11:44:59]i319: Applied execute package: core_JustForMe, result: 0x0, restart: None Notice that the package names (core_AllUsers, core_JustForMe) are different, but TARGETDIR is the same. It also seems that the packages are always ordered all users first - possibly this issue could be avoided if we did not interleave the packages, though you'd likely still not get a working install at the end. |
|
|
| msg281979 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-29 10:19 |
| I installed python just for my user, attempted to run python just out of interest in the command line and again the same error appeared (missing python35.dll). I uninstalled that then reinstalled for all users, and again during installation the message missing python35.dll appeared. Any other suggestions? Thanks for the help so far. |
|
|
| msg281992 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-11-29 14:48 |
| Could you attach those three sets of logs? I'm running low on ideas and need all the inspiration I can get :) |
|
|
| msg281994 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-29 14:58 |
| I've attached the logs, Thanks, Mark |
|
|
| msg282026 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-11-29 18:32 |
| That's only the most recent set, and all it shows is that the per-user install didn't help. Do you have the earlier sets of install logs for the per-user install and uninstall? I'd like to see why those didn't have the effect I expected. |
|
|
| msg282067 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-11-30 09:28 |
| This is everything I have in my temp file that I could possibly send you, hope it helps. |
|
|
| msg282231 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-12-02 08:40 |
| Hi All, Just wanted to check if there is any progress on the below? I understand it's a bit of a mess, however I use python in my day job(this is on my work pc) so any help getting it sorted would be great. Thanks again, Mark |
|
|
| msg282245 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-12-02 15:44 |
| Sorry, I got caught up in work stuff yesterday and didn't get a chance to go through these. I'll try and find time today. |
|
|
| msg282249 - (view) |
Author: Mark Harris (Marcopolo) |
Date: 2016-12-02 16:17 |
| No worries Steve, I've managed to fix it. I uninstalled, went through regedit & removed all mentions of python. I then installed python 2.7, installed 3.4 afterwards, uninstalled python 2.7 and for some reason that worked, it is working correctly now! Thanks for all your help, Mark |
|
|
| msg282251 - (view) |
Author: Steve Dower (steve.dower) * |
Date: 2016-12-02 17:54 |
| > installed 3.4 afterwards Did you mean 3.5 here? If you're going to change versions, I'd at least suggest grabbing the 3.6 beta - it's *much* better than 3.4, and we've had very little trouble with the most recent version (RC is coming in a week or two). |
|
|