How to avoid the "Windows Defender SmartScreen prevented an unrecognized app from starting warning"

Question

My company distributes an installer to customers via our website. Recently when I download via the website and try to run the installer I get the warning message:

Windows protected your PC

Windows Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.

If I right-click on the installer and choose Properties I note the following:

Our installer is signed.

How do I find the reason for the Windows Defender SmartScreen warning?

I have not managed to find any log file for Windows Defender nor found anything in the Event Viewer.

Solution 1

If you have a standard code signing certificate, some time will be needed for your application to build trust. Microsoft affirms that an Extended Validation (EV) Code Signing Certificate allows us to skip this period of trust-building. According to Microsoft, extended validation certificates will enable the developer to immediately establish a reputation with SmartScreen. Otherwise, the users will see a warning like "Windows Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.", with the two buttons: "Run anyway" and "Don't run".

Another Microsoft resource states the following (quote): "Although not required, programs signed by an EV code signing certificate can immediately establish a reputation with SmartScreen reputation services even if no prior reputation exists for that file or publisher. EV code signing certificates also have a unique identifier which makes it easier to maintain reputation across certificate renewals."

My experience is as follows. Since 2005, we have been using regular (non-EV) code signing certificates to sign .MSI, .EXE and .DLL files with timestamps, and there has never been a problem with SmartScreen until 2018, when there was just one case when it took 3 days for a beta version of our application to build trust since we have released it to beta testers. It was in the middle of the certificate validity period. I don't know what SmartScreen might not like in that specific version of our application, but there have been no SmartScreen complaints since then. Therefore, if your certificate is a non-EV, it is a signed application (such as an .MSI file) that will build trust over time, not a certificate. For example, a certificate can be issued a few months ago and used to sign many files, but for each signed file you publish, it may take a few days for SmartScreen to stop complaining about the file after publishing, as was in our case in 2018.

We didn't submit our software to Microsoft malware analysis. Microsoft started to provide this service in 2017. It may be a viable alternative to an Extended Validation (EV) certificate.

In conclusion, to avoid the warning altogether, i.e., prevent it from happening even suddenly, you need an Extended Validation (EV) code signing certificate, and/or, you can submit your software to Microsoft malware analysis.

Solution 2

TL;DR

This warning is shown if your app doesn't have enough reputation with Microsoft SmartScreen yet. In order to gain reputation, you can either

• submit your app for malware analysis to Microsoft,
• buy an "Extended Validation" code signing certificate,
• buy a standard code signing certificate, or
• just wait for a long time.

Read on for the details about these different options.

Option 1: Submit your app for malware analysis to Microsoft

Microsoft allows software developers to submit a file for malware analysis. According to Microsoft, this will help developers to "validate detection of their products". If the review was successful, the Microsoft SmartScreen warnings will go away faster, or sometimes even instantly (it worked instantly for one of my own apps). You need to have a Microsoft account to submit your app for review.

However, note that if you release an updated version of your app, then you'll also have to request a new review again. To overcome this problem, you'll either have to use an "Extended Validation" or a standard code signing certificate (see below).

Option 2: Buy an "Extended Validation" code signing certificate

A guaranteed way to immediately and permanently get rid of the Microsoft SmartScreen warnings is to buy an "Extended Validation" (EV) code signing certificate from one of the Microsoft-approved certificate authorities (CA's), and to sign your app with that EV certificate.

Such an EV certificate will cost you somewhere between 250 and 700 USD per year, and will only be issued to registered businesses. If you're a single developer, you must be a sole proprietor and have an active business license. You can read more about the formal requirements for EV code signing certificates in the EV Code Signing Certificate Guidelines.

An EV certificate will typically be shipped to you by physical delivery on a hardware token.

Option 3: Buy a standard code signing certificate

The cheaper "standard" (i.e. non-EV) code signing certificates can also be used to permanently, but not instantly, get rid of the Microsoft SmartScreen warnings. Standard code signing certificates will cost you between 100 and 500 USD per year, and can also be issued to private developers without an active business license. Some CA's also offer discounts for open source projects.

No instant solution

The problem with standard code signing certificates is that they do not instantly silence Microsoft SmartScreen. Instead, some time will be needed for your certificate to build reputation before the warning will go away. However, once your certificate has built enough reputation, all applications signed with that certificate will be permanently trusted by Microsoft SmartScreen and won't trigger the warning anymore.

How long will it take?

So, how long will it take until the Microsoft SmartScreen warning will disappear when using a standard code signing certificate? Unfortunately, this is difficult to answer, since Microsoft itself refuses to publish any details about this. And since there is a whole bunch of information that Microsoft SmartScreen might use to decide upon trustworthiness, your mileage may vary greatly. According to inofficial numbers reported by various sources (see below), it usually takes between 2 and 8 weeks until the warning will permanently go away. However, keep in mind that this will also depend on how many downloads and / or installs your app has.

The inofficial numbers are:

• 42 days and about 1.400 app installs. Source: my own certificate (Feb 2021)
• 16 days and about 2.000 app installs. Source: my own certificate (May 2020)
• One month and more than 10.000 downloads. Source: here (Jan 2020)
• Between a few weeks and a month. Source: here (Dec 2019)
• About 2-3 weeks. Source: here (Dec 2019)
• About 3.000 downloads. Source: here (Dec 2013)

What you also need to know

Note that there is another catch with standard code signing certificates: When your old certificate has expired, the certificate reputation will not automatically carry over to the new certificate. What you can do in this case, however, is to re-sign a previously released product already signed with an already trusted certificate with your new/renewed certificate (resulting in two signatures). The original signature will continue to bypass SmartScreen and the new signature will help the new certificate to build up trust. You'd ideally even start this dual-signing phase well before your old certificate expires, so that your new certificate will become trusted before your old certificate expires.

Note that it's still strongly recommended to buy a standard code signing certificate with a long validity term in order to avoid the hassle with transferring your existing certificate reputation for as long as possible.

As a final note, always make sure that you're timestamping your signed apps. Timestamping is extremely important, as it will allow the signed app to remain valid after the certificate itself has expired. Make sure to use an SHA-2 digest algorithm (e.g. SHA-256) for both the file and the timestamp signatures. Also see this question for further details.

Option 4: Just wait for a long time

If you don't take any measures at all, the Microsoft SmartScreen warning will also go away eventually. This might however take a ridiculous amount of time (months) and / or downloads (tens of thousands). Another big problem is that each time you'll release an updated version of your app, the waiting period will start all over again. So, this probably isn't the solution you're looking for.

Solution 3

After clicking on Properties of any installer(.exe) which block your application to install (Windows Defender SmartScreen prevented an unrecognized app ) for that issue i found one solution

1. Right click on installer(.exe)
2. Select properties option.
3. Click on checkbox to check Unblock at the bottom of Properties.

This solution work for Heroku CLI (heroku-x64) installer(.exe)

Solution 4

UPDATE: Another writeup here: How to add publisher in Installshield 2018 (might be better).

---

I am not too well informed about this issue, but please see if this answer to another question tells you anything useful (and let us know so I can evolve a better answer here): How to pass the Windows Defender SmartScreen Protection? That question relates to BitRock - a non-MSI installer technology, but the overall issue seems to be the same.

Extract from one of the links pointed to in my answer above: "...a certificate just isn't enough anymore to gain trust... SmartScreen is reputation based, not unlike the way StackOverflow works... SmartScreen trusts installers that don't cause problems. Windows machines send telemetry back to Redmond about installed programs and how much trouble they cause. If you get enough thumbs-up then SmartScreen stops blocking your installer automatically. This takes time and lots of installs to get sufficient thumbs. There is no way to find out how far along you got."

Honestly this is all news to me at this point, so do get back to us with any information you dig up yourself.

---

The actual dialog text you have marked above definitely relates to the Zone.Identifier alternate data stream with a value of 3 that is added to any file that is downloaded from the Internet (see linked answer above for more details).

---

I was not able to mark this question as a duplicate of the previous one, since it doesn't have an accepted answer. Let's leave both question open for now? (one question is for MSI, one is for non-MSI).

View more solutions

Comments

[Andy]

It seems that the problem is that we are signing with a "Standard Code Signing Certificate". If we sign with a "Extended Validation (EV) Code Signing Certificate" we do not need to build trust by having our software installed by many users. Instead the certificate issuer undertakes a vetting process where they make sure we are a legit company. I suspect there has been a policy change with a recent Windows 10 upgrade. Anyway it would be really useful to be able to read logs from Windows Defender. Next time the problem might be something else, and it is a pain to find out what is wrong.

[Stein Åsmul]

What kind of money are we talking about for an EV Code Signing Certificate? Did you check? Without sounding too out there: who smells a racket? We are now "trust based" unless you dig deeper in your wallet? Strange with the overhead of "normal" certificates if they yield no trust? Do they hold water as "tampering proof " at least? Maybe see my comment below on Virustotal.

[Andy]

$410 vs $289 per year. I think it is almost fair enough. Seems they do a little bit of extra work like contacting the company by phone, looking up the company in official registers etc. Yes ordinary certificates guarantee that the installer has not been tampered with.

[Stein Åsmul]

Thanks for the information. Sounds like what they did 15+ years ago when getting a normal certificate? We had to provide quite a bit of information back then as well, but I guess things have de-evolved - price seems like back then though. The more things change, the more they stay the same - only the name changes? What about a mandatory malware check before such a EV certificate can be used? I mean, if they are into "trust" and "reputation" beyond pure tamper proof - that would be the better requirement over simply checking that the company exists? Don't you think? Signed malware - not great.

[Stein Åsmul]

Adding a link to an older Q/A: How to pass the smart screen on Win8 when install a signed application?.

[Josef Bláha]

@Andy, was you original certificate issued by CA in Windows Root Certificate Program? Did the EV certificate help?

[emkey08]

Also see stackoverflow.com/q/39437773

[Admin]

I had same issue with heroku.exe... I ran the installer from command prompt (in Administrator mode) just by typing path where the installer is (e.g.: C:\Downloads\heroku-x64.exe) and press enter and I was able to install it which was previously being blocked...

[Christopher Painter]

It's all a scam IMO. I've helped a few customers worth through this. The rail PITA is that the process requires a FIPS 140-2 Level 2 token which makes automating builds a real challenge.

[Stein Åsmul]

Maybe just running the setup through virustotal.com and then waiting a couple of days could affect the trust? Who knows? In essence it is just an "unknown binary" before it is identified by security software. Doubt it would help much, but worth a try.

[Stein Åsmul]

Maybe the telemetry from Windows Defender is what is actually being used? As such, maybe run Defender on several PCs that also chat back to Microsoft as well? I don't know much about this, just that "something" is being sent back to the death star :-). I would run Defender on my MSI and also its administrative image (will be without a digital certificate) and see what happens. Great if someone could illuminate what actually happens for such telemetry data.

[user2568374]

this doesn't solve it for other people downloading it!

[jay thanki]

May be you are doing something wrong or may be your (.exe) is corrupted. @user2568374

[Bastion]

This is the better solution. Windows Defender was blocking the Kaspersky AVZ anti-viral toolkit :-O

[Developer404]

You saved me. This works. Anyway I am installing SAM from AWS which is suppose to be secured

[Stein Åsmul]

Sharing a link to a similar answer on SmartScreen. "Buying trust"... Hmmm...

[lkessler]

An EV Certificate is only availalbe to someone with a registered company. If you are an Independent Software Vendor without a registered company, you cannot purchase an EV Certificate.

[Ado Ren]

Can confirm that option 1 got rid of the warning within 24h for.

[samiksc]

Overall a very good summary of the options, very useful indeed! However, submitting app to the app store (option 4) will NOT do the trick. When 'reputation based protection settings' is turned on in Windows Security console, 'app store apps check' is also turned on by default. So if you are developer of the app, your app will still get the warning even if it is submitted to the app store and a user downloads from the app store. User will need to specifically turn off this check, which as a developer, we can't mandate.

[emkey08]

@samiksc Thanks for pointing this out. You're right, SmartScreen is actually also enabled for Microsoft store apps by default (in Windows 10, at least). I've updated my answer and have removed the Microsoft app store option.

[Steve Rindsberg]

This turns into something like the old "Nobody will hire you w/o experience and you'll never get experience until somebody hires you" problem. The current message from SmartScreen is basically just "You don't want to do this and because you're too stupid to make your own choices, we won't even give you the option." So if it won't let anybody run the thing, how, exactly, is it supposed to build up trust?

[emkey08]

@SteveRindsberg During the initial phase when your new code signing certificate isn't trusted yet, you can submit your app for malware analysis to Microsoft in order to avoid the Windows Defender warning. But still, make sure that you additionally always also code-sign your app, so that your certificate can build up trust.

[Steve Rindsberg]

@emkey08 Thanks for the reply, but I've had a code signing certificate for over five years, and just renewed it in December 2021. I'd think that after even 6 months it'd no longer be considered "new". I code sign all of my MSIs and the code within them, but my client's still getting a Defender warning. Submitting the thing to MS every time there's change (happens VERY often when the app's under development) is a non-starter. IMO, MS has just gone over the top with this.

[harry]

Regarding SmartScreen exemption not carrying over to renewed certs: the trick is to go back and re-sign a previously released product already signed with an already exempted cert with your new/renewed cert (resulting in two signatures). The original signature will continue to bypass SmartScreen and the new signature will give the new cert the street credit it needs to become exempted.

[emkey08]

@MahmoudAl-Qudsi Thank you very much for pointing this out. I've included your comment into the answer.