-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run electrum 4.2.0 on Windows 7 (api-ms-win-core-path-l1-1-0.dll is missing from your computer) #7728
Comments
And to confirm, Electrum 4.1.5 did run on Windows 7, right? Is Win7 still getting security updates?
We did not realise we broke compatibility with Win7 -- the change was not intentional, but I wonder if Win7 is still worth supporting. Hmm, according to the Steam hw survey, 4.4% of Windows users (using Steam) are on Win7 these days.
|
Yes, Electrum 4.1.5 runs on Windows 7 without any problems.
Old hardware (no drivers for win 10 & 11), don't have time for upgrade, 99.9% of software (browsers, IDE, developer tools, etc..) still work on Windows 7 without problems.
According to StatCounter, global market share for Windows 7 is ~12%, and in some countries much higher: China ~32%, India ~25%, etc... |
I've tested this myself now. Documenting here for posterity.
|
Ah, I forgot that for the Windows builds we use the official binary builds of python from python.org (instead of cross-compiling from source on Linux, see #6565). New releases from the Python 3.8.x branch no longer get binary builds anymore, only source-only security fixes. (see https://peps.python.org/pep-0569/) This means that with our current build scripts if we wanted to bundle python 3.8, we would be stuck with 3.8.10, and not get security fixes. :/ |
Is it possible to build electrum with python from msys2 repository? I installed Python 3.9.11 from there and it seems to work on Windows 7. |
Not sure... do you mean we would build python from their sources, or that they distribute a binary and we could use that? We currently use the binary built by python.org, so we trust them. It is not ideal but I find this reasonable. We could try to cross-compile the msys2 python using mingw, as in #6565. If that could be made to work, I would actually prefer that to the status quo. However, that seems like a lot of work. PRs would be welcome. |
Possible ways to fix:
Note that any approach would require being able to build reproducible binaries (as is already the case), and we heavily dislike bundling pre-built binaries. Considering that
my decision for now is to drop support for Windows 7. If someone comes along and starts contributing towards supporting Windows 7, then we could potentially reintroduce support, however as it stands we don't have time to do it ourselves. Existing Win7 users can keep using Electrum 4.1.5 for the time being -- but they should consider upgrading or changing their OS. |
You might consider including the dll in the portable version, at least, since that would significantly increase its portability (likely a reason some people use the portable version).
Even now it represents 10% of Windows installs. https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide
That is an ominous "for the time being". I'm a happy user of Electrum on Linux so it's no skin off my own nose but I would like to be able to recommend Electrum to my friends without saying "The first step is back up all your files before we install a new operating system..." and in any case it should not be necessary to replace the host operating system to use "portable" software. |
When I start electrum-4.2.0.exe on Windows 7 I get this error:
The program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.
According to this, the problem is related to python 3.9, it doesn't support Windows 7.
Readme file for electrum contains Language: Python (>= 3.8), therefore, it should be possible to build electrum for Windows 7 with Python 3.8.
Could you please build the latest electrum with Python 3.8?
The text was updated successfully, but these errors were encountered: