Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
ie_to_edge_bho.dll is part of Microsoft Edge’s IEtoEdge BHO, a browser helper that redirects incompatible Internet Explorer sites to Edge. It is not a standalone repair file to download, register, or replace. The supported fix is to update Edge, use Edge’s Internet Explorer mode for legacy sites, and check the two Edge policies that control the helper and redirection. If you want redirection stopped and the helper removed, disable redirection, enable the prevent-install policy, restart Edge, and let the next Edge update remove the existing BHO.
What is ie_to_edge_bho.dll?
Microsoft identifies this component as IEtoEdge BHO. BHO means Browser Helper Object, a type of Internet Explorer extension. Edge uses it to help redirect sites that Internet Explorer can no longer handle to Microsoft Edge. Microsoft’s documented redirection flow requires this helper; it is installed or blocked through Edge policy rather than treated as a consumer DLL that users maintain independently.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $117.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Internet Explorer support ended on June 15, 2022. That end of support is why opening an old site in Internet Explorer can lead to Edge instead. The supported compatibility route is Edge’s Internet Explorer mode: modern pages use the Edge engine, while sites that still require legacy behavior can be loaded with the Internet Explorer engine inside Edge.
The automatic redirection flow was introduced for Edge Stable beginning with version 87, provided the required policies allow it. Seeing a modern site open in Edge is therefore not, by itself, evidence that a DLL is broken.
Popular on Amazon
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Is ie_to_edge_bho.dll safe, or should I replace it?
Do not download a replacement copy from a DLL site, manually register it, or delete it from an installation folder. Microsoft documents IEtoEdge BHO as an Edge-managed compatibility component, not as a separately supported download. Replacing one file can leave the browser’s policy state and component version out of sync.
A file name alone is not enough to identify a legitimate component. A randomly named BHO, a copy outside the expected Microsoft installation, or a file that your security software flags should be handled as a possible security incident rather than repaired as IEtoEdge BHO. Microsoft’s malware encyclopedia warns that manual removal is not recommended for the specific malicious BHO entry it documents. That warning concerns the named malware case, not a diagnosis of the legitimate IEtoEdge component.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- If the symptom is simply that an Internet Explorer page opens in Edge, treat it as expected redirection first.
- If a known legacy site needs Internet Explorer behavior, configure IE mode instead of trying to keep ordinary Internet Explorer running.
- If a security product reports a suspicious BHO, isolate and scan the system with current security tooling and follow that product’s removal instructions.
How do I decide which fix I need?
Choose the path that matches the outcome you want. The same policies can either restore supported redirection or stop it and prepare the helper for removal.
| Goal | RedirectSitesFromInternetExplorerRedirectMode | RedirectSitesFromInternetExplorerPreventBHOInstall | What happens |
|---|---|---|---|
| Keep supported automatic redirection | Sitelist or Not Configured | Disabled or Not Configured | The IEtoEdge BHO can be installed and incompatible sites can redirect. |
| Stop redirection and remove the helper | Enabled, with the option that disables redirection | Enabled | Redirection is disabled; the next Edge update removes an existing BHO. |
| Run one legacy site with IE behavior | Leave organization policy unchanged unless your administrator directs otherwise | Do not block the helper if your managed setup depends on it | Use an IE mode page in Edge rather than ordinary Internet Explorer. |
On a personal computer, start with the browser settings and update checks. On a work or school computer, a greyed-out setting or a policy that returns after you change it usually means the organization controls Edge; an administrator must change the policy or Enterprise Site List.
How do I use Internet Explorer mode for an old site?
IE mode is the supported way to run a site that still depends on legacy Internet Explorer behavior, including older ActiveX-based applications where the organization permits them. It avoids forcing unsupported stand-alone Internet Explorer to remain the default browser.
- Open Microsoft Edge and enter
edge://settings/defaultBrowserin the address bar. - Turn on Allow sites to be reloaded in Internet Explorer mode.
- Restart Edge when prompted, or close every Edge window and open the browser again.
- On a current non-enterprise Edge installation, add the site under Internet Explorer mode pages.
- Open or reload the site. Edge will use IE mode for the address you added while ordinary pages continue to use the modern Edge engine.
The exact availability of the option depends on how Edge is managed. If the control is greyed out, the device is likely receiving an organizational policy. Ask the administrator to include the site in the organization’s Enterprise Site List and to deploy the relevant Edge policies instead of changing registry values locally.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsMicrosoft’s documented migration flow lists Windows 10 version 1709 or later, Windows 8.1, and Windows 7 as prerequisites for that redirection scenario. Those operating systems and their browser configurations can have different support status today, so verify the current Edge and Windows support requirements before a new deployment.
How do I restore automatic IE-to-Edge redirection?
If incompatible Internet Explorer sites should redirect but do not, check the policy that blocks BHO installation first, then the policy that controls redirection. A browser restart is required after a policy change because the prevent-install policy does not support dynamic refresh.
1. Check whether BHO installation is being prevented
The policy is named RedirectSitesFromInternetExplorerPreventBHOInstall. Microsoft documents it under SOFTWAREPoliciesMicrosoftEdge as a REG_DWORD.
- When this policy is enabled, the IEtoEdge BHO is not installed.
- When it is disabled or not configured, the helper is allowed to install when Edge’s redirection setup requires it.
- If an existing helper is present and you enable the policy, Microsoft says it is removed on the next Microsoft Edge update.
On a managed device, inspect the policy assignment through your organization’s normal Group Policy or management-console process. On an unmanaged device, avoid creating arbitrary registry entries just to force a DLL into place; use the documented policy name and value only if you understand who manages the computer and why the setting is needed.
2. Check the redirection mode
The second policy is RedirectSitesFromInternetExplorerRedirectMode. Microsoft says redirection works when this policy is set to Sitelist or left Not Configured. Setting it to disable prevents incompatible sites from redirecting to Edge.
Review the policy in the management tool used by the device, then restart Edge. You can also open edge://policy to see which Edge policies are being applied and whether a local setting is being overridden by an organization. If the policy shows a source you do not control, changing the browser’s settings page will not permanently alter the result.
3. Update Edge and test a known incompatible site
After correcting the policies, update Edge through its built-in update page and restart it. Test with the site that previously failed, not only with a modern public website. A successful redirect should open the page in Edge; a legacy application that requires the Internet Explorer engine should instead be assigned to IE mode.
How do I stop Internet Explorer from opening Edge and remove the BHO?
Use Microsoft’s post-deployment sequence rather than deleting a DLL or editing arbitrary COM registration entries. This approach changes the supported Edge policies and lets an Edge update perform the component cleanup.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Set RedirectSitesFromInternetExplorerRedirectMode to Enabled, then choose the option that disables redirection.
- Set RedirectSitesFromInternetExplorerPreventBHOInstall to Enabled.
- Restart Microsoft Edge so the policy change is loaded. If the device is managed, restart according to your organization’s change procedure and confirm the policy appears in
edge://policy. - Allow the next Microsoft Edge update to run. Microsoft documents that the existing IEtoEdge BHO is uninstalled by that update when the prevent-install policy is enabled.
- Reopen the old site. It should no longer be automatically redirected. If the site still needs legacy behavior, add it to Edge’s IE mode pages instead.
The removal is update-driven, not an immediate “delete this DLL” operation. If you need the helper again later, reverse the policies, restart Edge, and allow Edge to update so the supported redirection component can be installed when required.
What if ie_to_edge_bho.dll is missing or Edge says the helper is not working?
A missing-file message does not establish that the file should be downloaded separately. First determine whether the device is supposed to have the helper at all. If the prevent-install policy is enabled, its absence can be intentional. If redirection is disabled, a missing helper may have no practical effect because incompatible pages are not meant to redirect.
Check policy state before changing files
- Open
edge://policyand look for both redirection policies. - Confirm that RedirectSitesFromInternetExplorerRedirectMode is not set to disable if you expect automatic redirection.
- Confirm that RedirectSitesFromInternetExplorerPreventBHOInstall is not enabled if your setup requires the helper.
- Restart Edge after any correction, because these settings are not guaranteed to apply while the browser is running.
Confirm that Edge is current
Use Edge’s built-in update control, finish any pending restart, and retest. The documented removal and installation behavior is tied to an Edge update, so an out-of-date browser can leave the component state unchanged until the update completes.
Use IE mode instead of forcing ordinary Internet Explorer
If your actual requirement is one old application, configure that site as an IE mode page. This separates the compatibility requirement from the question of whether every Internet Explorer navigation should redirect. It also gives an administrator a site-by-site control through an Enterprise Site List.
Repair the browser installation only through supported Edge maintenance
If Edge itself cannot update or its policy page is damaged, use the standard Windows and Edge maintenance options available for your edition, then reboot and retest. Do not copy a DLL from another computer: the correct component version is tied to the installed Edge release and policy state.
How do organizations manage IEtoEdge BHO and legacy sites?
Organizations should manage the transition centrally rather than asking each user to edit a registry value. Microsoft’s migration documentation describes an Enterprise Site List for sites that require IE mode, together with the Edge policies that govern redirection.
Build the site list around business requirements
Identify the applications that genuinely require the Internet Explorer engine and place only those sites in the Enterprise Site List. Modern sites should remain on the normal Edge path. A narrow list reduces unexpected compatibility behavior and makes it easier to retire legacy entries when applications are upgraded.
Deploy the policies consistently
Use the organization’s Group Policy or mobile-management platform to deploy RedirectSitesFromInternetExplorerRedirectMode, RedirectSitesFromInternetExplorerPreventBHOInstall, and the IE mode configuration. A user-level setting that conflicts with a device policy will not be a reliable fix; the effective policy shown in edge://policy is the one that determines behavior.
Recommended Free Tools
Plan removal as a staged change
When the organization no longer needs automatic redirection, first disable it through the redirect-mode policy, then enable the prevent-install policy. Schedule or wait for the next Edge update, which removes an existing BHO under that configuration. Keep the Enterprise Site List and IE mode entries for applications that still require them until those applications are modernized.
What should I do if the DLL looks suspicious?
Separate a legitimate IEtoEdge diagnosis from a malware investigation. Microsoft’s malware encyclopedia describes malicious BHOs as DLLs registered to run in Internet Explorer and specifically advises against manual removal for the threat entry it covers. If your security software names a threat, follow its quarantine and cleanup workflow rather than deleting a file by hand.
- Disconnect the affected computer from sensitive networks if your security team’s procedure calls for containment.
- Record the detection name, file path, and security-product guidance.
- Run the product’s current scan and apply its recommended remediation.
- After cleanup, update Edge and review both redirection policies so a legitimate compatibility component is not confused with the detected file.
A Microsoft-looking filename in an unexpected directory is not proof of authenticity. Conversely, a browser redirection by itself is not proof of infection; it can be normal behavior for an incompatible Internet Explorer site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why do the common “DLL fixes” fail?
Downloading a replacement DLL
A downloaded file may be the wrong architecture, version, or build, and it does not recreate the Edge policy and update state that controls IEtoEdge BHO. It can also introduce an untrusted binary.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Registering the DLL with a command
IEtoEdge BHO is not documented as a standalone consumer COM component that users should register manually. Registration changes can create a state Edge does not support and may not survive the next browser update.
Deleting the file to stop redirects
Deleting one file does not change RedirectSitesFromInternetExplorerRedirectMode. Edge can restore a supported component during a later update, while the underlying redirect policy remains active. Use the policy sequence instead.
Changing a setting without restarting Edge
The prevent-install policy does not support dynamic refresh. A policy can appear correct in an administrative console while an already-running Edge process continues using the previous state. Restart Edge after policy changes and then verify the effective values.
Disabling all compatibility features for one broken site
If only one application needs legacy behavior, disabling every redirect can create a larger usability problem. Add the specific site to IE mode or the Enterprise Site List and leave modern browsing on the normal Edge path.
How do I verify that the fix worked?
Verification should match your chosen outcome. A single browser launch is not enough because policy and update changes can take effect at different times.
- Open
edge://policyand confirm the effective values for both redirection policies. - Restart Edge after policy changes.
- For restored redirection, open a site known to be incompatible with Internet Explorer and confirm it launches in Edge.
- For a legacy application, open the site from the IE mode pages list and confirm the page is running in IE mode rather than ordinary Edge mode.
- For BHO removal, confirm the prevent-install policy is enabled, complete the next Edge update, restart Edge, and check that redirection remains disabled.
- If a security product raised an alert, verify its remediation status separately; browser behavior alone cannot prove that a detected file is gone.
If the policy values repeatedly revert, the device is probably receiving them from a central management service. Escalate the effective policy and the Edge version to the administrator instead of repeatedly editing local settings.
If the policy, update, and browser-maintenance steps are difficult to manage manually, Outbyte PC Repair can serve as an optional shortcut for common Windows issues, broken system elements, invalid redirects, shared DLL problems, cleanup, and crash diagnostics. It complements antivirus software rather than replacing it; results vary, and no tool repairs every crash. It runs on Windows 11, 10, 8, and 7, with a category-based free trial of at least two days followed by a paid subscription.
Frequently asked questions
Can I keep using Internet Explorer after June 15, 2022?
Internet Explorer support ended on that date, so relying on the stand-alone browser is not a supported long-term plan. Use Edge IE mode for sites that still require the legacy engine and ask the application owner about modernization.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Why is the Internet Explorer mode option missing in Edge?
The option can be unavailable or greyed out when an organization controls Edge through policy. An administrator must configure the relevant policy or Enterprise Site List; a local registry edit may be overwritten by management.
Will enabling the prevent-install policy remove the BHO immediately?
No. Microsoft documents removal with the next Microsoft Edge update. Restart Edge after changing the policy, then allow the update to complete before checking the component state.
Does a redirect prove that ie_to_edge_bho.dll is present?
Redirection requires the IEtoEdge BHO in Microsoft’s documented flow, but the visible redirect alone is not a file-integrity check. Confirm the effective policies and Edge version rather than inferring the exact DLL path from browser behavior.
What if an old application fails even in IE mode?
IE mode addresses browser-engine compatibility, not application-side defects, authentication changes, or a server that has been retired. Capture the site address, the IE mode policy state, and the application error, then have the site owner or administrator review the Enterprise Site List and the application’s current support requirements.
Frequently Asked Questions
Can I keep using Internet Explorer after June 15, 2022?
Internet Explorer support ended on that date, so relying on the stand-alone browser is not a supported long-term plan. Use Edge IE mode for sites that still require the legacy engine and ask the application owner about modernization.
Why is the Internet Explorer mode option missing in Edge?
The option can be unavailable or greyed out when an organization controls Edge through policy. An administrator must configure the relevant policy or Enterprise Site List; a local registry edit may be overwritten by management.
Will enabling the prevent-install policy remove the BHO immediately?
No. Microsoft documents removal with the next Microsoft Edge update. Restart Edge after changing the policy, then allow the update to complete before checking the component state.
Does a redirect prove that ie_to_edge_bho.dll is present?
Redirection requires the IEtoEdge BHO in Microsoft’s documented flow, but the visible redirect alone is not a file-integrity check. Confirm the effective policies and Edge version rather than inferring the exact DLL path from browser behavior.
What if an old application fails even in IE mode?
IE mode addresses browser-engine compatibility, not application-side defects, authentication changes, or a server that has been retired. Capture the site address, the IE mode policy state, and the application error, then have the site owner or administrator review the Enterprise Site List and the application’s current support requirements.
Quick Recap
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.
