ANAVEM
Reference
Languagefr
How to Uninstall Internet Explorer from Windows Server 2019-2025

How to Uninstall Internet Explorer from Windows Server 2019-2025

Remove Internet Explorer 11 from Windows Server using Settings app, DISM command line, or PowerShell. Complete guide with verification steps and Edge migration tips.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 17, 2026 12 min 7
easywindows-server 8 steps 12 min

Why Should You Remove Internet Explorer from Windows Server?

Internet Explorer 11 reached end-of-support on June 15, 2022, making it a security liability on your Windows Server infrastructure. While IE11 remains available as an optional feature on Windows Server 2019, 2022, and 2025, Microsoft strongly recommends migrating to Microsoft Edge for security, performance, and compatibility reasons.

Removing Internet Explorer from your Windows Server environment offers several benefits:

  • Enhanced Security: Eliminates potential attack vectors from an unsupported browser
  • Reduced Attack Surface: Fewer components mean fewer potential vulnerabilities
  • Compliance Requirements: Many security frameworks now require removal of unsupported software
  • Resource Optimization: Frees up disk space and reduces system complexity

This tutorial covers three reliable methods to completely remove Internet Explorer from Windows Server, along with proper verification steps and Edge migration strategies.

What Are the Prerequisites for Removing Internet Explorer?

Before starting the removal process, ensure you have the necessary access and tools in place. You'll need Administrator privileges on the target Windows Server, which can be Windows Server 2016, 2019, 2022, or the latest 2025 version.

Microsoft Edge should be installed and configured as your replacement browser. Most modern Windows Server installations include Edge by default, but older systems may require manual installation. Additionally, you should have basic familiarity with command-line tools like PowerShell or Command Prompt, as some methods require these interfaces.

Pro tip: Document your current browser configuration and any applications that specifically require Internet Explorer before proceeding. This documentation will be invaluable if you need to configure IE mode in Edge later.
Implementation Guide

Full Procedure

01

Verify Current Internet Explorer Installation

Before removing Internet Explorer, check if it's currently installed and which version you're running. This helps determine the best removal method.

Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -eq "Internet-Explorer-Optional-amd64"}

This PowerShell command shows the current state of IE11. Look for the State field - it should show Enabled if IE is installed.

You can also check by opening the Start menu and searching for "Internet Explorer". If it appears, it's currently installed.

Pro tip: Take a screenshot of your current browser setup before proceeding. This helps if you need to document the change or troubleshoot later.
02

Install Microsoft Edge (If Not Present)

Since Internet Explorer reached end-of-support on June 15, 2022, Microsoft Edge is the recommended replacement. Most Windows Server 2019+ installations include Edge, but verify it's available.

Get-AppxPackage -Name "Microsoft.MicrosoftEdge*" -AllUsers

If Edge isn't installed, download it from the Microsoft Edge Enterprise page. For server environments, use the MSI installer:

MicrosoftEdgeEnterpriseX64.msi /quiet /norestart

Verification: Open Edge by typing msedge in Run dialog (Win+R) or search for "Microsoft Edge" in the Start menu.

Warning: Don't remove IE without having Edge available. Some legacy applications may need IE mode in Edge to function properly.
03

Method 1 - Remove IE Using Settings App

The Settings app provides the most user-friendly way to remove Internet Explorer on Windows Server 2019 and newer versions.

Open Settings by pressing Win+I or clicking the Start button and selecting the gear icon.

Navigate to AppsApps & featuresOptional features. You can also directly access this by running:

ms-settings:appsfeatures

Scroll through the list of installed features until you find Internet Explorer 11. Click on it to select it, then click the Uninstall button.

Windows will prompt you to restart the server. Click Restart now to complete the removal process.

Verification: After restart, search for "Internet Explorer" in the Start menu. It should no longer appear in the results.

04

Method 2 - Remove IE Using DISM Command Line

DISM (Deployment Image Servicing and Management) provides a command-line method that works across all supported Windows Server versions and is ideal for automation.

Open Command Prompt as Administrator. Right-click the Start button and select "Windows PowerShell (Admin)" or "Command Prompt (Admin)".

Run the following DISM command to disable the Internet Explorer feature:

dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64

The system will prompt you to restart. Type Y and press Enter to restart immediately.

For automated scripts where you want to suppress the restart prompt, use the quiet flag:

dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64 /quiet

Verification: After restart, run this command to confirm IE is disabled:

dism /online /get-featureinfo /featurename:Internet-Explorer-Optional-amd64

The output should show State : Disabled.

05

Method 3 - Remove IE Using PowerShell

PowerShell offers the most flexible approach, especially for remote server management and scripting scenarios.

Open PowerShell as Administrator. You can do this by right-clicking the Start button and selecting "Windows PowerShell (Admin)".

Use the Disable-WindowsOptionalFeature cmdlet to remove Internet Explorer:

Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online

To avoid the automatic restart and handle it manually later, add the -NoRestart parameter:

Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online -NoRestart

For remote server management, you can execute this on multiple servers:

$servers = @("SERVER1", "SERVER2", "SERVER3")
foreach ($server in $servers) {
    Invoke-Command -ComputerName $server -ScriptBlock {
        Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online -NoRestart
    }
}

Verification: Check the feature status with:

Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -eq "Internet-Explorer-Optional-amd64"}
Pro tip: Save your PowerShell commands in a .ps1 script file for future use across multiple servers. This ensures consistency and saves time.
06

Configure Edge IE Mode for Legacy Applications

After removing Internet Explorer, some legacy web applications may not work properly. Microsoft Edge includes IE mode to handle these scenarios.

Open Microsoft Edge and navigate to edge://settings/defaultBrowser.

Under "Internet Explorer compatibility", set "Allow sites to be reloaded in Internet Explorer mode" to "Allow".

For enterprise environments, create an Enterprise Mode Site List. Create an XML file with your legacy sites:

<?xml version="1.0" encoding="UTF-8"?>
<site-list version="1">
  <site url="legacy-app.company.com">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
</site-list>

Deploy this XML file via Group Policy under Computer Configuration → Administrative Templates → Windows Components → Microsoft Edge → Configure the Enterprise Mode Site List.

Verification: Navigate to a site configured for IE mode. You should see an "Internet Explorer" icon in the address bar indicating IE mode is active.

07

Update File Associations and Default Browser

After removing Internet Explorer, Windows automatically reassigns HTML file associations to Microsoft Edge. However, you should verify and configure these settings properly.

Open Settings and navigate to AppsDefault apps.

Scroll down to "Web browser" and ensure Microsoft Edge is selected. If not, click on the current browser and select Edge from the list.

For HTML file associations, scroll down to "Choose default apps by file type" and verify these extensions point to Edge:

  • .htm
  • .html
  • .shtml
  • .xht
  • .xhtml

You can also configure this via PowerShell for multiple servers:

# Set Edge as default browser
$EdgePath = "${env:ProgramFiles(x86)}\Microsoft\Edge\Application\msedge.exe"
Set-ItemProperty -Path "HKLM:\SOFTWARE\Classes\http\shell\open\command" -Name "(Default)" -Value "$EdgePath %1"
Set-ItemProperty -Path "HKLM:\SOFTWARE\Classes\https\shell\open\command" -Name "(Default)" -Value "$EdgePath %1"

Verification: Double-click an HTML file. It should open in Microsoft Edge instead of showing an error or prompt.

08

Verify Complete Removal and Test Functionality

Perform comprehensive verification to ensure Internet Explorer is completely removed and your server remains functional.

Check that IE is no longer accessible through these methods:

  • Search "Internet Explorer" in Start menu (should return no results)
  • Run iexplore in the Run dialog (should fail)
  • Check Programs and Features (IE should not be listed)

Verify the removal using PowerShell:

Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Internet-Explorer*"}

The output should show State : Disabled for the Internet-Explorer-Optional-amd64 feature.

Test web functionality by opening various websites in Microsoft Edge to ensure normal browsing works correctly.

For servers running web applications, test that IIS and other web services continue to function normally:

# Check IIS status if applicable
Get-Service -Name W3SVC -ErrorAction SilentlyContinue
# Test web server response
Invoke-WebRequest -Uri "http://localhost" -UseBasicParsing
Warning: Some older management consoles or applications may still try to launch IE. Test all critical applications after removal and configure IE mode in Edge if needed.

Frequently Asked Questions

Can Internet Explorer be completely removed from Windows Server?+
Internet Explorer cannot be completely removed from Windows Server because core IE components are integrated into the Windows operating system for compatibility. However, you can disable and uninstall the IE application itself, making it inaccessible to users while leaving essential system components intact. This approach provides security benefits while maintaining system stability.
What happens to HTML files after removing Internet Explorer from Windows Server?+
After removing Internet Explorer, Windows automatically reassigns HTML file associations to Microsoft Edge. Double-clicking HTML files will open them in Edge instead of IE. You can verify and manually configure these associations through Settings > Apps > Default apps > Choose default apps by file type if needed.
Do I need to restart Windows Server after removing Internet Explorer?+
Yes, restarting Windows Server is required to complete the Internet Explorer removal process. The restart applies the feature changes and ensures IE is fully disabled. You can choose to restart immediately during the removal process or defer the restart using the -NoRestart parameter in PowerShell commands.
How do I handle legacy applications that require Internet Explorer after removal?+
Use Microsoft Edge's IE mode feature to run legacy applications that require Internet Explorer compatibility. Configure IE mode through Edge settings or deploy an Enterprise Mode Site List via Group Policy to automatically load specific sites in IE compatibility mode. This provides the necessary compatibility without requiring IE installation.
Can I remove Internet Explorer from Windows Server Core installations?+
Yes, you can remove Internet Explorer from Windows Server Core using DISM or PowerShell commands since these methods don't require the graphical Settings app. Use the command line methods: 'dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64' or the PowerShell equivalent 'Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online' for Server Core environments.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...