Internet Explorer is Microsoft’s retired Windows web browser and the origin of a compatibility engine that many older business sites still expect. The standalone desktop browser no longer functions as a supported general browser on affected Windows releases. On those systems, opening Internet Explorer normally redirects to Microsoft Edge. Organizations with an internal site that depends on old document modes, ActiveX, or Internet Explorer-specific behavior now use Internet Explorer mode inside Edge instead of returning to the retired desktop application.
The desktop app ended
Internet Explorer reached its final major release and left support on many Windows editions. Microsoft later disabled the desktop application through an Edge update on affected Windows 10 systems. Windows 11 never shipped it as a normal standalone browser. A download cannot restore supported daily browsing where the operating system has removed that route.
The old engine has not disappeared from every Windows component. MSHTML remains for compatibility, and Edge can call it inside a managed IE mode tab. This distinction explains why an Internet Explorer shortcut may open Edge while an older line-of-business site still renders with legacy behavior.
IE mode replaces it
Internet Explorer mode runs selected sites inside Microsoft Edge. An administrator normally places those addresses in an Enterprise Mode Site List and chooses the compatibility behavior. Users keep the Edge window, address bar, and security servicing while the tab uses legacy rendering for the designated page.
IE mode is not a switch for making the entire web behave like Internet Explorer. A broad rule can trap modern login pages inside an old document mode or carry the wrong cookies through a workflow. Microsoft recommends mapping the legacy site and leaving neutral authentication or redirection domains outside the engine when that flow requires Edge.
Document mode choices
Old sites can depend on IE11 behavior, IE8 Enterprise behavior, IE7 Enterprise behavior, or quirks logic. The most modern compatible choice leaves more room for the page’s own directives. Forcing an older mode everywhere can move page elements, hide controls, or stop a button from responding.
Authentication often crosses several addresses. An incomplete neutral-site list can let the first page open correctly and then break sign-in on another domain. The troubleshooting process records the whole navigation path and checks which address changed engines. Fixing only the visible starting URL may leave the failure untouched.
Controls and automation
Internet Explorer once exposed browser automation through its own application object. Edge IE mode does not reproduce that automation interface. A script that creates an Internet Explorer window must move to a supported browser automation route even if the page itself renders correctly in IE mode.
ActiveX and other legacy components create another boundary. Some controls can run only under the required enterprise configuration, and some page sections may still fail inside IE mode. Applications built around the Windows WebBrowser control follow a separate compatibility path. A successful page test does not prove that its external automation or desktop integration survived the migration.
Security and support
Internet Explorer no longer receives browser support as an ordinary desktop app on retired editions. Installing an old package or copying its executable does not create a safe current browser. Modern websites have also removed workarounds for its rendering engine, so TLS connections, sign-in pages, and scripts can fail before the page reaches its content.
Microsoft maintains IE mode according to the lifecycle of supported Windows releases and Edge policy. That route exists for a controlled list of legacy business dependencies. General browsing belongs in a maintained browser, while an organization should inventory each IE mode site and remove it from the list after its application no longer needs the old engine.
