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...

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...

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...

...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...

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)....

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...

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?

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....

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)...

Sorry, no attached images (I copied this from an email). My bad!