Fatal Error about crypter HOT 9 CLOSED

Hey! So the first thing the ransomware does is the encryption. Once that's complete it tries to open the GUI. So given that the encryption has run, the GUI must be what's causing the issue.

These kinds of problems are my number one priority right now, so you have my undivided attention, lol. Have you got Git installed on your machine right now? if so, do you have Git BASH? Git BASH seems to catch the errors whilst windows CMD and Powershell don't

If you open Git BASH, go to the bin directory that has the Crypter.exe executable in it, and run ./Crypter.exe. Then once you click OK on that "Fatal Error!" error box, you should get the error printed to the console :-)

from crypter.

Okay... I think I've figured out what the problem is! Can you try rebuilding but DONT use UPX. Leave the "UPX Packer Directory" field blank. I think there's some kind of strange issue with UPX at the moment. Can you let me know if this makes a difference? thanks

from crypter.

Fairly confident this is the problem here. Issue #32 was exactly the same and was fixed by not using the UPX packer. I'll get this fixed so that UPX can be used ASAP

from crypter.

Hey hi,
when u built the .exe i had upx disabled

from crypter.

Are you able to post the output of the Builder console?

from crypter.

So I think this problem is actually a combination of two things: UPX and an issue with wxPython version 3.0.0.0. I've since updated the distributable to use a newer version of wxPython which has fixed this problem. Please redownload the Crypter_distributable_2.0.zip package from here and let me know how that goes :-)

from crypter.

I am using your package XD

from crypter.

I have updated it several times though in the last few days (including when I posted my last comment), so you may have an older release. The new package has the correct version of wxPython (3.0.2.0)

from crypter.

Closed due to inactivity/assuming this is fixed given your responses to other issues

from crypter.