homepage

I tried to install 3.5.1 32-bit into a fresh virtualbox image from https://dev.windows.com/en-us/microsoft-edge/tools/vms/mac/ (IE 10 on Win 7), and got this error message. When I try to run Python with "py -3", it will not run, it only shows:
 ---------------------------
 python.exe - System Error
 ---------------------------
 The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem. 
 ---------------------------
 OK 
 ---------------------------
I tried repairing the installation (with the control panel), which did not help.
I've attached the log files created by the installer.

The main log file reports that installing the CRT exited with the code ERROR_INSTALL_ALREADY_RUNNING (0x652): 
 Another installation is already in progress. 
 Complete that installation before proceeding 
 with this install.
You may need to completely reinstall to have it retry installing the CRT update.

This was my second attempt, and there is no other installation running.

This is in a virtualbox. I have my host OS files mapped in the guest Windows OS to drive N:. When I try to install by running N:\Downloads\python-3.5.1.exe, it fails with the error shown above. When I copy the file to the C: drive, it succeeds! ?

Packages are installed from the ProgramData folder on the system volume. For example, the log shows the CRT update executed as follows:
 "C:\Windows\system32\wusa.exe" "C:\ProgramData\Package Cache\
 D4036846864773E3D647F421DFE7F6CA536E307B\
 Windows6.1-KB2999226-x86.msu" /quiet /norestart
Is it installing from the same ProgramData directory when it succeeds?

I'm attaching another bunch of logs. There seem to be two installations here, one of which succeeded.

Sorry for letting this slide for a while...
Can you check (in Programs and Features, View Installed Updates) whether you have KB2999226 installed? If not, you can get it from https://support.microsoft.com/en-us/kb/2999226
In the first install, this component failed (hence the missing DLL error), and then in subsequent installs it wasn't re-run. I'm not sure exactly what happened here, but it's possible that the installation was deferred until the next reboot automatically. Being a Windows Update, we don't have much control over how these are managed and the operating system can basically do what it likes.

Steve, I do have that update installed.

Is your installation working okay then? You seemed to imply that in an earlier message, but I just want to confirm before closing the issue.