4 ms·
That's not true though. We have very little volume installs and since the EV, there has has not been one of these messages..
by mnkypete 8y ago
That's not true though. We have very little volume installs and since the EV, there has has not been one of these messages..
- slededit 8y agoI've had differing experiences. Note that if you've been distributing before you got the cert part of that rep will carry over as its also a function of the exe signature.
- mnkypete 8y agoI would check if something in the signing process is going wrong, refer to this (very long) SO thread: https://security.stackexchange.com/questions/109629/deprecation-of-sha1-code-signing-certificates-on-windows/113114#113114 https://security.stackexchange.com/questions/109629/deprecat... We actually switched certificates (from StartCom to Globalsign) and the signing was wrong at first, so the message kept showing. When we fixed it, it went away immediately, even though certificate and author name changed... Here's the article:https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/ https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-sma... "Programs signed by an EV code signing certificate can immediately establish reputation with SmartScreen reputation services even if no prior reputation exists for that file or publisher."