This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Missing api-ms-win-core-path-l1-1.0.dll for python-3.9.0b1-amd64.exe Under Win7
Type: crash Stage: resolved
Components: Windows Versions: Python 3.9
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: Andrew Ushakov, ccanepa, honglei.jiang, lukasz.langa, mhammond, paul.moore, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2020-05-23 09:11 by honglei.jiang, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (10)
msg369707 - (view) Author: honglei jiang (honglei.jiang) * Date: 2020-05-23 09:11
Python.exe cannot run for missing  api-ms-win-core-path-l1-1.0.dll ,

api-ms-win-core-path-l1-1-0.dll is for only Windows 8?

https://github.com/microsoft/CNTK/issues/224
msg369910 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2020-05-25 19:23
Sorry, Windows 7 is no longer supported in Python 3.9. You'll need to update, ideally to Windows 10, but if you want to stay on Windows 8.1 then I believe that one's supported until Python 3.10.
msg371437 - (view) Author: Mark Hammond (mhammond) * (Python committer) Date: 2020-06-13 05:14
Can we get this mentioned somewhere? Eg, https://www.python.org/downloads/release/python-390b3/ doesn't mention anything about minimum versions. https://www.python.org/downloads/windows/ also has prominent notices like "Note that Python 3.8.3rc1 cannot be used on Windows XP or earlier." but nothing for 3.9

(This threw me for some time - I still have a win7 VM I used for testing and figured there was something broken in the VM before finding this)
msg371548 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2020-06-15 14:16
Łukasz can add a note to the release page, I believe.
msg375070 - (view) Author: Claudio Canepa (ccanepa) Date: 2020-08-09 14:37
At beta 5 the download page [0] says nothing about dropping win7 support.

The  installer, at least the one I tried ( python-3.9.0b5-amd64.exe ) will install on win7, and without warnings.

It would be much better if it refused to install.
msg375071 - (view) Author: Claudio Canepa (ccanepa) Date: 2020-08-09 14:38
opps, 

[0] https://www.python.org/downloads/release/python-390b5/
msg375072 - (view) Author: Claudio Canepa (ccanepa) Date: 2020-08-09 14:49
also, no mention in

https://pythondev.readthedocs.io/platforms.html
msg375073 - (view) Author: Paul Moore (paul.moore) * (Python committer) Date: 2020-08-09 15:00
https://docs.python.org/3.9/using/windows.html should probably be updated:

"""
As specified in PEP 11, a Python release only supports a Windows platform while Microsoft considers the platform under extended support. This means that Python 3.9 supports Windows Vista and newer. If you require Windows XP support then please install Python 3.4.
"""

Technically, the link to PEP 11 is sufficient, but "Python 3.9 supports Windows Vista and newer" is inaccurate.

If someone wanted to submit a PR, I'm sure it would be welcome.
msg405716 - (view) Author: Andrew Ushakov (Andrew Ushakov) Date: 2021-11-04 12:55
Is the missed api-ms-win-core-path-l1-1.0.dll library the only reason of the Python 3.9 and 3.10 incompatibility with Windows 7? I am asking because I just found replacement of this dll, compatible with Windows 7: https://github.com/nalexandru/api-ms-win-core-path-HACK, which allows to use Blender (with embedded Python 3.9) in Windows 7 environment.

Then I copied installation of Python 3.10 64-bit from Windows 10 to Windows 7, mentioned above DLL to the root sub-directory of Python 3.10 and was able to run Python. 

So my question is: is it possible to modify just a  Windows installer to allow installation to Windows 7? With warning, additional question, etc.?

Thank you in advance.

---
Andrew
msg405719 - (view) Author: Paul Moore (paul.moore) * (Python committer) Date: 2021-11-04 14:20
Well, we don't support doing that - so I'm not sure what you want beyond the statement "it's not supported". If it works for you, then by all means use it, but you'll be on your own for any issues you encounter unless you can reproduce them in a "normal" supported installation.

And I assume it goes without saying, don't do this in a production environment :-)
History
Date User Action Args
2022-04-11 14:59:31adminsetgithub: 84917
2021-11-04 14:20:15paul.mooresetmessages: + msg405719
2021-11-04 12:55:24Andrew Ushakovsetnosy: + Andrew Ushakov
messages: + msg405716
2021-04-08 11:08:37eric.smithlinkissue43661 superseder
2020-08-09 15:00:32paul.mooresetmessages: + msg375073
2020-08-09 14:49:16ccanepasetmessages: + msg375072
2020-08-09 14:38:40ccanepasetmessages: + msg375071
2020-08-09 14:37:45ccanepasetnosy: + ccanepa
messages: + msg375070
2020-06-15 14:16:12steve.dowersetnosy: + lukasz.langa
messages: + msg371548
2020-06-13 05:14:55mhammondsetnosy: + mhammond
messages: + msg371437
2020-05-25 19:23:06steve.dowersetstatus: open -> closed
resolution: not a bug
messages: + msg369910

stage: resolved
2020-05-23 09:11:53honglei.jiangcreate