Failed to execute crypter.exe #83
Comments
|
Hello, what version of wxPython are you running? did you install the dependencies using the requirments.txt in this repository? |
|
Yes, exactly as you said i installed everything on requirements.txt. and there are no problems at all. But i'm still got a error message and can't run the program. |
|
Hey, I've just made a slight tweak to the way that PyInstaller is invoked by the builder. Can you pull the latest changes from this repo for the develop branch, then make sure you're on develop and try running the builder and building Crypter again? Let me know if this does/doesn't work :-) |
|
Hi, Doesn't work.
|
|
But I see no problem in the code. Except for UPX which doesn't compile perfectly. But i maybe i send this compiling code for you, and you can see where the problem. [2020-09-07 17:54:47]: Build Launched |
|
One thing I find very strange here is that your Crypter exe is 32MB, which it definitely shouldn't be. I'm building it currently without UPX and it's coming in at 13MB. Can you run the build again, but set the debug level at the top to "3 - High", then paste the console output in here again so I can take a look |
|
This is the build output when i set debug to high. But it seems the error in executing the exe still exists. [2020-09-15 21:54:49]: Build Launched |
|
Hmmm okay, I can't see anything wrong with that configuration. Can you try something? uninstall Pyinstaller from your system, and then reinstall it by running the following: pip install https://github.com/pyinstaller/pyinstaller/archive/v3.6.zip and then give it another go. I've had a search around and a few people have reported this as a fix. There might be something strange going on with your PyInstaller installation |
|
Hello, I've tried using the version of the pyinstaller you gave, but the exe file still can't be executed in windows. |
|
Can you try it using the method I mentioned though? When you installed PyInstaller 3.6 using the requirements.txt file, I believe there may have been a problem with the exact one you downloaded |
|
hi, as you said I have installed all the dependencies in requirement.txt according to the version.
|
|
Can you run the following: pip uninstall pyinstaller Then try again and let me know if it still doesn't work |
|
is it using python2 or paython3? when I run it an error appears when calling the pyinstaller [2020-09-15 22:26:39]: (ERROR): Builder: A Build failure occurred (2): Call to PyInstaller failed. Check that PyInstaller is installed and can be found on the system path |
|
Sorry, it's Python 3 so I suppose in your case the command will be: pip3 uninstall pyinstaller |
|
Hi, I've tried it on three windows machines 7,8,10 and still can't |
|
This is really strange. I haven't seen anyone hit this problem before. Are you running this on VMs? is there any way you'd be able to export one and upload it somewhere so I can take a closer look? I'm struggling to think of any other ways right now that I could investigate... |
|
hello I've done some testing, now it works, I've tried running it and installed it on another version of windows using a virtual box. It turns out that maybe my machine does not support because I have updated my previous version of windows to version 2004 and when I run it on windows version 1909 in virtual box everything works fine. |
|
how can i generate it with python extension only? |
|
Oh, well at least it seems to be working! It could be a Windows thing, but perhaps there are other versions of the dependencies/libraries that are conflicting, and that's why it works on a new instance of Windows. What do you mean Python extension only? like .py? Currently the builder only builds Crypter as a executable file (.exe). You can however run Crypter via the python script without building, by running: python3 Main.py from the Crypter directory |
|
Thanks for helping me, I've tried using Main.py. And I'll learn how the code works. |
|
No problem., sorry it took a while. If you have any more problems feel free to open another issue |
|
Hi, I tried to use the pyinstaller manually on the console, and when I finished making it the exe file can't be run / opened, what is the GUI / Builder.pyw actually doing so that it can make the executable file with pyinstaller run properly, whereas when I call pyinstaller automatically manually via the console with the command pyinstaller --onefile Main.py. It can't be run. |
|
If you want to know the exact command that the builder is running to create the executable, do the following:
[2020-09-15 21:54:52]: Builder: Running command: pyinstaller --noconsole --clean -F --noupx Main.spec There have been some updates so I'd definitely recommend following those steps and then using the exact command you see in your own console. Is there any particular reason you want to do it this way and not use the Builder? |
|
Hi, How do I generate Main.spec without being called by pyinstaller first. Shouldn't the pyinstaller run Main.py first before generating Main.spec? |
|
You can point pyinstaller straight at the main.py script yes, but it tends to be a little more complicated for more advanced executable building. In the case of Crypter, the user sets a number of options in the builder, some of which [I think] can't be specified directly on the command line when invoking PyInstaller. As a result, the Builder creates a custom Main.spec file from the settings specified in the Builder, and then points PyInstaller at the spec file instead of Main.py. This is one of the main purposes of the Builder application. The only way to generate a Main.spec is to either:
|
|
how do i create main.spec manually? |
|
If you open it in a text editor you'll see it's just a text file. You can then modify the settings |
|
from which main.spec actually appears. How can I edit it if I haven't created it yet. Can you explain it from the code, because I don't understand it when it is displayed in GUI form, because I am not used to it. |
Hi, can you help me, i run crypter.exe but i can't see the program run as well. I try to reopen 5 times but the error message always appear. This is the error alert:
Fatal error detected
Failed to execute script pyi_rth_pkgres
The text was updated successfully, but these errors were encountered: