Microsoft confirms its new Edge browser won't support Silverlight
Microsoft has already announced that its new Microsoft Edge web browser in Windows 10 will not be using many of the features that were a part of its old Internet Explorer browsers. That includes support for ActiveX-based plug-ins.
Context & Ripple Effects
This confirmation closes out a decision Microsoft had been telegraphing since spring: the May coverage detailed Edge dropping VML, VB Script, toolbars, BHOs and ActiveX entirely as a security posture, while Ars Technica's preview framed asm.js performance as the replacement path for what plug-ins used to do.
It also fits the two-engine split from March, when Microsoft said Spartan would carry the new Edge rendering engine while IE 11 keeps Trident in Windows 10 — meaning the Silverlight cutoff only works because a legacy fallback browser ships alongside it.
First-order effects
- Enterprises running line-of-business apps built on Silverlight or ActiveX controls lose their default-browser path on Windows 10 and must route those users to IE 11 instead.
- Microsoft formally strands its own plug-in platform: Silverlight content has no forward home in Edge, and the extension story shifts to whatever model Edge ultimately adopts rather than BHOs.
Second-order effects
- Developers of intranet and media-delivery apps face forced rewrites against open web standards, since IE 11 is explicitly a compatibility stopgap rather than a development target under the Trident/Edge split.
- Rival browsers gain nothing they must counter — they had already abandoned plug-in architectures — but Microsoft removing its last differentiator narrows Edge's pitch to performance and integration alone.
Third-order effects
- A clean-slate engine unburdened by legacy compatibility was the bet here; when that proved insufficient, Microsoft moved to a Chromium-based Edge — the arc suggests even a security-first rebuild couldn't sustain a third rendering engine against web-compatibility gravity.
- If the pattern holds, browser vendors converge on shared engines with differentiation moving to UI and services layers — visible later in Edge's own churn, like the scrapped rounded-tab redesign confirmed in 2024.
The trend: Browser platforms are retiring proprietary plug-in ecosystems in favor of standards-based rendering, with legacy engines kept only as managed compatibility fallbacks until even that becomes untenable.