What SmartScreen does, as Microsoft documents it
Microsoft Defender SmartScreen checks files that users download before it lets them run. Microsoft’s page for app developers says it weighs two signals:
- Publisher reputation: is the file signed, and is the signing certificate from a known, trusted publisher?
- File hash reputation: has this exact file been downloaded by users without signs of malicious behavior?
A new binary can show a warning even when it is signed, until its hash or its publisher certificate has gathered enough positive history. Unsigned files start from zero with every version. Signed files can inherit reputation across versions if they are signed with the same publisher identity.
| What you ship | First-download behavior (per Microsoft) |
|---|---|
| Microsoft Store app | No warning. Microsoft re-signs it |
| Signed with a valid OV or EV certificate | Warning until reputation builds. The publisher name is shown |
| Signed with Artifact Signing | Same as other valid certificates; reputation builds over time |
| No signature | “Windows protected your PC”. The user must choose Run anyway. Enterprise policy can block it entirely |
| Self-signed certificate | Same as no signature |
Three more facts from the same page shape your plan:
- EV no longer bypasses SmartScreen. “Paying a premium for EV solely to avoid SmartScreen warnings is no longer justified.”
- There is no exact threshold. The warning stops once the file hash has enough download history, which Microsoft says “can take several weeks and hundreds of clean installs from a wide audience”.
- For consumer machines there is no way to submit a file for a reputation review. Enterprise administrators can submit files through the Microsoft Security Intelligence portal.
On Windows 11, Smart App Control can supersede SmartScreen reputation checks and blocks unsigned files that lack a positive reputation. If you tell early customers to expect a prompt, as Microsoft suggests, say it plainly in the download page and in the order email.
Your signing options
| Option | What you get | What it costs and requires |
|---|---|---|
| Microsoft Store | No SmartScreen warning; Microsoft’s certificate | Packaging for the Store. Microsoft says its new onboarding flow charges no registration fee. Check Microsoft’s current Store terms for revenue rules |
| Artifact Signing (formerly Trusted Signing) | Microsoft’s recommended service for signing outside the Store. No hardware token; works from CI | From $9.99 a month. Identity validation. Basic and Premium accounts, with Basic quota listed at 5,000 signatures a month |
| OV or EV certificate from a certificate authority | A certificate bound to your verified identity | Private key in a hardware module, certificate renewals, a CA fee |
| Unsigned or self-signed | Nothing | Warnings on every new version |
Artifact Signing: who can use it
Microsoft renamed Trusted Signing to Artifact Signing. The Learn quickstart says public-trust certificates are available to organizations in the United States, Canada, the European Union, the United Kingdom, Australia, New Zealand, Japan, South Korea, Singapore, Switzerland, Norway and Israel, and that individual developers must be located in the United States or Canada. Identity validation happens only in the Azure portal. If you are an individual outside those two countries, this route is closed, and a CA certificate or the Store is next.
Certificates from a CA: what changed
The CA/Browser Forum’s Code Signing Baseline Requirements changed two things you will notice when you buy or renew:
- Hardware key storage. Since June 1, 2023, the CA must ensure the subscriber’s private key is generated, stored and used in a suitable hardware crypto module. In practice that means a USB token or a cloud HSM service. You cannot download a certificate file and drop it onto a build server.
- Shorter validity. Ballot CSC-31 cut the maximum validity from 39 months to 460 days for certificates issued on or after March 1, 2026. Plan an annual renewal, and automate it.
Timestamp every signature. Artifact Signing certificates have a three-day validity, and Microsoft’s documentation says time stamping is critical for a signature to keep validating after that. SignTool needs both a file digest and a timestamp digest. Without /fd it errors, and without /td a timestamped signing errors too:
signtool sign /v /fd SHA256 /tr "http://timestamp.acs.microsoft.com" /td SHA256 ^
/dlib "<path>\Azure.CodeSigning.Dlib.dll" /dmdf "<path>\metadata.json" ^
YourApp-Setup.exe
That is the Artifact Signing form from Microsoft’s documentation. With a CA certificate you pass your certificate by hash instead (/sha1) and a timestamp URL from your CA.
Which option fits which seller
| Your situation | Likely fit | Why |
|---|---|---|
| Individual developer in the United States or Canada | Artifact Signing, individual validation | The only individual route Microsoft lists, no hardware token |
| Registered company in a supported country, including Switzerland and EU states | Artifact Signing, organization validation | Lowest recurring cost, works from CI |
| Individual developer in another country | CA certificate with a hardware key, or the Store | Artifact Signing does not offer public-trust certificates to individuals there |
| Business customers whose IT department asks for EV | EV certificate from a CA | Microsoft says EV may matter for procurement, though not for SmartScreen |
| You want no first-download warning and can package for the Store | Microsoft Store | Store apps never show SmartScreen download warnings, per Microsoft |
| Free hobby tool, no budget | Unsigned | Expect warnings on every new version |
Installers
Pick one installer format and sign the installer and the executables inside it. Microsoft’s guidance is to sign every release and not to modify files after signing.
- MSIX is Microsoft’s modern package format. Microsoft’s page says it gives clean install and uninstall and automatic updates, and that all MSIX packages must be signed before installation. It is also the route to the Store.
- MSI is the Windows Installer format. WiX is an open-source toolset that builds MSI packages from XML files.
- Inno Setup is an open-source installation builder for Windows applications, in development since 1997 according to its own site.
Whichever you pick, keep the publisher name the same across releases. Microsoft lists “use a consistent signing identity” because changing the certificate resets the publisher signal.
A checklist for the first release
- Choose signing: Artifact Signing if you are eligible, otherwise a CA certificate with a hardware key, or the Store.
- Sign every executable and the installer, with timestamps.
- Verify with SignTool’s
verifycommand on a clean machine. - Download your own build through a browser on a fresh Windows machine and note what SmartScreen shows.
- Tell early customers what to expect.
- Keep the same signing identity for every later release.
Payments, license keys and updates
Windows software sells like any other direct download: Stripe takes the payment, something issues a license key, the installer lands on the buyer’s machine, and the app checks the key. The payment side is in how to sell software online with Stripe, and download delivery in delivering software downloads after payment.
With Clavem, give each release file the platform label windows and publish it. Your app then asks for the newest version at launch:
curl "https://clavem.io/v1/releases/PRODUCT_ID/latest?platform=windows" \
-H "X-License-Key: YOUR-LICENSE-KEY"
The demo product has no published release, so the live API answers with this today:
{"error":{"code":"not_found","message":"This product has no published release yet."}}
With a release published and a valid key, the answer carries version, notes and a files array. Each file has a signed url valid for one hour, so request the link when the customer clicks Download, not when your app checks. A key that is missing or invalid is not an error: the response still tells the app that a new version exists, without the files. See Releases and downloads. Windows licensing code is the same as on any platform: activate once, validate at launch, verify the Ed25519 token offline when the network is down (offline verification).
Doing this with Clavem
Clavem handles keys, device limits, downloads and update checks for software sold through Stripe. It does not sign your builds or provide a certificate. Signing happens in your build pipeline, and the signed installer is what you upload. Clavem is not a merchant of record, so VAT and sales tax stay with you or with Stripe Managed Payments; tax basics explains the choice. The free plan covers 50 active licenses, which is enough to test the whole flow with a signed installer.
Questions
Does an EV code signing certificate remove the SmartScreen warning?
Not according to Microsoft. Its SmartScreen reputation page says EV certificates no longer bypass SmartScreen and that paying a premium for EV solely to avoid warnings is no longer justified. EV may still matter for enterprise procurement.
How long until SmartScreen stops warning about a new app?
Microsoft gives no exact threshold. Its page says reputation builds from download volume and that it can take several weeks and hundreds of clean installs from a wide audience. There is no mechanism to submit a file for review for consumer machines.
Can I sign with a self-signed certificate?
You can, but Microsoft says a self-signed certificate behaves like no signature. The user sees Windows protected your PC and must choose Run anyway.
Do I have to sign if I only sell to a few customers?
Unsigned files must build SmartScreen reputation again with every new version, and Windows 11 Smart App Control can block unsigned files that lack a positive reputation. Signing every release is Microsoft's own advice.
Sources
- Microsoft Learn, SmartScreen reputation for Windows app developers (as of November 2026)
- Microsoft Learn, Artifact Signing quickstart, regions and eligibility (as of November 2026)
- Microsoft Learn, Artifact Signing overview (as of November 2026)
- Microsoft Learn, Artifact Signing with SignTool (as of November 2026)
- Microsoft Learn, SignTool reference (as of November 2026)
- CA/Browser Forum, Code Signing Baseline Requirements (as of November 2026)
- CA/Browser Forum, Ballot CSC-31 maximum validity reduction (as of November 2026)
- Microsoft Learn, What is MSIX (as of November 2026)
- WiX Toolset (as of November 2026)
- Inno Setup (as of November 2026)
- Microsoft Learn, Open a developer account for the Microsoft Store (as of November 2026)