Reported November 16, 2026. Microsoft began removing default trust for the remaining 10 eMudhra root certificates in its products and services on November 16, according to reporting by IT之家 citing the Microsoft Security Response Center. Certificate chains that rely on those roots may fail validation, potentially disrupting access to affected websites and services or verification of software signatures.
Windows devices that can reach Microsoft’s certificate update service will receive the trust-list change automatically, including Windows devices in Azure environments. Microsoft Edge and WebView2 Runtime are removing default trust through a PKI Metadata component update, without requiring a full browser release. Devices typically check for that update every 10 hours and also check when an application starts.
The change follows a problem involving eight eMudhra intermediate certificate authority private keys that could be calculated because of how they were generated. Six were used for TLS website certificates and two for code-signing certificates. Microsoft warned that someone possessing the keys could issue certificates that appear trustworthy to impersonate websites or software publishers. Microsoft said the issue originated in eMudhra’s certificate system, not a breach of Microsoft’s systems.
Microsoft had already blocked the eight affected intermediate certificates in Windows on October 20, 2026; Edge and WebView2 separately used a CRLSet update to block affected TLS certificates. On October 26, Windows removed seven related certificates from its trusted list—six eMudhra G3 roots and one AAA Certificate Services cross-signed certificate—with Edge following on October 27. Removing the remaining 10 roots is a broader trust decision, not a claim that each root’s private key was compromised.
Microsoft advises operators still using eMudhra certificates to check their certificate chains and replace affected certificates with ones issued by another trusted authority. Earlier out-of-band and November 10 security updates addressed the October removals for Windows devices that cannot connect to Microsoft’s certificate update servers. For the November 16 removal of the remaining roots, Microsoft said it would provide a separate offline certificate update package for administrators to download and deploy. It also cautioned administrators against locally restoring trust without a security assessment.