Home / Blog / Industry News
"Windows Protected Your PC" After Code Signing: Why and What to Do
Signed installers still trigger SmartScreen, and since 2024 EV certificates no longer skip it. How reputation works, how to check your signature, and what reduces the warning.
You bought a code-signing certificate, signed your installer, and users still see the blue "Windows protected your PC" screen with "Microsoft Defender SmartScreen prevented an unrecognized app from starting". This is one of the most common complaints from software publishers, and Microsoft now documents that it applies to EV certificates too. Signing is necessary, but it is not what SmartScreen is checking on its own. This post explains how SmartScreen decides, what changed for EV, and what you can actually do about the warning.
Signing and reputation are two different things
A code signature answers "who published this file, and has it changed since?" SmartScreen asks a different question: "has Microsoft seen enough people run this without problems?" According to Microsoft's own documentation, SmartScreen looks at two signals:
- Publisher reputation: is the file signed, and does the signing certificate have a good history?
- File hash reputation: has this exact file been downloaded and run by many users without signs of malicious behaviour?
A new, unknown publisher certificate and a new file hash both start with no reputation. So a correctly signed first release still triggers the warning. The difference from an unsigned file is that the dialog, after "More info", shows your verified publisher name instead of "Unknown publisher".
What changed for EV certificates
For years the standard advice was "buy an EV certificate and the SmartScreen warning disappears immediately". That is no longer true. Microsoft's SmartScreen reputation page for Windows app developers (learn.microsoft.com) now states that EV certificates no longer bypass SmartScreen, that the old behaviour "no longer exists", and that paying a premium for EV solely to avoid SmartScreen warnings is no longer justified. EV and OV certificates now build reputation the same way.
EV can still matter for other reasons: stricter identity validation that some enterprise customers ask for, and the Windows hardware (driver) programme, which requires an EV certificate to register. But if you are choosing between OV and EV only for SmartScreen, OV is now equivalent.
First, rule out a broken or missing signature
Before blaming reputation, confirm that the file users download is actually signed and timestamped. Common mistakes:
- The inner EXE is signed, but the installer (setup.exe, MSI, or the bootstrapper) is not, or vice versa.
- A post-build step (packer, resource editor, installer compiler, "strip" step) modified the file after signing, which breaks the signature.
- The file was signed without a timestamp and the certificate has since expired.
- The download is a ZIP, and users run an unsigned file from inside it.
Check on a clean machine with the downloaded file, not your build output:
signtool verify /pa /v setup.exe
Get-AuthenticodeSignature .\setup.exe | Format-List Status, StatusMessage, SignerCertificate, TimeStamperCertificate
Status should be Valid and TimeStamperCertificate should not be empty. In Explorer, right-click the file, choose Properties > Digital Signatures, and check that the signature is there and "This digital signature is OK".
How to reduce the warning in practice
1. Sign every file, every release, with the same certificate
Reputation attaches to the publisher certificate as well as to each file hash. Microsoft notes that changing the signing certificate affects the publisher trust signal, so a new certificate can mean starting again. Sign all executables you ship (installer, main EXE, helper EXEs, DLLs) with one certificate. When you renew, renew early and keep the same organisation identity; expect some warnings again after the switch. Since 1 March 2026, publicly trusted code-signing certificates are issued for at most 460 days, so a new certificate (and this reset) comes round more often than with the old multi-year certificates.
2. Release fewer, larger builds to the public
Every new build has a new hash with zero file reputation. Publishing a nightly build to your public download page spreads users over many hashes and none of them accumulate reputation. Keep a stable public release and put frequent builds on a separate channel.
3. Expect weeks, not days
Microsoft gives no threshold. Its guidance is that it can take several weeks and hundreds of clean installs from a wide audience. Plan a launch with that in mind and tell early users what they will see: the publisher name in the dialog is your verification, and "More info > Run anyway" is safe when that name is yours.
4. Do not get flagged as unwanted software
A certificate can also build negative reputation. Bundled offers, aggressive installers, obfuscation that looks like malware, or signing a third-party tool that antivirus engines flag can all damage your certificate's standing. If a file is wrongly detected by Microsoft Defender, report it as a false positive through the Microsoft Security Intelligence file submission portal (microsoft.com/wdsi/filesubmission). Microsoft also notes that enterprise IT administrators can submit files there for review to speed up trust for internal or managed deployments.
5. Consider the distribution channel
- Microsoft Store: Store apps are re-signed by Microsoft and do not get the SmartScreen download warning. If your app fits the Store, this is the most reliable route.
- Enterprise deployment tools (Intune, Configuration Manager): files installed this way do not go through a browser download, so users typically do not see the download prompt. Your files still need to be signed, and enterprise policy may apply its own checks.
- Direct download: serve over HTTPS from a stable domain and avoid URL shorteners and file lockers.
6. Watch for Smart App Control on Windows 11
On Windows 11 devices with Smart App Control turned on, unsigned files are blocked unless they have a positive reputation, and the check applies to all executables, not only downloads. Signing every binary matters even more there.
What does not help
- Re-signing the same file with a more expensive certificate.
- Asking Microsoft to "whitelist" a consumer download: for consumer endpoints there is no submission process for reputation; it builds from usage.
- Changing file names. Reputation follows the hash and the certificate, not the name.
- Telling users to turn SmartScreen off.
The hardware-key side of the story
Since June 2023, CA/Browser Forum rules require that the private keys of publicly trusted code-signing certificates (OV and EV) be generated and stored on hardware: a USB token, an HSM, or a cloud signing service. That makes "sign every file, every release, with the same certificate" harder in practice, because the token sits on one desk while builds run elsewhere. Teams often end up signing only the installer by hand, which leaves inner binaries unsigned. The fix is to make signing part of the build so it cannot be skipped.
How OneSigner handles it
OneSigner does not change how SmartScreen scores your files; reputation still has to build. What it removes is the reason teams skip signing: the code-signing token stays plugged into one Windows machine running OneSigner, the PIN is kept in the service configuration file there (restrict it to SYSTEM and administrators) and entered automatically, and any build runner signs every EXE, DLL and MSI over HTTPS with OneSignTool or AzureSignTool, timestamped, with the same certificate every time. Only the file hash travels to the signing machine. See code signing in CI/CD and the OneSignTool CLI guide.



