When trying to use Legendary, I noticed that it didn't work on 7 because the latest releases use Python 3.9, it has the api-ms-win-core-path-l1-1-0.dll error.
To solve this, grab api-ms-win-core-path-HACK, and copy the x64 dll into %windir%\System32, and then copy the x86 dll to %windir%\syswow64.
Due to the way Legendary works, it extracts a minified Python 3.9 into %temp%, then it executes the code, because using an actually good coding language is too hard I guess. This means that the dll can't be used unless it is copied to the system folders. This probably works for more applications, I just don't know much that uses anything past 3.8.
Running Python 3.9-3.11 based applications on Windows 7
- K4sum1
- Lazy Owner
- Posts: 759
- Joined: 11 Jan 2021, 07:40
- OS: Windows 8.1 x64
- Has thanked: 385 times
- Been thanked: 178 times
- Contact:
Running Python 3.9-3.11 based applications on Windows 7
I tested this with the latest Python 3.11 (portable ofc) and it works with that, so this will work for a lot of applications for the foreseeable future.
R3n who?
- Darth Agnon
- Posts: 5
- Joined: 12 Feb 2023, 20:25
- OS: Windows 7
- Has thanked: 10 times
- Contact:
Running Python 3.9-3.11 based applications on Windows 7
There is also this project which supplies Python 3.9 to 3.11 installers that support Windows 7 and Windows Server 2008 R2, basically by including api-ms-win-core-path-HACK and modifying the installers.
- K4sum1
- Lazy Owner
- Posts: 759
- Joined: 11 Jan 2021, 07:40
- OS: Windows 8.1 x64
- Has thanked: 385 times
- Been thanked: 178 times
- Contact:
Running Python 3.9-3.11 based applications on Windows 7
I'd think it would be better to just remove the requirement instead of including the dll if you're already modifying source.
R3n who?
Who is online
Users browsing this forum: No registered users and 0 guests