Why is Windows SmartScreen blocking so many installations? According to AI, SmartScreen uses various signals:
File reputation (the big one)
SmartScreen maintains a reputation score for that exact file hash:
- How many people have downloaded it
- How many have run it
- Whether users aborted or overrode warnings
- Whether it’s been reported as malicious
A brand-new binary has zero reputation, so it gets flagged even if it’s harmless.
Publisher reputation (certificate reputation)
This is where code signing comes in — but with a catch.
- A standard code-signing certificate starts with no reputation
- Reputation is built over time as many users run binaries signed with that cert
- Until then, SmartScreen still shows “Windows protected your PC”
So signing helps, but it does not give instant trust, unless an (expensive) Extended Validation) code-signing certificate is used. Using a self-signed certificate as "Trusted Root" may even have a worse rating as consequence.
We finally bought a code-signing certificate from the reputable source Certum, since they have a special deal for open source developers. Their CA is present on every Windows installation, see here in the Certificate Manager:

So expect a further announcement when our binaries are signed with the new certificate. Over time, the reputation in SmartScreen will also improve.
This article was partly created with the help of AI, however, manual adjustments were made where needed.












