Internet Explorer retired, but Edge still runs its engine through at least 2029
Legacy business applications can depend on controls that a modern browser never promised to run, leaving IT with a migration list to finish.
Internet Explorer left the desktop and kept a room inside Edge. The retirement party apparently came with a forwarding address.
Microsoft’s IE mode documentation describes two rendering engines inside one browser. Modern sites use Chromium. Legacy sites configured for IE mode use “Trident MSHTML,” the engine from Internet Explorer 11. A newer frame around an older engine can preserve a business application whose replacement is still somewhere in the budget spreadsheet.
The distinction matters when an internal site depends on an old document mode or an ActiveX control. Microsoft’s supported-functionality list includes ActiveX, Browser Helper Objects and settings for IE security zones. A site that simply looks old doesn’t automatically need this machinery. The actual dependency decides whether compatibility mode belongs in the migration plan.
An IE indicator appears beside the address when a page uses the older engine. Administrators can control which sites get that treatment through the Enterprise Mode Site List. Ordinary websites stay on the modern rendering path. That makes a carefully maintained list far easier to defend than telling everyone to use the old engine whenever an application has a bad day.
Microsoft’s lifecycle FAQ says the IE11 desktop application ended support on certain operating systems on June 15, 2022. The qualifier matters: the browser’s history spans multiple Windows products with their own lifecycles. IE mode’s commitment is separately described as support through “at least 2029,” with a year of notice before retirement.
That wording gives administrators a minimum commitment, rather than a scheduled shutdown at midnight on December 31, 2029. It also supplies no permission to freeze the underlying operating system. A support promise that depends on a supported OS still needs the OS part. Fine print has entered the chat (wearing reading glasses).
The Silverlight example makes the catch concrete. Rendering a page successfully says very little about whether each component on that page still receives fixes. The application owner needs the full dependency list, including controls, authentication behavior and any separate software the workflow launches.
An inventory can turn this from browser archaeology into a retirement project. For each listed site, a named owner can record what breaks outside IE mode, what business process depends on it and what would replace it. A site that passes its real workflow in modern Edge can leave the list. A site that fails can point to a specific migration problem, rather than another calendar reminder called Modernize Everything.
The remaining list still needs owners.