Skip to content
anavem.com logoanavem.com logo
Windows ServerTutorialsPowershell

How to Uninstall Internet Explorer from Windows Server 2019-2025

Remove the end-of-support Internet Explorer 11 optional feature from Windows Server 2019, 2022, and 2025 using Settings, DISM, or PowerShell, then verify the removal and set up Edge IE mode for legacy apps.

Difficulty
Intermediate
Time required
20-30 minutes
Steps
8
Platform
Windows Server
Version
2019, 2022, 2025
How to uninstall Internet Explorer from Windows Server 2019, 2022, and 2025 using Server Manager, PowerShell, or DISM.
View full image
Table of contents

Quick Answer

Go to the steps

Internet Explorer 11 is an optional feature on Windows Server 2019-2025, so you disable it rather than uninstall an app. The fastest path is an elevated DISM command that turns off the feature, followed by a restart. Confirm Microsoft Edge is installed first, and set up Edge IE mode afterward for any legacy apps that still need IE.

  1. Confirm Edge is installed and note any apps that require IE.
  2. Open an elevated Command Prompt or PowerShell (Run as Administrator).
  3. Run: dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64
  4. Restart the server when prompted.
  5. Verify with dism /online /get-featureinfo /featurename:Internet-Explorer-Optional-amd64 and configure Edge IE mode if needed.
Command
dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64

Expected result: After a restart, the Internet-Explorer-Optional-amd64 feature reports State : Disabled, and iexplore no longer launches while Microsoft Edge remains available.

Key takeaways

  • You will learn three reliable ways to remove the Internet Explorer 11 optional feature from Windows Server 2019, 2022, and 2025 - through the Settings app, DISM, and PowerShell - plus how to verify the removal. You will also learn how to keep Edge in place and configure IE mode so legacy web apps continue to work.
  • Internet Explorer 11 reached end-of-support on June 15, 2022, so leaving it enabled adds an unsupported, unpatched browser to your attack surface. Removing it reduces vulnerability exposure and helps meet compliance frameworks that require unsupported software to be uninstalled.
  • Internet Explorer 11 is an optional feature on Windows Server 2019-2025 that you can safely disable once Edge and IE mode are in place to keep legacy apps working.

Introduction

Internet Explorer 11 is still shipped as an optional feature on Windows Server 2019, 2022, and 2025, but it reached end-of-support on June 15, 2022 and no longer receives security fixes. Because it is an optional feature rather than a full application, you do not uninstall it like a normal program - you disable the Internet-Explorer-Optional-amd64 feature, which requires a restart to fully take effect. This guide walks through three interchangeable methods: the Settings app (GUI), DISM, and PowerShell (including remote execution across many servers), so you can pick whichever fits your workflow. Before removing IE, confirm that Microsoft Edge is present as the supported replacement, since some legacy web apps still depend on the IE rendering engine. After removal, you will configure Edge IE mode and an Enterprise Mode Site List so those apps keep working, then verify that IE is gone and services like IIS remain healthy.

Who this is for: Sysadmins, MSP technicians, and IT pros managing one or many Windows Server 2019-2025 hosts who need a repeatable, automation-friendly removal process.

Before you start

Access
You need local Administrator privileges on the target Windows Server, and Remote Server Administration or WinRM access if you plan to disable the feature on multiple servers with Invoke-Command. Deploying an Enterprise Mode Site List for Edge IE mode additionally requires rights to edit and link the relevant Group Policy Object.
Required roles
  • Local Administrator on the target Windows Server
  • Group Policy edit rights (only if deploying the Edge Enterprise Mode Site List via GPO)
  • Administrator
Vendor
Microsoft
Tested environment
Windows Server 2019/2022/2025
  • Administrator permissions required

Applies to Windows Server 2019, 2022, and 2025 (Windows Server 2016 also has the IE optional feature). Requires Administrator privileges.

About 20-30 minutes per server, including a restart.

Warning: Install and verify Microsoft Edge before removing IE

Do not disable the Internet Explorer optional feature until Microsoft Edge is confirmed present and launchable. Removing IE without a supported replacement browser leaves the server with no vendor-supported browser and can break IE-dependent workflows.

Warning: Legacy applications may stop working

Some older management consoles, intranet portals, and line-of-business web apps depend on Internet Explorer. Test every critical application after removal, and configure Edge IE mode for any site that requires it before rolling this change out to production.

Warning: A restart is required to complete removal

Disabling the Internet-Explorer-Optional-amd64 feature via Settings, DISM, or PowerShell requires a server reboot to finish. Schedule a maintenance window; use /norestart, /quiet, or -NoRestart only when you control the reboot timing yourself.

1Verify the current Internet Explorer installation

Confirm whether IE11 is enabled and identify the correct feature name before making changes.

Admin path
Start menu > search "Internet Explorer"

Open an elevated PowerShell session and query the state of the Internet Explorer optional feature. Look at the State field in the output - it will read Enabled if IE11 is currently installed, or Disabled if it has already been removed.

You can also confirm interactively: open the Start menu and search for Internet Explorer. If it appears in the results, the feature is present.

Document your current browser configuration and note any internal applications that are known to require Internet Explorer, so you can add them to an Edge IE mode site list later.

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

Expected result: The command returns the feature with State : Enabled, confirming IE11 is installed and the feature name is Internet-Explorer-Optional-amd64.

Note

On Windows Server, IE11 is an optional feature rather than a full application, so it will not appear the same way it does on client Windows. Record the current state before changing anything - this baseline helps with troubleshooting and rollback.

2Install or confirm Microsoft Edge as the replacement browser

Ensure Edge is present before removing IE so the server retains a supported browser.

Admin path
Run dialog (Win+R) > msedge

Before touching Internet Explorer, verify that Microsoft Edge is available. In an elevated PowerShell session, check for the Edge package.

If Edge is not present, download the Microsoft Edge for Business MSI from the official Microsoft Edge Enterprise download page and install it silently:

Code
MicrosoftEdgeEnterpriseX64.msi /quiet /norestart

After installation, launch Edge to confirm it works: press Win+R, type msedge, and press Enter, or search for Microsoft Edge in the Start menu.

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

Expected result: Edge either returns an installed package entry, or launches successfully to a new tab after MSI installation - confirming a supported browser is available.

Note

Do not remove IE until Edge is confirmed working. Some legacy web apps require IE mode inside Edge, which is unavailable if Edge itself is missing. Most Windows Server 2019+ builds ship with Edge, but minimal or older images may not.

3Method 1 - Remove IE using the Settings app

Uninstall IE11 through the GUI on Windows Server 2019 and newer.

Admin path
Settings > Apps > Apps & features > Optional features > Internet Explorer 11 > Uninstall

This is the most straightforward method for a single server with a desktop experience.

  1. Open Settings with Win+I, or run ms-settings:appsfeatures from the Run dialog to jump straight to the right page.
  2. Navigate to Apps > Apps & features > Optional features.
  3. Scroll the installed feature list and select Internet Explorer 11.
  4. Click Uninstall.
  5. When prompted, click Restart now to complete removal.

Expected result: Internet Explorer 11 disappears from the Optional features list after the restart, and a Start menu search returns no IE result.

Note

This method requires the Server with Desktop Experience installation option. On Server Core there is no Settings app - use the DISM or PowerShell methods instead. A restart is required to fully complete the removal.

4Method 2 - Remove IE using DISM

Disable the IE feature from the command line for automation-friendly removal.

Admin path
Start button (right-click) > Command Prompt (Admin)

DISM works across every supported Windows Server version, including Server Core, and is ideal for scripted deployments.

  1. Right-click the Start button and open Command Prompt (Admin) or Windows PowerShell (Admin).
  2. Run the disable-feature command below. When prompted to restart, type Y and press Enter.

For unattended scripts where you want to suppress the restart prompt, append /quiet:

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

After the restart, confirm the state:

Code
dism /online /get-featureinfo /featurename:Internet-Explorer-Optional-amd64
Cmd
dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64

Expected result: DISM reports "The operation completed successfully" and the get-featureinfo output shows State : Disabled after restart.

Note

/quiet suppresses the prompt but the reboot still happens automatically unless you also manage restart behavior in your script. The feature name is case-insensitive but must be spelled exactly as shown.

5Method 3 - Remove IE using PowerShell

Disable IE with PowerShell, including remote execution across multiple servers.

Admin path
Start button (right-click) > Windows PowerShell (Admin)

PowerShell is the most flexible option, especially for remote and bulk management.

  1. Right-click the Start button and open Windows PowerShell (Admin).
  2. Run Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online. Add -NoRestart if you want to control the reboot manually.
  3. To remove IE across a fleet, loop over a server list with Invoke-Command:
Code
$servers = @("SERVER1", "SERVER2", "SERVER3")
foreach ($server in $servers) {
    Invoke-Command -ComputerName $server -ScriptBlock {
        Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online -NoRestart
    }
}

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

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

Expected result: The cmdlet completes and reports RestartNeeded True; after reboot the feature verification shows State: Disabled.

Note

Replace SERVER1, SERVER2, SERVER3 with your actual hostnames. Remote execution requires WinRM/PowerShell remoting enabled and appropriate admin credentials on the targets. Save the commands as a .ps1 script for repeatable, consistent rollouts. Using DISM vs PowerShell disables the same underlying feature - pick whichever fits your tooling.

6Configure Edge IE mode for legacy applications

Keep IE-dependent web apps working after IE is removed.

Admin path
edge://settings/defaultBrowser > Internet Explorer compatibility

Removing the IE optional feature does not remove Edge's built-in IE mode, so legacy sites can still be rendered with the Trident engine.

  1. Open Edge and go to edge://settings/defaultBrowser.
  2. Under Internet Explorer compatibility, set Allow sites to be reloaded in Internet Explorer mode to Allow.
  3. For enterprise deployment, create an Enterprise Mode Site List XML that lists each legacy site:
Code
<?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>
  1. Deploy the file via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Edge > Configure the Enterprise Mode Site List, pointing the policy at the XML location.
YAML
<?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>

Expected result: When you open a configured legacy site, an Internet Explorer icon appears in the Edge address bar, confirming IE mode is active.

Note

Replace legacy-app.company.com with your real site URLs. The Microsoft Edge administrative templates (ADMX) must be installed in your Group Policy central store for the policy to appear. IE mode depends on the MSHTML/Trident engine that remains part of Windows even after the IE feature is removed.

7Update default browser and file associations

Point HTML files and the default browser to Edge after IE removal.

Admin path
Settings > Apps > Default apps > Web browser

After IE is removed, verify that Edge is the default handler for web content.

  1. Open Settings > Apps > Default apps.
  2. Under Web browser, confirm Microsoft Edge is selected; if not, click the current entry and choose Edge.
  3. Scroll to Choose default apps by file type and confirm these point to Edge: .htm, .html, .shtml, .xht, .xhtml.

For scripting the default browser across multiple servers, set the shell open commands in the registry:

Code
$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"
PowerShell
$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"

Expected result: Double-clicking an HTML file opens it in Microsoft Edge, and the default apps page lists Edge for web content types.

Note

Windows usually reassigns HTML associations to Edge automatically when IE is removed, so this step is verification more than reconfiguration. Confirm the Edge install path matches your environment before running the registry commands - the path can differ on custom deployments. For managed fleets, prefer Group Policy default-associations XML over per-machine registry edits.

8Verify complete removal and test functionality

Confirm IE is gone and critical services still function.

Admin path
Run dialog (Win+R) > iexplore

Run a final confirmation pass:

  1. Search Internet Explorer in the Start menu - it should return no results.
  2. Run iexplore in the Run dialog - it should fail to launch.
  3. Open Programs and Features - IE should not be listed.
  4. Confirm the feature state in PowerShell (command below) shows State : Disabled.
  5. Open several sites in Edge to confirm normal browsing.
  6. On servers hosting web workloads, confirm IIS and web responses still work:
Code
Get-Service -Name W3SVC -ErrorAction SilentlyContinue
Invoke-WebRequest -Uri "http://localhost" -UseBasicParsing
PowerShell
Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Internet-Explorer*"}

Expected result: The feature query returns State: Disabled, iexplore fails to launch, IE is absent from Start/Programs, and IIS/web requests still respond normally.

Note

Some older management consoles or line-of-business apps may still attempt to invoke IE. Test every critical application after removal and add any broken web app to the Edge IE mode site list from the earlier step. The W3SVC check silently returns nothing on servers without IIS installed, which is expected.

Confirming Internet Explorer Is Disabled and Edge Is in Place

Confirm configuration

After completing the removal and rebooting, the goal is a Windows Server where the Internet Explorer 11 optional feature is fully disabled, Microsoft Edge is the supported default browser, and any IE-dependent web apps continue to load through Edge IE mode.

The authoritative signal is the optional feature state. Running Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -eq "Internet-Explorer-Optional-amd64"} should report State : Disabled, and dism /online /get-featureinfo /featurename:Internet-Explorer-Optional-amd64 should show the same. This confirms the feature is off at the OS level, not merely hidden from the UI.

Beyond the feature flag, verify behaviour: iexplore in the Run dialog should fail to launch, Internet Explorer should return no results in the Start menu, and it should not appear under Programs and Features. Double-clicking an .htm or .html file should open Microsoft Edge. For servers hosting web workloads, confirm services are unaffected - Get-Service -Name W3SVC and Invoke-WebRequest -Uri "http://localhost" -UseBasicParsing should behave exactly as before. If you configured IE mode, a site on your Enterprise Mode Site List should reload with the Internet Explorer icon shown in the Edge address bar.

Normal result: The feature reports State : Disabled in both PowerShell and DISM, iexplore no longer launches, IE is absent from Start and Programs and Features, HTML files open in Edge, and IIS/web services and IE-mode sites continue to work normally.

Abnormal result: The feature still shows State : Enabled (or Enable Pending / Disable Pending, meaning the reboot has not completed), iexplore still launches, IE remains listed in Programs and Features, HTML files fail to open or prompt for a browser, or a critical web app breaks because it required IE and no matching IE-mode Site List entry exists.

IE feature disabled (PowerShell)

FeatureName : Internet-Explorer-Optional-amd64 State : Disabled

Expected output confirming the optional feature is off after the reboot.

Reboot still pending

State : Disable Pending

The disable was queued but the server has not yet been restarted; complete the reboot, then re-check.

DISM confirmation

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

Cross-checks the feature state from the DISM command line, useful in automation logs.

IE mode active in Edge

Address bar shows the Internet Explorer icon on legacy-app.company.com

Indicates the Enterprise Mode Site List entry is applied and the legacy app is rendering in IE mode.

Troubleshooting

Legacy web application fails to load or shows a blank page after Internet Explorer is removed

Warning

Cause: The app depends on the Trident (MSHTML) rendering engine or ActiveX controls that only IE11 provided, and it has not been added to Edge IE mode.

Enable IE mode in Edge at edge://settings/defaultBrowser by setting Allow sites to be reloaded in Internet Explorer mode to Allow, then add the app's URL to an Enterprise Mode Site List XML with <compat-mode>IE11</compat-mode> and <open-in>IE11</open-in>, and deploy it via Group Policy. Confirm the Internet Explorer icon appears in the address bar when you open the site.

Related step 6: Configure Edge IE mode for legacy applications

DISM or Disable-WindowsOptionalFeature reports that the feature cannot be found or is not present

Warning

Cause: The feature name was mistyped, or you are on an edition/architecture where the feature identifier differs from Internet-Explorer-Optional-amd64.

List the exact available feature names first with Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Internet-Explorer*"} and use the returned FeatureName verbatim in your DISM or PowerShell command. Confirm the command prompt is elevated.

Related step 4: Method 2 - Remove IE using DISM

A management console or shortcut still tries to launch Internet Explorer after removal

Note

Cause: The application hardcodes iexplore.exe or an HTML file association still points to IE, so it errors out because the executable is gone.

Reconfigure the default web browser and HTML file associations to Microsoft Edge under Settings > Apps > Default apps, and add the offending application's URL to the Edge Enterprise Mode Site List so it opens in IE mode instead of the removed IE binary.

Related step 7: Update default browser and file associations

Get-WindowsOptionalFeature still shows State: Enabled after running the disable command

Note

Cause: The required restart has not been completed, so the feature change is pending and not yet applied.

Restart the server to finish applying the change, then re-run Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -eq "Internet-Explorer-Optional-amd64"} and confirm the State field now reads Disabled. If you used -NoRestart or /quiet, schedule and complete the reboot before verifying.

Related step 8: Verify complete removal and test functionality

Removing Internet Explorer leaves the server without any working browser

Critical

Cause: Microsoft Edge was not installed or confirmed before IE was disabled, which can happen on older or minimally configured server images.

Install Edge from the Microsoft Edge Enterprise MSI with MicrosoftEdgeEnterpriseX64.msi /quiet /norestart, then launch it by running msedge from the Run dialog to confirm it works. Always verify Edge is present before disabling IE.

Related step 2: Install or confirm Microsoft Edge as the replacement browser

Frequently asked questions

Can I reinstall Internet Explorer on Windows Server if a legacy app breaks?

Yes. Because IE11 is an optional feature, you can re-enable it with dism /online /enable-feature /featurename:Internet-Explorer-Optional-amd64 or Enable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 -Online, followed by a restart. In most cases, adding the app to Edge IE mode is a better long-term fix than reinstalling the unsupported browser.

Does removing Internet Explorer affect Microsoft Edge IE mode?

No. Edge IE mode uses the Trident engine components that remain on the system and does not depend on the standalone Internet Explorer 11 application. Disabling the IE optional feature still lets you reload legacy sites in IE mode within Edge once you have configured it.

Which Windows Server versions still include Internet Explorer 11?

Internet Explorer 11 ships as an optional feature on Windows Server 2019, 2022, and 2025. On these editions it is available but can be disabled or removed, and Microsoft recommends Edge as the replacement since IE11 reached end-of-support on June 15, 2022.

Is it safe to disable Internet Explorer on a production Windows Server?

It is generally safe as long as Microsoft Edge is installed as the replacement and any IE-dependent applications are moved to Edge IE mode first. Because IE11 is unsupported, removing it reduces your attack surface, but you should document current browser configuration and test critical apps after the change.

Do I need to restart the server after disabling the IE optional feature?

Yes. Disabling the Internet Explorer optional feature requires a restart to fully apply, whether you use the Settings app, DISM, or PowerShell. You can defer the reboot with the /quiet flag in DISM or -NoRestart in PowerShell, but the feature will not show State: Disabled until the server has restarted.

What is the difference between using DISM and PowerShell to remove IE?

Both disable the same Internet-Explorer-Optional-amd64 feature and produce the same result. DISM uses dism /online /disable-feature, while PowerShell uses Disable-WindowsOptionalFeature -Online, which integrates more easily into scripts and supports remote execution across multiple servers via Invoke-Command.

Conclusion

You verified whether Internet Explorer 11 was enabled, confirmed Microsoft Edge was installed, and then removed the IE optional feature using one of three methods - the Settings app, DISM, or PowerShell. You also configured Edge IE mode with an Enterprise Mode Site List, updated default browser and file associations, and verified that IE is gone while IIS and web services still function.

Internet Explorer 11 is an optional feature on Windows Server 2019-2025 that you can safely disable once Edge and IE mode are in place to keep legacy apps working.

Main path
dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64
Reader actions
Was this helpful?
Rate this articleRate
24 readers viewed this article

Reader reviews

Rate this articleBe the first to rate
No written reviews yetRate the article above, or be the first to share your experience.