Knowledge Base
Ways to Open Internet Explorer with Selenium WebDriver
A practical guide to launching Internet Explorer with Selenium WebDriver, the driver and configuration caveats, modern alternatives, and where proxies fit.
Automating Internet Explorer with Selenium still comes up for teams maintaining legacy internal applications that were built for that browser. While IE is end-of-life and largely superseded, Selenium can still drive it through the dedicated InternetExplorerDriver, provided the environment is configured carefully.
This walkthrough explains the practical way to open IE with Selenium WebDriver, the well-known configuration caveats, the modern IE-mode alternative, and where proxies become relevant in legacy automation.
The basic way to launch IE
To open Internet Explorer you use the InternetExplorerDriver, which acts as the bridge between Selenium and the browser. Conceptually you point Selenium at the IE driver executable and create an IE WebDriver instance, then navigate as you would with any other browser.
The driver executable must match your system architecture and be discoverable on your PATH or supplied explicitly. Mismatched driver versions or a missing executable are the most frequent reasons the browser fails to launch at all.
Configuration caveats unique to IE
IE automation is notoriously sensitive to environment settings. The classic requirements include:
- Setting Protected Mode to the same value across all security zones, otherwise the session becomes unstable.
- Configuring the browser zoom level to 100%, since other levels confuse click coordinates.
- Applying any required registry settings that the IE driver documentation calls for.
Because of these constraints, IE automation tends to need a tightly controlled, consistent machine configuration to run reliably, which is part of why teams migrate away from it.
Modern alternatives to native IE
Since Internet Explorer is retired, the recommended path for legacy apps is IE mode in Microsoft Edge, which renders IE-dependent pages within a supported, maintained browser. Selenium can target Edge configured to use IE mode, giving you legacy compatibility without depending on the standalone IE browser.
For genuinely new automation, modern browsers like Edge or Chrome are far more stable and better supported. Reserve native IE automation for cases where it is strictly required by an old internal system.
Where proxies fit in legacy automation
Proxy needs do not change much just because the browser is older. A single local IE session usually needs no proxy, but automation that touches many internal or external endpoints, or runs across machines, can benefit from routing through proxies for stability and request distribution.
For general tasks, datacenter proxies are a value-focused option, while residential proxies may suit location-sensitive external targets. Our buying guide helps match a plan to your setup.
What to compare before buying
Before you order, weigh these points so the proxies you pick match your real workload and budget:
- Proxy type: datacenter for general automation, residential for sensitive external targets
- Compatibility with your automation framework and proxy configuration method
- Concurrency support if you run automation across several machines
- Geographic coverage for any region-specific external endpoints
- Session stability for multi-step legacy workflows
- Transparent pricing: confirm the exact package before ordering
- Support responsiveness for troubleshooting connectivity issues
Frequently asked questions
Yes, through the InternetExplorerDriver, but IE is end-of-life. Microsoft recommends using IE mode in Edge for legacy pages, which Selenium can also target.
Common causes are a missing or mismatched driver executable, Protected Mode settings that differ across zones, or a zoom level other than 100%. IE automation needs a carefully aligned configuration.
IE mode runs IE-dependent pages inside Microsoft Edge, giving legacy compatibility within a supported, maintained browser. It is the recommended path now that standalone IE is retired.
No. Reserve native IE automation for strictly required legacy systems and use modern browsers like Edge or Chrome for new work, since they are far more stable and better supported.
Not for a single local session. Proxies help when automation touches many endpoints or runs across machines, where distributing requests improves stability.
Datacenter proxies are a value-focused choice for general tasks, while residential proxies may be more suitable for location-sensitive external targets.
Related pages worth comparing
Have a comparison question about how to open ie using selenium webdriver? Email info@comparebestproxy.com.