the named trojan appears in Microsoft Answers search returns to be (potentially) a false-flag
but I’d like to get your assurances please - because this will greatly impair our ability to use, and more importantly share these files with others (which we regularly do) - and would ask what remediation Enscape will undertake to ensure this be countered.
I understand that this is a problem of course, but due to the unsigned nature of packed .exe files, false flags can still occur I’m afraid.
Two potential solutions are being discussed internally for the future to circumvent this: generating .exe standalones through a web service (which requires large uploads) or including a standalone viewer application (which may overall complicate the overall user experience).
At the moment though we can only reccomend allowing that “threat” as long as it’s occurring with our generated .exe standalones. Hopefully this will not surface on many other users machines.