Internet Explorer is dead, and Microsoft meant it.
On June 15, 2022 Microsoft retired Internet Explorer 11 and pushed an update that permanently disabled the desktop app.
Microsoft now redirects IE into Microsoft Edge and uses Edge’s IE mode to run old sites.
This matters for everyday users (favorites and passwords get imported) and for IT teams running legacy intranet apps.
This post explains what changed, who’s affected, why Microsoft retired IE, and the practical next steps to keep sites working.
Understanding What Happened to Internet Explorer
Microsoft pulled the plug on Internet Explorer 11 and yanked support on June 15, 2022. The desktop app got permanently disabled through a browser update pushed to certain Windows 10 versions. That was it. More than 25 years of Internet Explorer as a standalone product, done.
Microsoft swapped in Microsoft Edge, a faster browser built on a modern engine that can still handle old websites. Try to open Internet Explorer after the retirement date and Windows just redirects you to Edge. Edge can run those older sites in a built-in compatibility mode called IE mode.
The retirement hit home users and enterprise IT differently. People at home see their favorites, passwords, and browsing history get imported into Edge without much fuss. Companies stuck with legacy intranet apps can configure IE mode to keep those sites running while moving everything else to the modern browser. The old rendering engine from IE11 (Trident or MSHTML) still gets support for developers who embed browser controls in custom applications. But the standalone Internet Explorer app itself? No more maintenance, no more security patches.
The Internet Explorer Retirement Timeline and Milestones
Internet Explorer showed up in 1995 as an add-on for Windows 95 and quickly became the dominant web browser. By 2003, IE had roughly 95 percent of global browser market share. That shaped how developers built websites for over a decade. Then that dominance started falling apart in the mid-2000s when Firefox and Chrome entered with faster performance, better standards support, and modern features IE couldn’t match.
By 2014, Internet Explorer still had about 59 percent market share while Chrome sat at 21 percent. But within roughly two years Chrome overtook IE and Safari pulled ahead too. Microsoft released the first version of Edge in 2015 as a modern replacement. That signaled the beginning of IE’s long sunset. The formal retirement process kicked off in 2021 and wrapped up mid-2022 with the permanent disabling of the IE11 desktop application.
Key milestones:
- 1995 – Internet Explorer first shipped as an add-on for Windows 95
- 2003 – IE reached approximately 95% global browser market share at its peak
- 2015 – Microsoft released the first version of Edge as a modern alternative
- May 19, 2021 – Microsoft publicly announced the retirement plan for the Internet Explorer 11 desktop application
- August 17, 2021 – Microsoft 365 apps and services ended support for Internet Explorer 11
- June 15, 2022 – Internet Explorer 11 officially retired and reached end-of-life on Windows 10
- July 11, 2022 – Microsoft updated visual demonstrations of the IE mode button to reflect a design change
Why Microsoft Ended Support for Internet Explorer
Internet Explorer became ridiculously difficult and expensive to maintain as web standards evolved. The browser was built on an architecture designed in the 1990s and couldn’t keep pace with modern web technologies like HTML5, CSS3, and contemporary JavaScript frameworks. Each new web standard required workarounds or remained unsupported. That forced developers to write separate code paths for IE while other browsers adopted new features quickly.
Security vulnerabilities presented a growing cost and risk. Internet Explorer’s legacy code base contained outdated components like ActiveX controls, Browser Helper Objects, and VBScript that created attack surfaces modern browsers had abandoned. Patching these vulnerabilities meant maintaining code written decades earlier. Each fix risked breaking enterprise sites that depended on IE specific behaviors. Organizations continuing to use outdated browser technology after end-of-life face approximately 47 percent higher costs when a data breach occurs compared with those using updated tools.
Microsoft needed to consolidate engineering resources on a single modern platform. The company rebuilt Edge on the Chromium engine in 2020, gaining instant compatibility with the majority of the web while reducing the engineering burden of maintaining two separate browser code bases. The decision to retire IE let Microsoft focus security updates, performance improvements, and new features on Edge rather than splitting effort between a legacy product and its replacement.
The primary factors behind the retirement decision:
- Outdated architecture – IE’s 1990s-era design couldn’t support modern web standards without extensive rework
- Security risks – legacy components like ActiveX and VBScript created persistent vulnerabilities
- Lack of standards support – IE lagged years behind Chrome, Firefox, and Safari in adopting HTML5, CSS3, and modern JavaScript APIs
- Market share loss – by 2016 IE had fallen behind both Chrome and Safari in global usage
- Maintenance burden – supporting IE diverted resources from improving Edge and required maintaining decades-old code
How Microsoft Edge Replaced Internet Explorer
Microsoft Edge serves as the official replacement for Internet Explorer. It offers improved speed, security, and modern web standards support while preserving compatibility for legacy websites. Edge runs on the Chromium rendering engine (also used by Chrome) and the Blink layout engine. That delivers faster page loads and broader compatibility with contemporary web applications. For sites that still require Internet Explorer’s older rendering behavior, Edge includes IE mode, which activates the Trident MSHTML engine from IE11 within an Edge tab.
When you try to open Internet Explorer after June 15, 2022, Windows automatically redirects you to Microsoft Edge. The redirection imports favorites, saved passwords, browsing history, and other browser settings from Internet Explorer into Edge during the first launch. Microsoft plans to remove Internet Explorer icons from the taskbar and Start menu in a future Windows update, though no specific date has been announced for that change. The transition happens progressively, giving users time to adjust before the IE icon disappears entirely.
Microsoft committed to supporting IE mode in Edge through at least 2029. That provides a migration window for organizations with legacy intranet applications. IE mode uses the same Trident MSHTML rendering engine that powered IE11, so sites dependent on older web technologies continue to function. Edge checks every 30 days to confirm whether a site should remain in IE mode, prompting users to verify continued need for compatibility rendering. Enterprise IT teams can automate this process using site lists that specify which URLs should always open in IE mode.
| Feature | Behavior | Purpose |
|---|---|---|
| IE mode | Activates Trident MSHTML engine within an Edge tab for specific sites | Maintains compatibility with legacy intranet apps and ActiveX-dependent sites |
| Automatic redirection | Opening Internet Explorer launches Microsoft Edge instead | Seamlessly moves users to the modern browser without manual setup |
| Data import | Favorites, passwords, history, and settings transfer from IE to Edge on first launch | Preserves user data and reduces friction during the transition |
| Chromium engine | Uses Blink layout engine and V8 JavaScript engine for standard web pages | Delivers modern web standards support, performance, and cross-browser compatibility |
Using Legacy Websites After Internet Explorer’s Retirement
IE mode in Microsoft Edge provides the primary path for accessing legacy websites that depend on Internet Explorer specific technologies. The mode runs the Trident MSHTML rendering engine, supporting older web standards, ActiveX controls, and VBScript that modern browsers no longer recognize. You can manually reload any page in IE mode by clicking the “Reload in IE mode” button in the Edge toolbar. Edge will prompt every 30 days to confirm whether continued IE mode use is necessary for that site. That helps organizations track which legacy applications still require compatibility rendering.
Enterprise IT teams can automate IE mode behavior using site lists. Those are XML files that specify which URLs should always open in IE mode. These lists can be stored locally on each device or managed centrally through cloud-based administration tools in Microsoft 365. For applications that can’t be migrated immediately, IE mode provides a bridge while developers modernize code to work with standard web technologies. ActiveX controls and VBScript dependent applications will eventually require full rewrites, since no modern browser outside of IE mode supports these outdated components.
Common techniques for maintaining access to legacy web applications:
- IE mode in Edge – manually or automatically activate Trident rendering for specific sites
- Enterprise site lists – centrally manage which URLs always open in IE mode, reducing user friction
- ActiveX alternatives – replace ActiveX controls with modern equivalents like WebAssembly, JavaScript APIs, or browser extensions
- Polyfills – use JavaScript libraries to provide modern API support in older rendering contexts
- Modernization projects – rewrite legacy apps using HTML5, CSS3, and contemporary JavaScript frameworks
- Cross-browser testing – validate that modernized sites work in Chrome, Firefox, Edge, and Safari
Enterprise and IT Admin Guidance for the IE Shutdown
Organizations with legacy line-of-business applications need a structured migration plan to move users from Internet Explorer to Edge while preserving access to older intranet sites. IT teams should inventory all internal web applications, identify which ones depend on IE specific features like ActiveX or document modes, and prioritize modernization projects for the most critical systems. For applications that can’t be updated immediately, Edge’s IE mode provides compatibility rendering that keeps those sites functional while the organization completes longer term modernization work.
Enterprise exceptions exist for specific Windows editions that continue to receive Internet Explorer support beyond the June 15, 2022 retirement date. Currently in-support Windows 10 Long-Term Servicing Channel (LTSC) releases (including IoT editions) still include Internet Explorer. So do all Windows Server versions, Windows 10 China Government Edition, Windows 8.1, and Windows 7 systems with Extended Security Updates (ESUs). Future versions of these editions won’t ship with Internet Explorer. Organizations running these exceptions should still plan migration paths, since Microsoft will eventually remove IE from all platforms.
The final step in most enterprise migrations involves applying the DisableIE Group Policy setting. That blocks users from launching Internet Explorer and redirects all attempts to Edge. Before enabling this policy, IT teams should complete testing of critical sites in IE mode, train users on the Edge interface, and set up automated site lists to handle legacy applications transparently. Microsoft offers no-cost remediation and compatibility assistance through programs that help organizations test legacy sites and resolve compatibility issues during migration.
Automating IE Mode in Enterprise Environments
Site lists provide the most efficient way to manage IE mode at scale. IT administrators create an XML file listing URLs that require IE mode, then deploy that file through Group Policy or mobile device management (MDM) tools. Edge checks the site list whenever a user navigates to a URL and automatically activates IE mode if the site appears in the list. That eliminates the need for users to manually trigger compatibility rendering.
Organizations can host site lists locally on file shares or store them in the cloud using the Microsoft 365 admin center. Cloud-hosted site lists update automatically across all managed devices, letting IT teams add or remove sites from a central location without redeploying files. The site list supports wildcards and path-specific rules, so administrators can target specific applications within a domain while allowing other pages on the same domain to render in modern mode.
The DisableIE policy serves as the final migration step after site lists are tested and deployed. This policy prevents users from launching Internet Explorer so all web traffic flows through Edge. Combined with automated site lists, the policy creates a seamless transition where legacy sites continue to work in IE mode while everything else benefits from Edge’s modern security, performance, and standards support.
Security, Compliance, and Business Risks After Internet Explorer’s End-of-Life
Continuing to use Internet Explorer after June 15, 2022 exposes organizations to unpatched security vulnerabilities. Microsoft no longer releases security updates for the IE11 desktop application on affected Windows 10 versions. That means newly discovered exploits remain unaddressed. Attackers actively target unsupported software because they know patches will never arrive. That makes outdated browsers a persistent weak point in an organization’s security perimeter.
Regulatory and compliance frameworks increasingly require organizations to maintain supported software versions. Standards like PCI DSS for payment processing, HIPAA for healthcare data, and various industry specific regulations mandate that systems handling sensitive information receive regular security updates. Running Internet Explorer post-retirement can trigger audit findings and compliance violations, particularly if a data breach occurs and investigators determine that an unpatched browser contributed to the incident.
You should uninstall Internet Explorer from devices once browser data has been migrated to Edge or another modern browser. Removing the application reduces attack surface and eliminates the risk that users will accidentally launch an unsupported browser. For legacy sites that require IE specific rendering, Edge’s IE mode provides the same compatibility while receiving ongoing security updates through Edge’s regular update channel. IT teams that can’t immediately modernize all legacy applications should at minimum ensure IE mode is configured correctly and that the standalone IE application is disabled or removed from all production systems.
How to Migrate Bookmarks, Passwords, and Browser Data from Internet Explorer
Microsoft Edge automatically imports favorites, saved passwords, browsing history, and settings from Internet Explorer during the first launch after the retirement date. The import happens when Edge redirects a user who attempted to open Internet Explorer, capturing data before the transition completes. You can review and manage imported data by opening Edge Settings, navigating to Profiles, and selecting the option to view imported information.
For users who want to migrate data to a browser other than Edge (like Chrome, Firefox, or Safari), each browser provides import tools accessible through settings menus. Most browsers can read Internet Explorer’s stored data directly from Windows during the import process. Users who want to preserve a backup of their IE data before migration should export favorites to an HTML file through Internet Explorer’s File menu before the June 15, 2022 retirement date.
Steps to migrate browser data manually:
- Open Internet Explorer and navigate to File > Import and Export to create an HTML backup of favorites
- Export saved passwords using Windows Credential Manager if moving to a non-Microsoft browser
- Launch the destination browser (Edge, Chrome, Firefox, or Safari)
- Access the browser’s settings or preferences menu
- Select the option to import data from another browser and choose Internet Explorer from the list
Developer and Web Modernization Impacts After Internet Explorer’s Retirement
Web developers can stop testing and maintaining compatibility code for Internet Explorer after the retirement date. That eliminates the need for polyfills, vendor prefixes, and workarounds that made IE specific code paths necessary. Modern web standards (HTML5, CSS Grid, Flexbox, ES6+ JavaScript, and contemporary APIs) work consistently across Chrome, Firefox, Edge, and Safari without requiring fallback implementations. Developers who maintained separate stylesheets or JavaScript bundles for IE can remove that code, reducing bundle sizes and simplifying maintenance.
Legacy features like ActiveX controls, VBScript, Browser Helper Objects, and proprietary IE APIs have no direct modern equivalents. Applications that depend on these technologies require full rewrites using standard web components, JavaScript frameworks, or WebAssembly. For embedded browser controls in desktop applications, the MSHTML/Trident engine remains supported on all Windows platforms. That lets existing Windows applications that host browser views continue functioning without immediate changes.
Developers who need to test legacy behavior can use virtual machine images that include older Windows versions and Internet Explorer. Microsoft and third-party services provide VM images for testing, though these should only be used in isolated development environments and never connected to production networks due to the security risks of running unsupported operating systems. For most development work, testing in Edge’s IE mode provides sufficient validation of legacy compatibility while running on a supported platform.
| Legacy Feature | Modern Alternative | Migration Complexity |
|---|---|---|
| ActiveX controls | WebAssembly modules, JavaScript APIs, or browser extensions | High – requires complete rewrite of control logic |
| VBScript | Modern JavaScript (ES6+) | Medium – logic can often be translated but syntax differs significantly |
| Document modes / X-UA-Compatible | Feature detection with progressive enhancement | Low – remove meta tags and conditional comments, test in modern browsers |
| Proprietary CSS filters | Standard CSS filters, transforms, and blend modes | Low – mostly one-to-one replacements with standard syntax |
Final Words
IE was officially retired on June 15, 2022, and Microsoft now redirects IE to Edge with IE mode for legacy sites.
That affects everyday users, IT teams, and developers: favorites and passwords move into Edge, enterprises should use site lists or policies to manage compatibility, and developers need to modernize old code.
If you’re still wondering what happened to internet explorer, Microsoft ended support and moved users to Edge while keeping legacy access. It’s a change that makes browsing safer and easier going forward.
FAQ
Q: Why did Internet Explorer fail?
A: Internet Explorer failed because its outdated engine missed modern web standards, was slower and less secure, and became costly to maintain, allowing Chrome, Firefox, and Safari to capture users and developer support.
Q: Does Internet Explorer exist anymore? What replaces Internet Explorer?
A: Internet Explorer no longer exists as a supported browser: Microsoft retired IE on June 15, 2022 and now redirects users to Microsoft Edge, which provides an IE mode for legacy sites.
Q: What is actually the best browser to use?
A: The best browser depends on needs: for general speed and compatibility use Edge or Chrome, for stronger privacy choose Firefox, Mac users use Safari, and enterprises pick Edge for IE‑mode compatibility.
