EV code signing certificate

An EV code signing certificate used to be the way to get a Windows app past SmartScreen on day one. That stopped in 2024. Here's what an EV certificate is, what it still does, what it costs, and what most developers should buy instead.

A padlock with a small key resting beside it

An EV (extended validation) code signing certificate is a certificate for signing software that a certificate authority issues only after a deeper check of your company. You use it the same way as any other code signing certificate: to sign your .exe, .msi or driver so Windows can show who published it and confirm it hasn't been changed.

For years, developers paid extra for EV for one reason: an EV-signed installer skipped the Microsoft Defender SmartScreen warning from the very first download. That's no longer true. Microsoft's documentation says the behavior "was removed in 2024", and that EV-signed files "now go through the same reputation-building process" as files signed with a standard certificate.

So if you're a desktop app developer wondering whether you need one, the short answer is: probably not. The details follow, each checked against the source on November 17, 2026.

EV vs standard code signing certificates

The rules for publicly trusted code signing certificates are set by the CA/Browser Forum, in its Code Signing Baseline Requirements. They define two kinds: EV and non-EV. Certificate authorities sell the non-EV kind as "standard", "OV" (organization validation), or "IV" (individual validation) when it's issued to a person.

Standard (OV or IV) EV
Who can get one Companies and individuals Registered organizations only
What's verified Legal identity, address, and that the requester is authorized The same, plus the company's physical and operational existence and the people signing the request
Private key storage Certified hardware required Certified hardware required
Signature Authenticode, same algorithms Authenticode, same algorithms
SmartScreen Reputation builds over time The same since 2024
Windows hardware program Not accepted for registration Required for registration
Typical price Lower Higher

The signature itself is no stronger with EV. The difference is how thoroughly the certificate authority checked who you are before issuing it.

What changed, and why EV matters less now

Three things used to set EV apart. Two of them are gone.

1. Instant SmartScreen reputation: removed in 2024. Microsoft's SmartScreen documentation is blunt: "EV certificates no longer bypass SmartScreen." Every signed file now earns reputation the same way, through downloads and clean installs over time. Microsoft says there's no exact threshold, and that it can take several weeks and hundreds of clean installs.

2. Hardware key storage: now required for everyone. EV certificates always had to keep their private key on a hardware token. Since June 1, 2023, the Baseline Requirements say the same for every code signing certificate: the key must be protected in hardware certified to at least FIPS 140-2 Level 2 or Common Criteria EAL 4+. You can't download a standard certificate as a .pfx file any more either.

3. Stricter vetting: still there. An EV certificate still tells an enterprise buyer that a certificate authority confirmed your company exists and operates. Microsoft's wording is that EV "may matter for enterprise procurement".

Microsoft's own conclusion, from its guide to code signing options: paying the EV premium "solely to avoid SmartScreen warnings is no longer justified".

What you still need an EV certificate for

The Windows Hardware Developer Program. If you ship kernel-mode drivers, you need one. Since Windows 10 version 1607, Windows won't load new kernel-mode drivers unless Microsoft has signed them through the Hardware Dev Center, and to register for that program Microsoft says "you must have an extended validation (EV) code signing certificate". The certificate is tied to your account; Microsoft's signature is what goes on the driver.

Customers who ask for it. Some enterprise and government buyers have procurement checklists that say "EV". If a deal depends on it, that's a reason.

If neither applies and you already have an EV certificate, keep using it until it expires. It's still valid for signing. You just don't need to pay for another.

What an EV certificate costs

Prices vary a lot between certificate authorities. These are list prices from their own websites, read on November 17, 2026:

Certificate authority Standard, 1 year EV, 1 year
SSL.com $129 $349
DigiCert $696 $972

Microsoft's guide gives a broader range for the market: $150 to $300 a year for a standard certificate and $400 or more for EV. Resellers often sell the same certificates for less than the authority's list price.

Budget for where the key lives, too. A hardware token or a cloud signing subscription is often a separate line: SSL.com, for example, lists a FIPS YubiKey at $379 and its eSigner cloud signing from $15 a month.

And certificates don't last as long as they used to. For certificates issued on or after March 1, 2026, the Baseline Requirements cap validity at 460 days, down from 39 months. Multi-year certificates are gone, so plan to renew, and to be validated again, about once a year.

Signing with a hardware-held key, including in CI

Because the key can't leave certified hardware, you have three ways to hold it:

  • A USB token that the certificate authority ships to you. It works well on a desk. It doesn't work on a hosted CI runner, because there's nothing to plug it into.
  • Your own hardware security module, or a cloud key vault that meets the standard.
  • The certificate authority's cloud signing service, such as DigiCert KeyLocker or SSL.com eSigner. The key stays in their hardware and your build calls the service to sign. This is the option that works with GitHub Actions and other hosted runners.

Whichever you use, the signing command is still SignTool:

signtool sign /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /a MyApp.exe

/a picks the best certificate available, which with a token plugged in is the one on the token. Always include the timestamp (/tr and /td): it's what keeps your signature valid after the certificate expires, and with certificates now capped at 460 days that matters more than it used to.

What to use instead

For most desktop apps sold outside the Microsoft Store, there are two better choices than EV.

Azure Trusted Signing (now called Artifact Signing). Microsoft's own signing service costs $9.99 a month, needs no hardware, and is built for CI. Microsoft recommends it for apps distributed outside the Store. The limit is eligibility: organizations in a list of countries that includes the US, Canada, the EU and the UK, and individual developers only in the US and Canada.

A standard (OV or IV) certificate from a certificate authority. Available worldwide, to companies and individuals. Microsoft describes it as functionally equivalent to Artifact Signing for SmartScreen purposes.

Azure Trusted Signing Standard certificate EV certificate
Cost $9.99 a month From about $130 a year From about $350 a year
Available to individuals US and Canada only Yes No
Available worldwide No Yes Yes
Hardware needed None Token, HSM or cloud signing Token, HSM or cloud signing
SmartScreen Builds over time Builds over time Builds over time
Windows hardware program No No Yes

Whichever you pick, the way to get past SmartScreen is the same: sign every release with the same publisher identity, so the reputation your earlier versions earned carries over to the next one. Switching certificates or publisher names starts you again from zero.

Once the installer is trusted

Signing gets your app installed. If you sell it yourself, you also need each copy to know it's paid for and to receive updates. LicenseSeat handles license keys, device activation and update delivery for apps sold from your own site. It charges a flat monthly fee and takes 0% of your revenue. The guide on how to sell software online walks through the rest.

Common questions about EV code signing certificates

What is an EV code signing certificate?

It's a code signing certificate issued under the CA/Browser Forum's extended validation rules, which require the certificate authority to verify a company's legal, physical and operational existence. It signs software exactly like a standard certificate.

Does an EV certificate remove the SmartScreen warning?

Not any more. Microsoft removed the instant SmartScreen bypass for EV certificates in 2024. EV-signed files now build reputation over time, the same as files signed with a standard certificate.

What is the difference between OV and EV code signing?

The depth of the identity check, and the price. OV verifies the organization's legal identity and address. EV adds checks of its physical and operational existence. Both now need hardware key storage and both get the same SmartScreen treatment.

Can an individual get an EV code signing certificate?

No. Extended validation is for registered organizations. Individuals can get a standard certificate, which some authorities call individual validation, or use Azure Trusted Signing if they're in the US or Canada.

How long is an EV code signing certificate valid?

At most 460 days if it was issued on or after March 1, 2026. Before that, the maximum was 39 months. Signatures you timestamp stay valid after the certificate expires.

Do I need an EV certificate to sign Windows drivers?

You need one to register for the Windows Hardware Developer Program, which is how kernel-mode drivers get signed by Microsoft. You don't need one for ordinary applications and installers.

How much does an EV code signing certificate cost?

List prices on November 17, 2026 ranged from $349 a year at SSL.com to $972 a year at DigiCert, before the cost of a hardware token or cloud signing. Microsoft's documentation puts the market at $400 or more a year.

Can I use an EV certificate in GitHub Actions?

Yes, but not with a USB token. Use your certificate authority's cloud signing service, which keeps the key in their hardware and lets the runner request signatures.