Windows 7 / 64-bit / 4 Gb Ram / Intel i5 processor. This seems to have been discussed intermittently in the past, but none of the previous answers fixed my problem. I installed 3.5, and when I tried running it (both from the Windows cmd line and from the python cmd line) I received the error "The prodecure entry point strncmp could not be located in the dynamic link library VCRRUNTIME140.dll" I installed 2.7.12 and received the same error. I then uninstalled 2.7.12 and installed 2.7.11 and found that running this worked from the python cmd line but not from the windows cmd line. I then tried installing 3.5.11 and found vcruntime140.dll in the python directory. I copied this to the python 2.7 folder, uninstalled 3.5.11 (and 3.5.12 – after realising that the original installation didn’t seem to have completed successfully anyway, despite saying it had!), and now when I run python from both the windows cmd line and python cmd line it seems to work.
Nothing in Python 2.7 depends on vcruntime140.dll, so you shouldn't be seeing that error from there. My guess is that you have an extension module that requires it, or possibly your PATH or PYTHONPATH variables were mixed up. It sounds like everything is working now? There's nothing actionable in this report unfortunately, unless you can reproduce the issue and help us diagnose it some more.
Ah, in that case: - I guess the issue would have been that the python 3.5 installation I tried (which was 3.5.0a1) had the vcruntime140.dll issue - I've realised that the 3.5* installation puts Python on the beginning of the PATH - whereas I was putting the 2.7 directory at the end of the PATH (so when I was testing 2.7 my PATH variable was being ignored by the 3.5 one. - I assume that the missing vcruntime140.dll was a known bug in 3.5.0a1 and was fixed in a subsequent release I should have probably realised all of this earlier!
