Internet Explorer Mode in Microsoft Edge: How to Enable, Configure, and Troubleshoot It

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Internet Explorer (IE) mode is a compatibility feature built into the Windows desktop version of Microsoft Edge. Edge uses its Chromium engine for normal websites and the Internet Explorer 11 MSHTML/Trident engine for specifically configured legacy sites. It does not reinstall the retired Internet Explorer desktop application. On a personal or unmanaged Windows PC, add the website to Edge’s IE mode pages list; in an organization, administrators should deploy an Enterprise Mode Site List through Group Policy, Intune, or Microsoft’s cloud management tools.

The short answer

IE mode is intended for websites and line-of-business applications that genuinely depend on Internet Explorer behavior, such as old document modes, ActiveX controls, Browser Helper Objects, or IE-specific authentication and scripting. It is not a general-purpose way to make modern websites look like Internet Explorer, and it should not send every intranet site through the legacy engine.

Internet Explorer 11’s desktop application reached end of support for certain Windows versions on June 15, 2022. Microsoft positions IE mode as the replacement for legacy applications and currently commits to supporting it through at least 2029, with at least one year’s notice before retirement. See Microsoft’s Internet Explorer and Microsoft Edge lifecycle FAQ and IE11 end-of-support announcement.

Version note: Microsoft’s release schedule lists Edge 151 as the Stable-generation line on August 10, 2026, with Edge 152 planned for the week of August 27, 2026. Edge versions and menu labels change frequently, so use edge://version when checking a particular installation. The current personal-device instructions below apply to Edge 141 and later.

Primary reference: What is Internet Explorer mode?

How IE mode works

Modern website       → Microsoft Edge Chromium engine
Legacy IE website   → IE11 MSHTML/Trident engine inside Edge

When a page is running in IE mode, Edge displays an Internet Explorer indicator near the left side of the address bar. The browser remains Microsoft Edge: tabs, profiles, browser controls, updates, and most ordinary browsing features still come from Edge. Only the selected page or site is rendered by the embedded IE11 compatibility engine.

That distinction matters. IE mode:

• does not bring back the standalone Internet Explorer application;
• does not turn all of Edge into Internet Explorer;
• does not reproduce every IE toolbar, navigation menu, browser setting, or extension behavior;
• does not automatically make every old plug-in or local runtime work; and
• does not make IE mode available on macOS, Android, or iOS. Microsoft’s IE-mode policy documentation lists Windows support and marks those platforms unsupported.

Microsoft documents compatibility for IE5 through IE11 document modes where applicable, Enterprise Mode and compatibility modes, ActiveX controls, Browser Helper Objects, relevant IE security-zone and Protected Mode-related settings, and IE developer tools launched through IEChooser. It does not support IE toolbars or IE navigation-menu settings, and ordinary Edge DevTools do not attach directly to the IE-mode document. The complete capability list is in Microsoft’s IE-mode documentation.

When IE mode is appropriate

Good candidate	Usually the wrong solution
An internal line-of-business application that the vendor has not yet modernized	General web browsing
A site that requires an old IE document mode	A modern site that merely has an old-fashioned design
An application that specifically requires ActiveX or a Browser Helper Object	A vendor-supported application that already works in modern Edge
A legacy intranet application with IE-specific scripting, authentication, or form behavior	Replacing a missing Windows desktop application with a browser workaround
A controlled transition while the application is being replaced	A permanent substitute for application modernization

Before adding an exception, test the application in ordinary Edge. A site should use IE mode because of a verified technical dependency, not simply because it is old. For an enterprise deployment, identify the complete workflow—not just the first URL—including login pages, redirects, embedded frames, download locations, authentication endpoints, client-certificate prompts, and any server that opens a new window.

Before you enable IE mode

• Use a supported Windows desktop installation with current Windows updates and an up-to-date Edge build.
• Confirm that the application really needs IE behavior. Ask the vendor whether a modern-browser version is available.
• If the computer is managed by work or school, ask IT before changing Edge settings. A policy or Enterprise Mode Site List may intentionally control the option.
• For ActiveX, document modes, old authentication, client certificates, or security-zone dependencies, test the full application workflow rather than only its home page.
• Plan a migration date. IE mode is a compatibility bridge, not an application roadmap.

Enable IE mode on a personal or unmanaged Windows PC

Current method: Edge 141 and later

Microsoft’s current instructions for a non-enterprise device use a site-specific list rather than a permanent global switch:

1. Open Edge’s Settings.
2. Open Default browser.
3. Under Internet Explorer mode pages, add the affected website. The exact wording can vary slightly by Edge build or locale.
4. Open or reload the site.
5. Look for the Internet Explorer indicator beside the address bar. Its presence confirms that the current page is in IE mode.

You can open the relevant settings page directly with:

edge://settings/defaultBrowser

Microsoft’s current user instructions are in Internet Explorer mode in Microsoft Edge.

Older or alternate user method

On Edge versions or installations that still expose the older control:

1. Go to edge://settings/defaultBrowser.
2. Under Internet Explorer compatibility, set Allow sites to be reloaded in Internet Explorer mode to Allow.
3. Restart Edge.
4. Browse to the affected site.
5. Open Settings and more (…) and choose Reload in Internet Explorer mode.
6. Confirm that the IE indicator appears beside the address bar.

On Edge 92 or earlier, Microsoft placed the command under More tools > Reload in Internet Explorer mode. The option may not appear on a managed computer, may be disabled by policy, or may be unavailable when the organization’s site list controls the site.

How to stay in—or leave—IE mode

Links, scripts, forms, and some server-side redirects within the IE-mode workflow generally remain in IE mode. However, normal browser-control navigation can leave it. Typing a new address in the address bar, using the Back button, or opening a favorite can cause Edge to return to its normal Chromium engine.

To leave IE mode, select Leave on the information bar if it is displayed, or close the IE-mode tab and open a new Edge tab. Always check the indicator before diagnosing a page: one tab or navigation may be in IE mode while another is not. Microsoft describes these navigation rules in its support guidance and local site-list documentation.

Why the IE-mode option may be missing or disabled

On an organization-managed device, the setting may be visible but greyed out. The Reload in Internet Explorer mode command appears for unconfigured sites only when the organization permits users to reload them locally. The relevant policy is:

InternetExplorerIntegrationReloadInIEModeAllowed

This policy applies to Windows Edge 92 and later and requires an Edge restart after a policy change. If the site is already controlled by an Enterprise Mode Site List, the administrator’s configuration takes precedence and the user may not be allowed to create a separate local rule.

For a managed computer, do not create a recurring personal workaround. Send IT the exact URL, path, login URL, redirect target, and a description of the failure so the application can be added and tested in the organization’s site list. Administrators can read the reload-policy documentation for the available behavior.

Enterprise deployment: the three-layer model

A reliable organization-wide deployment has three layers:

1. Enable IE integration in Edge.
2. Identify the sites that genuinely require the IE engine.
3. Deploy and maintain an Enterprise Mode Site List that maps those sites, paths, modes, redirects, and cookie rules.

Microsoft recommends a specific site list instead of sending every intranet site into IE mode. This limits the legacy exception and makes the remaining applications visible for modernization.

1. Enable IE integration with Group Policy

Install the current Microsoft Edge administrative templates, then configure the following policy in either Computer Configuration or User Configuration:

Administrative Templates
  > Microsoft Edge
  > Configure Internet Explorer integration

Set the policy to Enabled, then select Internet Explorer mode. The underlying policy is:

InternetExplorerIntegrationLevel

The documented value mapping is:

Value	Meaning
0	None
1	IEMode
2	NeedIE

For a machine-level registry deployment, Microsoft documents this location and value:

HKLM\SOFTWARE\Policies\Microsoft\Edge

Value name: InternetExplorerIntegrationLevel
Type:       REG_DWORD
Value:      1

Restart Edge after changing the integration policy. In a domain environment, refresh policy with:

gpupdate /force

Then verify what Edge actually received at edge://policy. The main policy guidance is in Microsoft’s IE-mode deployment documentation and the integration-level policy reference.

2. Configure the Enterprise Mode Site List

For Edge 78 and later, configure:

Administrative Templates
  > Microsoft Edge
  > Configure the Enterprise Mode Site List

The policy is:

InternetExplorerIntegrationSiteList

Its value can be an HTTPS URL such as:

https://intranet.example.com/sites.xml

Microsoft recommends hosting the list over HTTPS. Supported configurations can also use a network share or local file, but an authenticated or inaccessible location can prevent Edge from downloading the list.

3. Create the XML site list

A minimal site list can look like this:

<?xml version='1.0' encoding='utf-8'?>
<site-list version='1'>
  <site url='legacy.example.com'>
    <open-in>IE11</open-in>
  </site>
</site-list>

A path-specific entry can be more narrowly scoped:

<?xml version='1.0' encoding='utf-8'?>
<site-list version='2'>
  <site url='legacy.example.com/hr'>
    <compat-mode>default</compat-mode>
    <open-in>IE11</open-in>
  </site>
</site-list>

IE11 is historical Enterprise Mode schema terminology. With Edge configured for IE integration, the entry opens in Edge’s IE mode; it does not launch the retired standalone Internet Explorer application.

Site-list rules that commonly cause failures

• Do not put http:// or https:// in the url attribute. Omitting the protocol applies the rule to both HTTP and HTTPS.
• Do not use wildcards.
• Avoid query strings in site-list URLs.
• A host, subdomain, port, or path can be targeted, depending on the required scope.
• Use separate entries when the application needs different behavior for specific paths.
• Include the actual login, redirect, SSO, embedded-frame, and download hosts when the workflow crosses domains.
• Use the Enterprise Site List Manager instead of hand-editing XML where possible.

These rules come from Microsoft’s Enterprise Mode schema guidance.

Enterprise Mode Site List Manager

The built-in manager is available at:

edge://compat/SiteListManager

Administrators must enable:

EnterpriseModeSiteListManagerAllowed

The manager can add sites, choose IE mode or Edge mode, select compatibility and document modes, configure redirect behavior, define neutral sites, add shared cookies, import lists, and export XML. Microsoft says the standalone Site List Manager remains available but will not receive feature updates; future improvements are directed to the in-browser tool. See the Site List Manager guide and its access-policy reference.

Site-list precedence

Edge processes one Enterprise Mode Site List. The Edge-specific site-list policy takes precedence over the older Internet Explorer site-list policy. A cloud-hosted site list takes precedence over both the Edge URL-based site-list policy and the Internet Explorer site-list policy. If behavior seems inexplicable, check which list is actually being applied rather than editing several lists at once.

Intune and cloud-hosted site lists

Microsoft Intune

Use the Microsoft Edge settings in Intune’s Settings catalog to deploy the Edge integration and site-list policies to Windows 10 or later devices. For managed Windows devices, this is functionally equivalent to applying the corresponding Edge settings through Group Policy. Assign the policies to the intended device or user groups, allow them to arrive, restart Edge, and verify them at edge://policy. Microsoft’s deployment instructions are in Configure Microsoft Edge with Intune.

Microsoft 365 cloud site-list management

Organizations can manage a cloud-hosted IE-mode site list through the Microsoft Edge site-list experience in the Microsoft 365 admin center. The documented prerequisites and behavior include:

• a Microsoft Entra tenant;
• an administrator with the appropriate Edge administration role;
• the user being signed in to Edge with a work or school account so the client can download the cloud list;
• Edge 93 or later; and
• worldwide or GCC cloud availability as documented by Microsoft.

The policy is:

InternetExplorerIntegrationCloudSiteList

The default refresh interval is two hours, and the minimum configurable interval is 30 minutes. After the first assignment, restart Edge and allow approximately 60 seconds for the list to appear, or open edge://compat/enterprise and select Force Update. See Microsoft’s cloud site-list management guide and cloud site-list policy reference.

Local site list versus Enterprise Mode Site List

Local list	Enterprise list
Created by an individual user on an unmanaged or permitted device	Created and distributed by IT
Useful for testing or a temporary workaround	Designed for repeatable organization-wide deployment
Default entry lifetime is 30 days	Remains governed by the organization until changed
Can be configured from 0 to 90 days with InternetExplorerIntegrationLocalSiteListExpirationDays	Managed through policy, XML, Intune, or cloud administration
Does not currently sync across devices	Can be deployed consistently to assigned users or devices

With the default expiration, the user is warned on day 31 that the site will no longer load in IE mode and can add it again. That is a signal to move a recurring application into the Enterprise Mode Site List, not a reason to keep recreating the local entry.

Designing a reliable site list

Use the narrowest matching scope

Start with the smallest host and path that covers the application. A whole-domain IE-mode rule may unintentionally send modern pages, help systems, authentication pages, or unrelated applications through the legacy engine. Test whether a path-specific rule is sufficient.

Choose the rendering mode carefully

Use the default or logic-based compatibility behavior first. If the page layout or controls are broken, use IEChooser to inspect the document mode and add an explicit mode only when testing proves it is required. Microsoft advises against adding explicit document modes unnecessarily.

The site-list manager can also select Edge mode, IE mode, compatibility/document modes, and redirect behavior. Depending on the schema and manager version, the relevant open-in choices include IE11 for IE mode, MSEdge for modern Edge, None for a neutral site, and Configurable where user configuration is intended. Confirm the exact generated XML in the manager before production deployment.

Neutral sites and authentication

A modern sign-in provider may need to remain in Edge even when the application itself uses IE mode. Add that provider as a neutral site—None in the site-list manager—when the workflow requires it. An incomplete neutral-site configuration is a common cause of SSO redirect loops and repeated credential prompts.

Shared cookies

Edge and IE-mode processes do not automatically share all session cookies. Specific session cookies can be shared through Enterprise Mode Site List rules. Persistent cookies created with an Expires attribute are outside this feature and cannot be shared. Edge 99 and later support sharing in both directions; earlier versions supported only Edge-to-IE sharing. Share only the cookies and domains that the tested workflow requires.

Separate sessions

If the application requires an isolated session, use a separate Edge profile or configure the affected IE-mode site with merge-type='no-merge' in the site-list configuration. Microsoft also documents launching Edge with a separate user-data directory:

--user-data-dir=<path>

Cookie sharing from IE mode back to Edge is not supported in no-merge IE-mode sessions. Treat separate sessions as a deliberate trade-off, not a general fix for every login problem.

What IE mode supports—and what it does not

IE-mode compatibility can preserve	IE mode does not fully reproduce
IE5 through IE11 document modes where applicable	The standalone Internet Explorer desktop experience
Enterprise Mode and compatibility modes	Internet Explorer toolbars
ActiveX controls when the control, runtime, permissions, and security configuration are present	IE navigation menus and related browser settings
Browser Helper Objects	Microsoft Edge DevTools attached directly to the IE-mode document
Relevant IE security-zone and Protected Mode-related policies	Every old plug-in or third-party runtime
IE developer tools through IEChooser	IE11 F12 tools through the ordinary Edge F12 shortcut
Normal Edge extensions, except those that need to interact directly with IE page content	Automation based on the old Internet Explorer InternetExplorer object

Silverlight should not be treated as a currently supported dependency. Older compatibility lists may mention it historically, but Microsoft Silverlight reached end of support on October 12, 2021. Likewise, an ActiveX entry in the compatibility list does not install a missing control or make an unsupported control safe to use.

Debugging an IE-mode page

Ordinary Edge DevTools do not inspect the IE-mode document directly. Launch the IE-specific developer tools with:

%systemroot%system32f12IEChooser.exe

IEChooser lists the active IE-mode tabs. Select the relevant tab and inspect its document mode, scripts, network behavior, and DOM. Start with the default compatibility behavior, then test an explicit document mode only if the evidence points to one.

For administrator diagnostics, use:

Address	Purpose
edge://version	Check the installed Edge version and installation details
edge://policy	See the policies Edge received and whether they have errors
edge://compat/enterprise	Inspect the applied Enterprise Mode Site List and force an update
about:compat	Inspect compatibility and site-list behavior
edge://compat/SiteListManager	Manage a site list when the manager policy permits it

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Troubleshooting IE mode by symptom

“Reload in Internet Explorer mode” is missing

1. Confirm that the device is Windows. IE-mode policies are not supported on macOS, Android, or iOS.
2. Determine whether the computer is managed by work or school.
3. Ask IT whether InternetExplorerIntegrationReloadInIEModeAllowed is enabled.
4. Check the Edge version and, on older builds, look under More tools instead of the current menu location.
5. Check whether an Enterprise Mode Site List already controls the site. If it does, the administrator’s rule overrides the local command.
6. Restart Edge after policy changes.

The option is visible but greyed out

This usually indicates management policy, an enterprise site-list rule, or a restriction on unconfigured sites. Compare the behavior with edge://policy and ask the administrator to add the application rather than attempting to bypass the policy.

The site opens in normal Edge instead of IE mode

Check the configuration in this order:

1. Open edge://policy and confirm that the integration and site-list policies are present without errors.
2. Open edge://compat/enterprise and about:compat to see whether the expected list and entry are loaded.
3. Verify that the site-list URL is reachable from the affected computer.
4. Validate the XML.
5. Compare the entry with the URL actually used, including host, port, subdomain, and path.
6. Remove any protocol, wildcard, or query string from the XML url attribute.
7. Check whether a higher-precedence cloud or Edge list overrides the entry.
8. Restart Edge after changing policy, and run gpupdate /force when testing Group Policy.

The first navigation can occur before a newly assigned site list finishes downloading. Microsoft documents the DelayNavigationsForInitialSiteListDownload policy for organizations that need to prevent that early navigation from bypassing the list.

“Could not retrieve EMIE site list” appears

Check whether the list host is reachable, whether authentication to the host succeeds, and whether the configured URL is correct. A policy that blocks third-party cookies can interact with HTTP authentication and prevent the site-list download. Microsoft specifically documents checking BlockThirdPartyCookies and, where appropriate, allowing the site-list domain through CookiesAllowedForURLs. Do not broadly weaken cookie policy; allow only the required list domain after testing.

The site keeps asking for credentials or enters an SSO redirect loop

1. Confirm that the visible page really has the IE-mode indicator.
2. Record every login, identity-provider, redirect, and callback URL in the failing workflow.
3. Add required modern authentication endpoints as neutral sites so they remain in Edge.
4. Use narrowly scoped session-cookie sharing rules only when the application requires them.
5. Remember that persistent cookies with an Expires attribute cannot be shared by this feature.
6. Clear the test session or use a clean profile and retest.

A main application URL can be correctly listed while its sign-in provider is not. That mismatch is often the real cause of the loop. See Microsoft’s IE-mode FAQ and cookie-sharing guidance.

The page layout, script, or buttons are wrong

Use IEChooser to inspect the active IE-mode tab and its document mode. Begin with the default mode and test the application. Add a specific compatibility or document mode only when testing demonstrates that it is necessary. An explicit legacy mode can fix one page while creating new problems elsewhere in the application.

ActiveX does not work

IE mode can preserve ActiveX scenarios, but it cannot supply a missing control. Verify that the required control and its runtime are installed, that the control is permitted by Windows and IE security-zone settings, and that the user has the necessary permissions. Check whether the control is still supported by its vendor. If the application needs an old runtime that cannot be safely installed on current workstations, consider a controlled remote or virtualized environment instead.

Form data or file uploads fail after an engine switch

On supported versions, form data may transfer when navigation switches between modern Edge and IE mode, but file attachments are not transferred between the engines. A login or form may therefore appear to survive the transition while an attachment does not. Keep the upload step within the engine that owns it, or redesign the workflow.

The site displays a TLS or security warning

Determine whether the server still requires TLS 1.0 or TLS 1.1. Edge may show a connection-not-secure error because those protocols are disabled by default. The preferred fix is to update the server or application. Do not globally re-enable obsolete TLS protocols merely to keep one legacy application working; use a narrowly controlled remediation only if the organization has fully assessed the risk.

Edge says to reinstall with administrator privileges

If Edge reports that the page requires a system-level installation, check Windows updates, whether IE11 is disabled in Windows Features, and whether Edge was installed per-user rather than for the whole computer. Microsoft documents reinstalling Edge at system level with:

installer.exe --system-level

Use the official installer and your organization’s software-deployment process rather than downloading an unverified installer.

New windows or sessions behave unexpectedly

Check whether the application needs separate sessions. Use separate Edge profiles or a site-list rule with merge-type='no-merge'. You can also launch a separate profile using --user-data-dir=<path>. Remember that cookie sharing from IE mode back to Edge is not supported in a no-merge IE-mode session.

Alternatives when IE mode is not enough

1. Modernize the application. Replace IE-specific document modes, ActiveX dependencies, Browser Helper Objects, obsolete scripting, and old authentication flows.
2. Use the vendor’s supported modern version. A vendor upgrade is preferable to creating a permanent compatibility exception.
3. Use a controlled Windows virtual machine or remote application. This may be appropriate when the application needs dependencies that IE mode cannot provide or that should not be installed on ordinary workstations.
4. Use a separate legacy environment only as a last resort. Do not present a retired standalone Internet Explorer installation as a supported general solution.

A third-party “IE tab” extension is not automatically equivalent to Microsoft Edge IE mode. It may not provide the Microsoft IE11 MSHTML engine, ActiveX behavior, enterprise policy integration, or the same support model. Verify any such product independently with its vendor before relying on it.

Recommended rollout checklist for IT

1. Inventory IE-dependent applications and identify owners, vendors, business impact, and retirement dates. Microsoft’s Enterprise Site Discovery documentation can help with application inventory.
2. Test each application in normal Edge first.
3. Record all hosts involved in login, redirects, frames, downloads, APIs, and client certificates.
4. Enable IE integration through Group Policy or Intune.
5. Create the narrowest possible Enterprise Mode Site List entries.
6. Use neutral sites and cookie-sharing rules only when the tested workflow requires them.
7. Start with default document-mode logic; add explicit modes only with evidence.
8. Test ActiveX controls, security zones, authentication, forms, uploads, pop-ups, new windows, printing, and downloads.
9. Deploy to a pilot group and verify with edge://policy, edge://compat/enterprise, and IEChooser.
10. Track every exception and assign a modernization or retirement owner.

Frequently Asked Questions

Does IE mode reinstall Internet Explorer?

No. IE mode is a rendering mode inside the Windows desktop version of Microsoft Edge. It uses the IE11 MSHTML/Trident engine for selected pages but does not restore the retired standalone Internet Explorer application.

Can I use IE mode on a Mac, iPhone, or Android phone?

No. Microsoft’s documented IE-mode policies support Windows and mark macOS, Android, and iOS as unsupported.

How long will Microsoft support IE mode?

Microsoft currently commits to supporting IE mode through at least 2029 and says it will provide at least one year’s notice before retirement. That is a minimum commitment, not a promise that the feature will end in 2029.

Why does a site work in IE mode but its login still fail?

The application’s login or identity-provider URL may be using a different engine, or the required session cookies may not be shared. Add required authentication endpoints as neutral sites and configure narrowly scoped session-cookie sharing only when necessary.

Can IE mode run any old ActiveX or plug-in?

Not automatically. IE mode can preserve ActiveX scenarios, but the required control, runtime, permissions, security settings, and vendor support must still be present. Unsupported or missing runtimes may require application modernization or a controlled remote environment.

The Bottom Line

IE mode is the supported Windows bridge for a defined set of legacy websites and applications—not a revived Internet Explorer browser. Use the site-specific list on an unmanaged PC, and use an Enterprise Mode Site List through Group Policy, Intune, or cloud management in an organization. Scope entries narrowly, include authentication and redirect endpoints, verify the actual document mode and cookies, and keep a modernization plan for every remaining IE-mode dependency.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.