Error when creating executable file with pyinstaller

6

I'm trying to create an exe for my python script using pyinstaller each time it runs into errors which can be found in a pastebin here.

Also when I double click the exe file it shows this error:

C:Users\Afro\AppData\Local\Temp_MEI51322\VCRUNTIME140.dll is either not designed to run on windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000007b

and then this:

Error loading Python DLL: C:\Users\Afro\AppData\Local\Temp_MEI51322\python35.dll(error code 193)

what's wrong, please?

python
python-3.x
exe
pyinstaller
asked on Stack Overflow Aug 7, 2016 by HackAfro • edited Sep 21, 2016 by Baris Demiray

4 Answers

5

I was haunted with similar issue. It might be that in your case UPX is breaking vcruntime140.dll. Solution to this is turning off UPX, so just add --noupx to your pyinstaller call.

pyinstaller --noupx --onedir --onefile --windowed get.py

Long explanation here: UPX breaking vcruntime140.dll (64bit)

answered on Stack Overflow May 3, 2017 by Waldi
5

I have also met this issue, and the root cause is that I am using upx to compress the file size. The solution is to exclude files which should not be compressed by upx:

pyinstaller --onefile --console --upx-dir=/path/to/upx --upx-exclude=vcruntime140.dll --upx-exclude=python36.dll my_script.py
answered on Stack Overflow Oct 14, 2019 by jdhao
1

In my case it was:

pyinstaller  --clean --win-private-assemblies --noupx --onedir --onefile script.py

--windowed caused problems with wxWidgets

answered on Stack Overflow Sep 17, 2018 by cy8g3n
1

I tried with this version of Pyinstaller commands, Add this commands to a .bat file and execute the .bat file. It worked for me:

pyinstaller --log-level=WARN ^
    --upx-dir <PATH_TO_UPX.exe_FILE> ^
    --upx-exclude vcruntime140.dll ^
    --upx-exclude ucrtbase.dll ^
    --upx-exclude qwindows.dll ^
    --upx-exclude libegl.dll ^
    --name <NAME_OF_APPLICATION> ^
    --onefile --windowed ^
    <PY_DEPENDENT_FILES.py>
answered on Stack Overflow Feb 24, 2021 by Prasad Nadiger

User contributions licensed under CC BY-SA 3.0