Microsoft will stop supporting Internet Explorer 8, 9, and 10 on January 12
Owen Williams / The Next Web :
Context & Ripple Effects
This January 12 deadline is the first hard cut in Microsoft's long unwind of Internet Explorer: it ends patches for three of the four surviving IE versions, leaving IE11 as the last engine standing on Windows 7, 8.1, and 10. The move gives enterprise web teams a date certain for dropping legacy-browser testing and pushes the remaining holdouts toward Edge.
Seen against the later coverage, the arc is deliberate — Microsoft first squeezed IE11 out of its own apps with an end-of-support calendar for Teams and Office 365, then forced certain URLs to open in Edge instead of IE, before finally pulling the plug on the browser altogether in the June 2022 retirement that ended 27 years of Internet Explorer. The 2016 cutoff is where that squeeze began.
First-order effects
- Enterprises and government sites still pinned to old intranet apps have a fixed date to migrate off IE8–10 or accept unpatched browsers; IT budgets shift from compatibility maintenance to migration projects starting now.
- Web developers get cover to collapse their testing matrices to a single IE version (IE11) plus modern engines, cutting QA cost immediately.
Second-order effects
- With fewer legacy engines to serve, sites can adopt standards IE8–10 never supported, which in turn makes those browsers render more sites broken — accelerating the exit rather than merely tracking it.
- Edge becomes the designated landing spot for displaced users, giving Microsoft a captive upgrade path inside Windows rather than losing them to Chrome.
Third-order effects
- If the pattern holds, end-of-support deadlines become Microsoft's standard migration lever: the same playbook reappears in the Windows 10 cutoff handled through Extended Security Updates, and in Edge's own Manifest V2 extension deprecation following Chrome — lifecycle management as product strategy.
- For the industry, it points to shorter effective lifespans for old rendering engines and enterprise software built on them, raising the recurring cost of staying current across every layer of the Windows stack.
The trend: Browser and platform vendors are compressing legacy-engine lifespans through dated cutoffs, using end-of-support announcements as the primary mechanism to force migrations to their current platforms.