Windows Server removed features
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit f0e2eaa · +1 −1 lines · also on GitHub
⋯ 99 unchanged lines
100100
|--|--|
101101
| Data Encryption Standard (DES) | DES, the symmetric-key block encryption cipher, isn't considered secure against modern cryptographic attacks. It's replaced by more robust encryption algorithms. DES was disabled starting with Windows Server 2008 R2 and is removed from Windows Server 2025 and later releases. |
102102
| IIS 6 Management Console (Web-Lgcy-Mgmt-Console) | The console is removed after being no longer developed in Windows Server 2019. You should also start migrating from IIS 6.0 or earlier versions to the latest version of IIS, which is always available in the most recent release of Windows Server. |
103
−| Internet Explorer | The Internet Explorer 11 desktop application is <a href="https://aka.ms/IEJune15Blog">retired and out of support</a> as of June 15, 2022. The standalone Internet Explorer application is removed from Windows Server 2025.<br><br>**IE mode in Microsoft Edge**: You can still access older, legacy sites that require Internet Explorer with <a href="https://aka.ms/IEmodewebsite">Internet Explorer mode in Microsoft Edge</a>. IE mode in Microsoft Edge remains supported for the duration of Windows Server 2025 support and continues to receive security updates.<br><br>**Disabling IE mode**: If your organization requires IE mode to be disabled for compliance purposes, you can disable it via Group Policy. For detailed guidance, see <a href="https://learn.microsoft.com/deployedge/edge-ie-mode-policies">Configure IE mode Policies</a>.<br><br>**Optional feature**: The Windows optional feature `Internet-Explorer-Optional-amd64` no longer exists in Windows Server 2025. DISM and PowerShell commands to remove this feature are not applicable to Windows Server 2025.<br><br>**Residual artifacts**: Some Internet Explorer components, such as `iexplore.exe` stubs and COM automation objects, remain in Windows Server 2025 for compatibility purposes. Attempting to launch `iexplore.exe` redirects to Microsoft Edge. These components are part of the operating system and shouldn't be manually removed.<br><br>**FAQ**:<br>- *Why is `iexplore.exe` present in Windows Server 2025?* Residual IE components remain for backward compatibility with scripts and applications that reference IE paths or COM objects. These components redirect to Microsoft Edge when invoked.<br>- *How do I validate that standalone Internet Explorer can't be used?* Run `dism /online /get-features \| findstr /i "Internet-Explorer"` to confirm the `Internet-Explorer-Optional-amd64` feature isn't listed. Attempting to launch `iexplore.exe` will redirect to Microsoft Edge.<br>- *How do I ensure IE mode is disabled f…
103
+| Internet Explorer | The Internet Explorer 11 desktop application is <a href="https://aka.ms/IEJune15Blog">retired and out of support</a> as of June 15, 2022. The standalone Internet Explorer application is removed from Windows Server 2025.<br><br>**IE mode in Microsoft Edge**: You can still access older, legacy sites that require Internet Explorer with <a href="https://aka.ms/IEmodewebsite">Internet Explorer mode in Microsoft Edge</a>. IE mode in Microsoft Edge remains supported for the duration of Windows Server 2025 support and continues to receive security updates.<br><br>**Disabling IE mode**: If your organization requires IE mode to be disabled for compliance purposes, you can disable it via Group Policy. For detailed guidance, see <a href="https://learn.microsoft.com/deployedge/edge-ie-mode-policies">Configure IE mode Policies</a>.<br><br>**Optional feature**: The Windows optional feature `Internet-Explorer-Optional-amd64` no longer exists in Windows Server 2025. DISM and PowerShell commands to remove this feature are not applicable to Windows Server 2025.<br><br>**Residual artifacts**: Some Internet Explorer components, such as `iexplore.exe` stubs and COM automation objects, remain in Windows Server 2025 for compatibility purposes. Attempting to launch `iexplore.exe` redirects to Microsoft Edge. These components are part of the operating system and shouldn't be manually removed.<br><br>**FAQ**:<br>- *Why is `iexplore.exe` present in Windows Server 2025?* Residual IE components remain for backward compatibility with scripts and applications that reference IE paths or COM objects. These components redirect to Microsoft Edge when invoked.<br>- *How do I validate that standalone Internet Explorer can't be used?* Run `dism /online /get-features | findstr /i "Internet-Explorer"` to confirm the `Internet-Explorer-Optional-amd64` feature isn't listed. Attempting to launch `iexplore.exe` will redirect to Microsoft Edge.<br>- *How do I ensure IE mode is disabled fo…
104104
| NTLMv1 | Replace calls to NTLM with calls to [Negotiate](/windows/win32/secauthn/microsoft-negotiate), which tries to authenticate with Kerberos and only falls back to NTLM when necessary. For more information, see [The evolution of Windows authentication](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/the-evolution-of-windows-authentication/ba-p/3926848). |
105105
| Windows PowerShell 2.0 | Starting with the [September 2025 update](https://support.microsoft.com/en-us/topic/september-9-2025-kb5065426-update-for-windows-server-2025-os-build-26100-6584-6a59dc6a-1ff2-48f4-b375-81e93deee5dd), Windows Server 2025 no longer includes Windows PowerShell 2.0. If Windows PowerShell 2.0 was installed before the September update, you can no longer use it. Windows PowerShell 2.0 applications and components should be migrated to PowerShell 5.0 or later. To learn more about the deprecation, see [Windows PowerShell 2.0 Deprecation](https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/). |
106106
| SMTP Server | Because SMTP Server features were removed from Windows Server 2025, there's no replacement within the operating system. Consider using Exchange Server or a non-Microsoft SMTP server as an alternative. To learn more about enabling SMTP connection in Exchange Server, see [Receive connectors in Exchange Server](/exchange/mail-flow/connectors/receive-connectors). |
⋯ 36 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 07:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.