Windows Smart Screen

We just released a new version of our app with the latest TA binaries, which was the only change we made. Now our app is blocked by Windows 10 smart screen, even though we use an EV certificate. Not saying that the TA changes are the cause, but it is a possibility. Anyone else experiencing this? Wyatt, was everything signed in the usual way? (we resign the dlls, but not the exe - not sure why, that is just the way our installer does it).thanks,Matt

Hey Matt,

TurboActivate.exe (the only thing you might conceivably see a "smart screen" for) is dual-signed (SHA1 & SHA256) with EV code signing certificates. Similarly all of our binaries on platforms that support signing (Windows & macOS) are signed with these EV certificates.

That's the long way of saying we use the best possible certificates to sign all of our binaries and it gives them an "extra boost" with regards to things like "smart screen". So instead of seeing an ominous warning about the files, the user will be present with a "Yess/no" option when you try to launch the TurboActivate Wizard as an admin.

Long story short, any smart screen problems have nothing to do with TurboActivate.

Also, if you have an installer you'll want to sign that and all of your executables and dlls. Preferably with an EV certificate (because they do get that "extra boost").

Reply
Discard post