Microsoft's https://aka.ms/secure-boot-version-violation SVN Security Violation URL is still not operational
@SochiOgbuanya is already working on this.
Since Dec 12, 2025.
Assessment
This issue has not been assessed yet.
Description
Not sure if this is the best place to report this problem, but considering that this is related to Secure Boot revocation and that this repository is maintained by Microsoft, I hope you can redirect this to the relevant people.
More than 1 year ago, Microsoft introduced SVN as a revocation mechanism in their Windows UEFI bootloaders, that, similar to the Linux Shim's SBAT, allows bulk validation and revocation of bootloaders, without having to add individual UEFI bootloader hashes to the DBX.
When such a revocation occurs, the end-user is faced with a message similar to this one:
The problem is that, after at least more than a year since this message has been part of Microsoft's UEFI bootloaders, the https://aka.ms/secure-boot-version-violation URL, that is referenced in the error screen, does not link to anything.
Considering that end-users very much can and do run in this error screen already (another recent example here), it is very problematic that the URL provided is invalid, as it makes a problem significantly worse.
We therefore ask that the Microsoft team in charge of Windows bootmgr (which is where this message comes from) takes care of making sure that the URL they included does resolve to a working page that explains to end users what Microsoft's SVN validation does, what conditions can lead to the error screen, and what kind of remediation users can bring, to avoid the error.
Thank you.
- Dominant language
- Python
- Stars
- 289
- Forks
- 89
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/secureboot_objects
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/secureboot_objects#471 ·
-
state:needs-owner state:needs-triage type:bug urgency:high
Difficulty 4/5 3-5 days Newbie friendliness 55/100
microsoft/secureboot_objects#467 · 3 comments ·
-
state:needs-triage type:feature-request urgency:low
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/secureboot_objects#466 ·
-
state:needs-triage type:feature-request urgency:low
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/secureboot_objects#462 · 3 comments ·
-
state:needs-owner state:needs-triage type:bug urgency:low
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/secureboot_objects#424 · 6 comments ·
All issues in microsoft/secureboot_objects
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·