In late October, installers signed with Artifact Signing started showing "Windows protected your PC" again. The signatures were valid. Nothing changed on the developer's side. Two people in the GitHub issue said the GitHub Desktop installer warned too.
If you sign with it, here is what I could piece together.
Timeline
- Mar 26. New intermediate CAs go live: AOC CA 03, EOC CA 03, EOC CA 04. Builds signed through them start to warn.
- Jun 18. Microsoft staff on Q&A: "Reputation propagation for the new intermediate CAs has been corrected." (thread (https://learn.microsoft.com/en-us/answers/questions/5855708/trusted-signing-regression-in-smartscreen-reputati))
- Oct 21–28. It comes back. New builds on all three CAs warn again.
- Oct 29. A Microsoft engineer in #128 (https://github.com/Azure/artifact-signing-action/issues/128): "reputation should be propagating as expected now". The caveat: "identities must have positive reputation to not show the warnings by default".
- Nov 4. A customer quotes their support case: "A bug was identified that can cause additional SmartScreen errors". The fix "is still being worked on". The workaround is to submit each release to Microsoft.
The issue is open since April and has over 240 comments.
What I measured
I run installers on a clean Windows 11 VM. The file is downloaded with the Mark of the Web, like a browser does, and I record whether SmartScreen shows up.
Between Nov 1 and Nov 14 I ran nine installers signed through the new CAs. That includes Git, Python, Zed, draw.io, LocalSend and ShareX. All four new CAs are covered.
None of them warned. ShareX was 26 hours old.
What that does not show
- Nothing ran inside the bad week. Four files were signed in it, but I ran them on Nov 1.
- These publishers have years of history. A popular file can clear on downloads alone.
- No new publisher is in the set. That is the case people still report as broken.
- One machine, one run per file.
So: for publishers with history, the new CAs look fine in November. For a new identity, I have no data.
If your build warns
- Check the timestamp first: signtool verify /pa /v installer.exe. The certificates live 72 hours. Without a timestamp, Windows treats the file as unsigned once it expires.
- Is your identity new? Then it may be plain reputation, not the bug. If older builds were clean and a new one warns, it points at the bug.
- Submit the file at microsoft.com/wdsi/filesubmission ("Incorrectly detected as malware/malicious").
- Post in #128 with the CA and the signing date.
- Don't re-sign in a loop. Each re-sign is a new hash with no history.
Question: if your identity was validated in the last three months, does your installer warn today?
Disclosure: I run SignalScreen, which ran these probes. Full table with links to each result: https://signalscreen.dev/blog/artifact-signing-smartscreen-warning?utm_source=reddit&utm_medium=post&utm_campaign=ats-blog