-
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
Error loading Python DLL #3171
Comments
So I take it you've used the "Windows Installer" exe? |
Yeah. I did try the standalone version though, same issue. |
Ok. I can reproduce on Win7 x64 [Version 6.1.7601], with all three Windows binaries. |
Reproduced on Windows 8.1 x64 [6.3.9600] with standalone and "Windows installer" exe. The fatal error message is different, "LoadLibrary: Invalid access to memory location." |
Correct behaviour / can't reproduce on:
|
I am also getting the same problem when updating. Hopefully a fix will be in soon, likely a problem with Win7/8 OS issue. |
I'm having the same issue on Win7 64b, also installed over 2.9.3. |
I have the same problem |
Issue confirmed here as well.... Win 7 64 bit.... same issue for installer and standalone exe.
|
Same here on Win 7 64bit |
Having the same issue Win 7 64 bit, I tried what is recommended in hotfix referenced above but getting same Errors |
@blais1064 of course you're getting the same errors. That is a pull request... The instructions for end-users there are only relevant with that change merged into the code, for newly built binaries. Please don't comment here if you have no new info to add. Some related links (for devs): |
This raises the question about if Electrum should maintain compatibility with OS that are not even supported by their own creators. For example, the end of Microsoft Mainstream support for Windows 7 was January 2015. Although, Microsoft will maintain the Extended support for Windows 7 until 2020 (mostly security updates - no bug fixes). For MacOS, El Capitan (10.11) reached the no-support status from Apple last month (with only security update until next fall - 2018). Apple maintains a shorter three years cycle, as all the updates are free. We have seen issues recently with both of those two operating systems. I guess it is up to the devs generosity to spend time fixing compatibility issues related to obsolete Operating Systems. |
Same issue here on Windows 7 Starter 32 bit with this version of Electrum: What can I do, to bring it to work? Can I downgrade to Version 2.9.3? Does this work without losing anything? Thank you. |
Fixed for me with v3.0.1! |
closing this. I added a note on the website, for machines that need a windows update. |
Update worked for me also, 3.0.1 on a pair of Windows 7 SP1 x64 Note: There is an x64 as we as a x86 version, take care to download the correct version of the Windows Update though are unsure if it makes a difference. |
Old issue, but just thought I'd add that I got the same error with 3.0.4 on Windows Vista and installing KB2999226 did the trick. So if anyone is trying to run Electrum on a really old Windows machine they have hope. |
I start electrum after install onto clean Win7 x64, first error electrum throws is it can't find: "api-ms-win-crt-runtime-l1-1-0.dll" I learn this is part of "vcredist_x64.exe", so I try to install that, but the installer for it throws an error about certificates and wont install. Obviously this machine wont be going online to update certificates, so I manually copy the api file into electrum folder, then electrum throws the error regarding python36.dll I decide to forget about trying to run cold wallet, and just go ahead and download electrum on another online machine. Windows smartscreen blocks the download. Good times... |
Just updated to the version 3.0 and I got this error after starting Electrum.
Does anyone know how to fix that? Tried reinstalling and restarting, but after quickly looking on google the only result I found is this github issue, which doesn't help me much...
Edit: Windows 7 x64, in case that matters.
The text was updated successfully, but these errors were encountered: