Search found 12 matches
- Fri Nov 19, 2021 1:11 am
- Forum: Enigma Protector x64
- Topic: Getting access violation in Enigma trying to protect 64 bit EXE
- Replies: 1
- Views: 6540
Getting access violation in Enigma trying to protect 64 bit EXE
I'm getting this while trying to protect my app: Access violation at address 0067F30B in module 'Enigma64g.exe'. Read of address 24F41000 Here's the full log (with my EXE name omitted). (I'm not sure why I get the warning about the MAP file since I always do a clean and full release build before pro...
- Thu Nov 18, 2021 11:08 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
The promised follow-up... I am still getting a crazy number of "Are you sure you want to install that" messages from both Edge and Windows SmartScreen, but I'm guessing this isn't Enigma's fault. I love how Microsoft treats adults like children. This nagging won't go away until more people...
- Wed Nov 17, 2021 7:43 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
Ok, I ran a new installer (32 bit, protected) by VirusTotal and it came back with ZERO false positives. I'll try this out on an older laptop to see how many warnings I get from Windows. I *might* buy the 64 bit version of Enigma after all, but I'm still hoping for a discount! Having to pay twice for...
- Wed Nov 17, 2021 12:54 am
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
...and I found the cause of the problem. If you're using the JCL Debug routine and you enable the "Insert JDBG data into the binary" feature, that throws a wrench into the machine. SignTool fails to sign the app in that case. If you use EurekaLog (or similar), you don't need to enable this...
- Tue Nov 16, 2021 7:13 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
Since Adobe came out with a 64 bit version of Acrobat Reader, I'm now preparing a 64 bit version of my app. However, I'm probably going to have to leave Enigma behind because I have no desire to pay for this package all over again, just to get 64 bit support (unless you give a substantial discount)....
- Thu Nov 11, 2021 10:44 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
Surprisingly, Microsoft already got back to me (pinch me!). They removed the detection and told me how to update my Defender signatures. So I did that and: 1) I rescanned the installer at VirusTotal. This time, it got back false positives from Sophos (Generic ML PUA (PUA)) and FireEye (Generic.mg.26...
- Thu Nov 11, 2021 5:02 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Re: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
I submitted the protected executable to Microsoft for analysis, but they probably won't get back to me for days, if not weeks or months. Is there something Enigma can do to fix this?
- Thu Nov 11, 2021 4:40 pm
- Forum: Problems
- Topic: Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
- Replies: 8
- Views: 12073
Getting flagged with Trojan:Win32/Sabsik.FL.B!ml
I recently received my first code signing certificate and I signed the executable after protecting it, then make the installer from that, then signed the installer. Installs and runs fine, but when I run the installer through VirusTotal, Microsoft is flagging it as containing Trojan:Win32/Sabsik.FL....
- Wed Oct 13, 2021 4:41 pm
- Forum: Problems
- Topic: Can't use JCL Debug for stack trace with Enigma
- Replies: 2
- Views: 4809
Re: Can't use JCL Debug for stack trace with Enigma
I ditched the JCL Debug stuff, and bought and integrated EurekaLog. If you follow their recommendations, you can get a stack trace while still using Enigma. Just use E.StackTrace (where E is the Exception instance)...
- Mon Oct 11, 2021 3:47 pm
- Forum: Problems
- Topic: Can't use JCL Debug for stack trace with Enigma
- Replies: 2
- Views: 4809
Re: Can't use JCL Debug for stack trace with Enigma
Sorry, no attached images (I copied this from an email). My bad!