We had such an issue with SmartScreen just once, near the middle of the validity period of our code signing certificate (non-EV), when we released a new, usual beta version of our program.
For example, the certificate can be issued several months ago and used to sign many files, but with each signed file that you publish, it can take a few days for the SmartScreen to stop complaining about that file after you publish it. msi file) that builds trust over time, not the certificate. If your certificate is non-EV, it is a signed application (e.g. EV code signing certificates also have a unique identifier which makes it easier to maintain reputation across certificate renewals." Running this app might put your PC at risk.", with the two buttons: "Run anyway" and "Don't run".Īnother Microsoft resource states the following (quote): "Although not required, 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. Otherwise, the users will see a warning like "Windows Defender SmartScreen prevented an unrecognized app from starting. According to Microsoft, extended validation certificates allow the developer to immediately establish reputation with SmartScreen. Microsoft affirms that an Extended Validation (EV) Code Signing Certificate allows to skip this period of trust building. If you have a standard code signing certificate, some time will be needed for your application to build trust.
0 kommentar(er)
