Error loading python dll loadlibrary не найден указанный модуль
Что делать? У меня даже НФС НР не работает похоже это все из за этого.
А ещё ms_config, не открывается сообщает об ошибке.
Вот ответ на ваш вопрос.
Если вы достаточно эрудированы - вы поймете.
Ответ:
So some program that is running at start-up is expecting you to have Python available so I guess relevant questions are
Do you have Python installed?
Did you recently delete python from your machine?
Are you aware of installing any programs that require Python?
Have you run a virus scan recently?
Have you checked your Startup menu for unexpected items?
Have you run msconfig and checked the Startup programs there?
Have you tried temporarily removing start-up programs until you have found the one that causes the problem? (You need to exercise caution when doing this)
Проще говоря по-русски:
1)Или вы ставили Питон, потом криво удалили и пошли глюки.
2)Или вы ставили что-то, чему нужен питон, потом это слетело и пошли глюки.
3)Или у вас вирусня, от которой нужно избавляться (скорее всего) , установите утилиту Dr. Web Cure IT и проверьте ей весь компьютер.
4)Или мы мучали msconfig и реестр - и что-то из этого в итоге начало работать не так.
5)Или за счет какой-то проги начало рушиться ядро.
6)Или винда решила сделать харакири (она это любит) .
В любом случае, ваши действия:
1)Проверить Dr Web Cure it компьютер, если чето найдет и удалит - хорошо.
2)Если не помогает - сносите винду, от питона хрен избавишься, от вирусни - тоже (если 1 шаг не помог)
3)ВСЕГДА имейте КУПЛЕННЫЙ лицензионный антивирус и будет вам счастье, я рекомендую Norton 360, но сразу предупреждаю - для него нужен компьютер как минимум средней мощности, иначе система и все программы будут тормозить.
Всегда рад помочь.
я не знаю что тут у меня делали, но появлятся стала ошибка данного вопроса,а после нее C:\\Programs Files\Uniblue\Registry Booster\PYTHON26.DLL
этот вустер скачан с интернета. епт. гворила ж брату, не надо это скачивать.
I am new at programming. I wrote a small program in python and converted it to .exe file with pyinstaller . Now when i try to open the .exe file a black screen appears and closes immediately. I was able to get a screenshot:
I saw a solution like adding input() at the end of the code but it didn't work either. My code:
3 Answers 3
This worked for me:
Had the same issue but then realized that I was inadvertently trying to execute the file in the build folder instead of the dist folder.
Looks like you might be making the same mistake from your traceback so see if using the executable in dist doesn't fix it for you
This solved the problem for me as well. Why isn't this in the manual? Based on the number of questions about it, seems like it would save a lot of people's time if it was.
So, I found it in the Usage. But I still think it should be spelled out more clearly in the written guide.
The problem seen in the screenshot is that the Python Library cannot be found. So some configuration in your pyinstaller is wrong. Are you sure that python36.dll is in that folder? Check where your python36.dll is located (normally in the same folder where your python installation is located and your python.exe can be found). Maybe you need to add this path to your Windows Path Configuration?
Please check the following two answers to see if your pyinstaller is configured correctly:
The situation should be similar for you with Python 3.6
Which means by the way that your program cannot be run at all. You can still run your python file directly to see if that works by opening a command line and running it with something along the lines python myfile.py if your script is called myfile.py
I checked the folder, there is python36.dll. I added path and reconverted the program. Still same. It worked with command line
Did you also try this on another platform? Does it work there?
try the latest development version, using the following command:
Legorooj commented Jun 27, 2020
@XtremeGood exclude_binaries=False should work just fine. Let me try and replicate
Teut2711 commented Jun 26, 2020 •
@altendky no. I just know that some people have had success building on windows 10 and running on XP.
@XtremeGood if my solution doesn't work you could try building on XP - note that you'll need to build python yourself though.
Ya I tried to look for installation methods for python on xp but there is no installer available for lower versions of python.
Teut2711 commented Jun 27, 2020 •
@Legorooj I had refreshed my pc(win 10 64 bit) yesterday and thus reinstalled all pythons. I installed python 3.7.7 and Python 3.8.3. Pyinstaller on venv with python 3.8.3 gave the same .dll error as in the topic with exclude_binaries=False and pyi pyth- gres kind of error (this actually had to fail since pyinstaller works with python 3.7). With venv with Python 3.7.7 on exclude_binaries=True I was able to build it without error whereas with exclude_binaries=False gave the same error. I was using pyinstaller-develop edition from GitHub to build this. I tried various combinations to work it out.
This issue can be closed or if it is possible you tell me what I can give you to catch the bug. I remember I deleted setup.py before building the code. I guess I saw some change in the logs with it's deletion too. It might be that I'm doing something wrong. I don't know.
Legorooj commented Jun 26, 2020 •
@XtremeGood apologies; I got it the wrong way round. You need to build on windows 10 for it to work on 7. The generated executables might work on XP but no guarantees.
@altendky is partially right; to build on windows XP you need python 3.4. However, an executable built with a newer version on a newer windows might work as I said above.
Teut2711 commented Jun 28, 2020
Ok, what about setup.py ? Can it also be a reason for the strange errors?
Legorooj commented Jun 28, 2020
@XtremeGood setup.py shouldn't affect the build.
Teut2711 commented Jun 29, 2020 •
Hmm, then `exclude_binaries` could be the problem. Unfortunately despite being a windows user I know nothing about dlls and binaries and thus can't be of any help here.
Legorooj commented Jun 24, 2020 •
@XtremeGood if you've got the project working, then great!
We don't actually officially support windows 7 anymore - PyInstaller mostly works on it though. I would suggest that if you want it to work on 7 and 10, build on 10 and it should work.
Teut2711 commented Jun 24, 2020 •
ok, just give me a few minutes.I pip uninstall pyinstaller and now python setup.py install the pyinstaller-develop from github
A minimal example program which shows the error
Well, I can post an image of project directory.
When I run mailer.exe by going into dist
I check too many popup dialogs which I close by terminating process through task manager.
Header of popup box says Tracing.
[1348] Pyinstaller Bootloader 3.x
10 more messages(too much to type for me)
Error loading Python DLL
C:\Users\Dell\AppData\Local\Temp_MEI140002\python37.dll
LoadLibrary:The specified module could not be found
I tried setting debug=True in a.spec and even setting exclude_binaries with both True /False, console True/False but nothing worked after wasting 3+ hours.
Teut2711 commented Jun 24, 2020 •
I ran pip install -U pyinstaller and then pyinstaller --clean a.spec. Did you mean this? And I just ran it. -U is for upgrade only I think.
Teut2711 commented Jun 27, 2020
Thanks @altendky . I can build it on xp now.
Teut2711 commented Jun 24, 2020 •
Lol, yes old GitHub looked better. I can't really show the diff because I made this project learning pyqt5 and really didn't use git and so no version history. I can surely push the latest commit to github(since once it was build successfully I did create a repo) and you can clone it from there.
Make sure everything is packaged correctly
- start with clean installation
- use the latest development version
- Run your frozen program from a command window (shell) — instead of double-clicking on it
- Package your program in --onedir mode
- Package without UPX, say: use the option --noupx or set upx=False in your .spec-file
- Repackage you application in verbose/debug mode. For this, pass the option --debug to pyi-makespec or pyinstaller or use EXE(. debug=1, . ) in your .spec file.
Teut2711 commented Jun 24, 2020 •
I couldn't see any effect of --debug=bootloader
altendky commented Jun 26, 2020
I don't know what security fixes you might be missing with this, but given it's been EOL for awhile and we are talking about also EOL Windows XP, perhaps it doesn't really matter.
Teut2711 commented Jun 24, 2020
Deleted the setup.py and recreated the virtualenv and I saw something no module found in the logs.
Legorooj commented Jun 24, 2020
Please use the very latest development version - I added commits today. Then add images of the dialog boxes when running a build using --debug=bootloader .
altendky commented Jun 25, 2020
XP is going to require you go all the way back to Python 3.4.
Legorooj commented Jun 24, 2020
@XtremeGood you're running a onefile build. Can you just check that it works as a onedir build.
Legorooj commented Jun 24, 2020
@XtremeGood what are the edits you made since it last worked? Can I have a diff?
altendky commented Jun 26, 2020
The part of Python that dropped XP compatibility in 3.5 is 'stripped out' by pyinstaller?
Legorooj commented Jun 26, 2020
@altendky no. I just know that some people have had success building on windows 10 and running on XP.
@XtremeGood if my solution doesn't work you could try building on XP - note that you'll need to build python yourself though.
Teut2711 commented Jun 25, 2020
@XtremeGood if you've got the project working, then great!
We don't actually officially support windows 7 anymore - PyInstaller mostly works on it though. I would suggest that if you want it to work on 7 and 10, build on 7 and it should work.
Actually the client has win 7 32 bit and I do development on win 10 64 bit. That's why I was asking if it could be possible to build on win 10 a version that supports win 7. The client has most pcs win xp and a few win 7. Therefore I was going to ask if it was possible to build it for xp but ok.
Teut2711 commented Jun 24, 2020 •
Despite of that it works finally, so my guess is setup.py was the bug or exclude_binaries=False was the bug.
I used exclude_binaries=True to build this.
Since it is build succesfully on windows 10 64 bit, can you tell how can I build it such that it works on windows 7 32 bit too?
Legorooj commented Jun 24, 2020
@XtremeGood as long as it's within the last 30 minutes, that's fine. Please edit the spec file to use EXE(. debug=True, . ) then build again before posting screenshots of the dialogs.
Teut2711 commented Jun 24, 2020 •
No good, still errors persist. I get the same error when I run the .exe
Error loading Python DLL C:\Users\Dell\AppData\Local\Temp_MEI140002\python37.dll LoadLibrary:The specified module could not be found
Is pyinstaller incompatible with python 3.7.5?
Well, if more info is needed, I can paste images of all popup's if you allow.
Stacktrace / full error message
The text was updated successfully, but these errors were encountered:
Legorooj added kind:support state:need info Need more information for solve or help. labels Jun 24, 2020
Teut2711 commented Jun 24, 2020
It's not onefile build definitely. You can see the surrounding dependencies or I can post a better picture.
Teut2711 commented Jun 25, 2020 •
Is the project available somewhere?
It is, you only built it for me. I have hardly changed anything but will push the latest change.
Legorooj commented Jun 29, 2020
@XtremeGood thanks for the offer, but I run Windows primarily and as much as I've never tinkered with the DLL searching much I'm a very fast learner. Give me a few days to try and replicate. In the meantime use whichever solution you got to work.
So, I have a new work laptop that I just upgraded to Windows 10, and I installed Google Drive (apparently it’s now called Backup and Sync by Google), and everything went fine for a while, I can put my files in a specific folder, and everything just syncs fine.
If this error also occurs to you, here are some tips to help you resolve the error when loading the Python DLL in Windows.
How can I fix the Python DLL loading error?
1. remove the temporary folder
- Open the file explorer and navigate to the following location :
C:WindowsTemp - Press Ctrl + A to select all items in the temp folder.
- Right-click on the files and select Delete.
- Then navigate to the following location:
C:UserNamesAppDataLocal - Right-click on the “Temp” folder and select “Properties”.
- In the Properties window, open the Security tab.
- Select the username and click the “Edit” button.
- In the User Name Permissions section, make sure the Total Control check box is selected.
Error: The file name is not specified. - Click Apply and OK to save your changes.
- Click OK to close the Temp Properties window.
- Open the “Temp” folder and delete all files in it.
- Try installing or opening the Backup and Sync application and see if there are any improvements.
Deleting temporary folders fixed the error in loading the Python DLL in apyinstaller for many users, so we recommend you try this.
Temporary folders may contain corrupted files that the application cannot process, leading to an error.
If this does not solve your problem, we recommend that you try third-party software.
DLLs and Registries are valuable data libraries that Windows uses to function properly.
As a result, damaged or missing DLLs or registry keys can be a major cause of crashes, lockups and error messages, and even prevent you from running Windows software and functionality in general.
Unfortunately, registries and DLLs are piles of data that are difficult for even advanced users to configure properly without advice or even help from Microsoft.
Moreover, restarting the Windows operating system is one of the few really effective solutions to correct these errors, but this solution has too many drawbacks.
Error: The file name is not specified.
To avoid all this, you can always turn to third-party automated solutions, and few are as good as Restoro. It automates almost every aspect of the PC repair process, from scanning to the actual repair.
Follow this short guide to find out how to restore your PC’s optimal performance with Restoro :
- Download and install Restoro
- Start Restoro
- Restoro is now collecting data about your PC.
Error: The file name is not specified.
- Wait until it finds problems with system stability and possible malware infections.
- Once the scan is complete, Restoro will show you an overview of the current status of your PC.
Error: The file name is not specified.
- Click on “Start Recovery.”
- Restoro will now start downloading and replacing the corrupted registries, DLLs and other damaged files found during the scan.
- This is made possible by online libraries that are used for comparison and replace damaged data with their functional equivalent.
- Restart your PC for all changes to take effect.
Now your computer should be working properly and you won’t have to worry about slow response times, BSoD errors or anything like that.
Warning: This program must be updated from the free version to perform some specific actions.
2. Perform backup and synchronization as an administrator.
- Open the folder where the backup and synchronization program is stored.
- Right-click on the installer.
- From the context menu, choose Run as Administrator. When prompted to click the UAC button, click Yes.
Error: The file name is not specified. - The installation program should now install without any problems.
If you have a problem with Google’s backup and sync function, do the following
- Right-click on the Dekstop application icon.
- Select “Run as administrator.”
- When prompted to click the UAC button, click Yes.
Sometimes you only need administrative rights to resolve a Python dll loading error, so be sure to try this method.
3. work in compatibility mode
- Open the file explorer.
- Navigate to the following location:
C:Program FilesGoogleDrive - If you are using a 32-bit operating system, tryC
:Program Files (x86)GoogleDrive - Right-click Googledrivesync.exe and select Properties.
- Open the Compatibility tab in the Properties window.
- Select the Run this program in compatibility mode check box.
Error: The file name is not specified. - Select a version of the operating system that is older than the version installed on your system.
- Click Apply > OK to save your changes.
Running Backup and Sync from Google in compatibility mode can help fix Python python39.dll DLL loading error and other Python DLL errors.
Python DLL Google Sync and Backup download error from Google can occur due to both resolution and compatibility issues. In this article, we have listed all the possible solutions to help you solve this problem.
Editor’s note: This article was originally published in May 2022 and revised and updated in February 2022 for the sake of timeliness, accuracy and completeness.
Related Tags:
error loading python dll loadlibrary the specified module could not be found, error loading python dll python27.dll (error code 5) windows 10, error loading python dll python27.dll (error code 126), error loading python dll anki, pyinstaller, google drive, %userprofile%\appdata\local\
Legorooj commented Jun 24, 2020
Sorry I keep pressing the wrong button :-). Still getting used to this theme change.
altendky commented Jun 24, 2020
Is the project available somewhere?
Teut2711 commented Jun 24, 2020 •
Teut2711 commented Jun 24, 2020
Strange now I 'm getting only one popup compared the the lots of when I initially posted this issue.
Читайте также: