Windows Server removed features

This page's changes and edits · All guidance changes

Microsoft's edit · 3 Jul 2025 00:45 UTC

update

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit df6eb88 · +21 ~~−21~~ lines · also on GitHub

11 ---

2 −title: Features removed or no longer developed in Windows Server

2 +title: Features Removed or No Longer Developed in Windows Server

33 description: Learn about the features and functionalities removed or no longer developed in Windows Server.

4 −ms.topic: article

4 +ms.topic: concept-article

55 author: xelu86

66 ms.author: alalve

7 −ms.date: 04/28/2025

7 +ms.date: 07/02/2025

88 ---

1010 # Features removed or no longer developed in Windows Server

1111

12 −Each release of Windows Server brings new features and improvements, while sometimes removing older ones to make room for better alternatives. This article details the features and functionalities removed or deprecated in Windows Server.

12 +Each release of Windows Server brings new features and improvements. Sometimes older features are removed to make room for better alternatives. This article details the features and functionalities removed or deprecated in Windows Server.

1313

1414 > [!TIP]

1515 > You can get early access to Windows Server builds by joining the [Windows Insider Program for Business](https://insider.windows.com/for-business), which is a great way to test feature changes.

1616

1717 > [!NOTE]

18 −> Windows Server Long-Term Servicing Channel (LTSC) releases have a Fixed Policy Lifecycle which includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see:

18 +> Windows Server long-term servicing channel (LTSC) releases have a Fixed Lifecycle Policy that includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see:

1919 >

2020 > - [Fixed Lifecycle Policy](/lifecycle/policies/fixed)

2121 > - [Lifecycle Terms and Definitions](/lifecycle/definitions)

⋯ 2 unchanged lines

2424

2525 ## Features no longer in development

2626

27 −We're no longer actively developing these features and may remove them from a future update. Some features were replaced with other features or functionality, while others are now available from different sources. Deprecation means a feature, functionality, or service is no longer in active development. A deprecated feature may be removed in future releases. A deprecated component still ships in Windows Server, is supported for production deployments, and continues to receive security and quality updates as per the product lifecycle.

27 +We're no longer actively developing these features and might remove them from a future update. Some features were replaced with other features or functionality. Others are now available from different sources. *Deprecation* means that a feature, functionality, or service is no longer in active development. A deprecated feature might be removed in future releases. A deprecated component still ships in Windows Server, is supported for production deployments, and continues to receive security and quality updates per the product lifecycle.

2828

2929 # [Windows Server 2025](#tab/ws25)

3030

3131 | Feature | Explanation |

3232 |--|--|

33 −| Computer Browser | The Computer Browser driver and service are deprecated. The browser (browser protocol and service) is a dated and insecure device location protocol. This protocol, service, and driver were first disabled by default in Windows 10 with the removal of the SMB1 service. For more information on Computer Browser, see [MS-BRWS Common Internet File System](/openspecs/windows_protocols/ms-brws/3cfbad92-09b3-4abc-808f-c6f6347d5677). |

34 −| Failover Clustering Cluster Sets | Failover Clustering Cluster Sets feature is no longer in active feature development and is deprecated. |

33 +| Computer Browser | The Computer Browser driver and service are deprecated. The browser (browser protocol and service) is a dated and insecure device location protocol. This protocol, service, and driver were first disabled by default in Windows 10, with the removal of the SMB1 service. For more information on Computer Browser, see [MS-BRWS Common Internet File System](/openspecs/windows_protocols/ms-brws/3cfbad92-09b3-4abc-808f-c6f6347d5677). |

34 +| Failover Clustering Cluster Sets |The Failover Clustering Cluster Sets feature is no longer in active feature development and is deprecated. |

3535 | Network Load Balancing (NLB) | NLB is no longer in active feature development and is deprecated. Consider using a Software Load Balancer (SLB) as an alternative. To learn more about SLB, see [What is Software Load Balancer (SLB) for SDN?](/azure/azure-local/concepts/software-load-balancer?context=/windows-server/context/windows-server-edge-networking) |

36 −| NTLM | [NTLMv1](/windows/win32/secauthn/microsoft-ntlm) is removed. LANMAN and NTLMv2 are no longer under active feature development and are deprecated. NTLMv2 will continue to work but will be removed from Windows Server in a future release. Replace calls to NTLM to calls to [Negotiate](/windows/win32/secauthn/microsoft-negotiate), which try to authenticate with Kerberos and only fall 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). |

36 +| NTLM | [NTLMv1](/windows/win32/secauthn/microsoft-ntlm) is removed. LANMAN and NTLMv2 are no longer under active feature development and are deprecated. NTLMv2 will continue to work but will be removed from Windows Server in a future release. Replace calls to NTLM with calls to [Negotiate](/windows/win32/secauthn/microsoft-negotiate), which tries to authenticate with Kerberos and only fall 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). |

3737 | Remote Mailslots | Remote Mailslots are deprecated. The Remote Mailslot protocol, which was initially introduced in MS DOS, is a dated and simple IPC method that is both unreliable and insecure. This protocol was first disabled by default in [Windows 11 Insider Preview Build](https://blogs.windows.com/windows-insider/2023/03/08/announcing-windows-11-insider-preview-build-25314/). For more information on Remote Mailslots, see [About Mailslots](/windows/win32/ipc/about-mailslots) and [[MS-MAIL]: Remote Mailslot Protocol](/openspecs/windows_protocols/ms-mail/8ea19aa4-6e5a-4aed-b628-0b5cd75a1ab9). |

3838 | TLS 1.0 TLS 1.1 | TLS versions 1.0 and 1.1 are deprecated per internet standards and regulatory bodies due to security concerns mentioned in [RFC 8996](https://www.rfc-editor.org/rfc/rfc8996). These versions are disabled by default in Windows Server 2025. For more information on TLS deprecation, see [TLS 1.0 and TLS 1.1 deprecation in Windows](/windows/win32/secauthn/tls-10-11-deprecation-in-windows). |

3939 | WebDAV Redirector service | The WebDAV Redirector service is deprecated. The service isn't installed by default in Windows Server. For more information on the WebDAV Redirector service, see [WebDAV - Win32 apps](/windows/win32/webdav/webdav-portal). |

40 −| Windows Internal Database (WID) | WID is used by several roles, including ADFS, ADRMS, IPAM, RD Connection Broker, and WSUS. Consider using a free or full version of SQL Server for these roles. WID will be removed from Windows in a future release. To learn more about the different types of SQL Server available, see [SQL Server editions](/sql/sql-server/editions-and-components-of-sql-server-2022). |

41 −| Windows Management Instrumentation Command line (WMIC) | Beginning with Windows Server 2025, WMIC is available as a feature on demand (FoD) which can be added with the `DISM /Add-Capability` command. It will be removed from Windows in a future release. [PowerShell for WMI](/powershell/scripting/learn/ps101/07-working-with-wmi) replaces the WMIC tool. Use PowerShell or programmatically query WMI as a replacement for WMIC. To learn more about WMIC depreciation, see [WMI command line (WMIC) utility deprecation: Next steps](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/wmi-command-line-wmic-utility-deprecation-next-steps/ba-p/4039242) |

42 −| Windows PowerShell 2.0 Engine | The Windows PowerShell 2.0 Engine is deprecated and isn't installed by default. Windows PowerShell 2.0 applications, and components should be migrated to PowerShell 5.0+. To learn more about the deprecation, see [Windows PowerShell 2.0 Deprecation](https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/). |

43 −| VBScript | VBScript is available as a feature on demand (FoD) and preinstalled in Windows Server 2025, before its removal from the operating system in a later release. As a replacement for VBScript, use PowerShell for automating tasks, custom actions, or scripts. To learn more about migrating to PowerShell, see [The VBScript-to-Windows PowerShell Conversion Guide](/previous-versions/windows/it-pro/windows-powershell-1.0/ee221101(v=msdn.10)). If you're using VBScript within your webpage, functionality is currently limited to browsers predating Internet Explorer 11. We recommend migrating your webpages to JavaScript, which provides cross-browser compatibility and modern browser support. |

44 −| Windows Server Update Services (WSUS) | WSUS is no longer actively developed, all the existing capabilities and content continue to be available for your deployments. |

40 +| Windows Internal Database (WID) | WID is used by several roles, including AD FS, AD RMS, IPAM, RD Connection Broker, and WSUS. Consider using a free or full version of SQL Server for these roles. WID will be removed from Windows in a future release. To learn more, see [SQL Server editions](/sql/sql-server/editions-and-components-of-sql-server-2022). |

41 +| Windows Management Instrumentation Command-line (WMIC) | Beginning with Windows Server 2025, WMIC is available as a Feature on Demand (FOD). It can be added with the `DISM /Add-Capability` command. It will be removed from Windows in a future release. [PowerShell for WMI](/powershell/scripting/learn/ps101/07-working-with-wmi) replaces the WMIC tool. Use PowerShell or programmatically query WMI as a replacement for WMIC. To learn more about WMIC depreciation, see [WMI command line (WMIC) utility deprecation: Next steps](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/wmi-command-line-wmic-utility-deprecation-next-steps/ba-p/4039242) |

42 +| Windows PowerShell 2.0 | Windows PowerShell 2.0 is deprecated and isn't installed by default. 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/). |

43 +| VBScript | VBScript is available as an FOD and preinstalled in Windows Server 2025, before its removal from the operating system in a later release. As a replacement for VBScript, use PowerShell for automating tasks, custom actions, or scripts. To learn more about migrating to PowerShell, see [The VBScript-to-Windows PowerShell Conversion Guide](/previous-versions/windows/it-pro/windows-powershell-1.0/ee221101(v=msdn.10)). If you're using VBScript within your webpage, functionality is currently limited to browsers predating Internet Explorer 11. We recommend migrating your webpages to JavaScript, which provides cross-browser compatibility and modern browser support. |

44 +| Windows Server Update Services (WSUS) | WSUS is no longer actively developed. All the existing capabilities and content continue to be available for your deployments. |

4545

4646 # [Windows Server 2022](#tab/ws22)

4747

4848 | Feature | Explanation |

4949 |--|--|

50 −| Guarded Fabric and Shielded VMs | Windows Server and Azure Local are aligning with Azure to take advantage of continuing enhancements to [Azure Confidential Computing](/azure/confidential-computing/) and [Azure Security Center](/azure/security-center/). Having this alignment translates to more cloud security offerings being extended to customer data centers on-premises. Microsoft continues to provide support for these features, but there's no further development on client versions of Windows as the Shielded VM RSAT feature is removed. |

51 −| Hyper-V vSwitch on LBFO | The Hyper-V vSwitch no longer has the capability to be bound to an LBFO team. Instead, it must be bound via [Switch Embedded Teaming (SET)](/azure/azure-local/concepts/host-network-requirements#switch-embedded-teaming-set). This change only applies to Hyper-V. LBFO is still fully supported for other non Hyper-V scenarios. |

52 −| Launching SConfig from a command prompt (CMD) | Starting with Windows Server 2022, `SConfig` is launched **by default** when you sign into a server running Server Core installation option. Moreover, PowerShell is now the default shell on Server Core. If you exit `SConfig`, you get to a regular interactive PowerShell window. Similarly, you can opt out from SConfig autolaunch. In this case, a PowerShell window pops up at sign-in. In either scenario, you can launch SConfig from PowerShell by running `SConfig`. |

50 +| Guarded Fabric and Shielded VMs | Windows Server and Azure Local are aligning with Azure to take advantage of continuing enhancements to [Azure Confidential Computing](/azure/confidential-computing/) and [Azure Security Center](/azure/security-center/). This alignment translates to more cloud security offerings being extended to customer datacenters on-premises. Microsoft continues to provide support for these features, but there's no further development on client versions of Windows as the Shielded VM RSAT feature is removed. |

51 +| Hyper-V Virtual Switch on LBFO | The Hyper-V Virtual Switch no longer has the capability to be bound to an LBFO team. Instead, it must be bound via [Switch Embedded Teaming (SET)](/azure/azure-local/concepts/host-network-requirements#switch-embedded-teaming-set). This change only applies to Hyper-V. LBFO is still fully supported for other non-Hyper-V scenarios. |

52 +| Launching SConfig from a command prompt | Starting with Windows Server 2022, `SConfig` is launched by default when you sign into a server running the Server Core installation option. Moreover, PowerShell is now the default shell on Server Core. If you exit `SConfig`, you get to a regular interactive PowerShell window. Similarly, you can opt out from SConfig autolaunch. In this case, a PowerShell window pops up at sign-in. In either scenario, you can launch SConfig from PowerShell by running `SConfig`. |

5353 | New EKUs for VBS enclaves | VBS enclaves are supported on Windows Server 2025 and later. *Existing* enclaves with the EKU 1.3.6.1.4.1.311.76.57.1.15 signature are still supported on Windows Server 2022 as long as they remain unchanged and don't require re-signing. |

54 −| Windows Deployment Services (WDS) boot.wim image deployment | The operating system deployment functionality of WDS is being partially deprecated. Workflows that rely on `boot.wim` from Windows Server 2022 installation media shows a non-blocking deprecation notice, but the workflows aren't impacted. Windows 11 workflows and workflows for future versions of Windows Server that rely on `boot.wim` from installation media is blocked. Alternatives to WDS, such as [Microsoft Endpoint Configuration Manager](/mem/configmgr/) or the [Microsoft Deployment Toolkit](/windows/deployment/deploy-windows-mdt/get-started-with-the-microsoft-deployment-toolkit) (MDT), provide a better, more flexible, and feature-rich experience for deploying Windows images. You're advised to move to one of these solutions instead. WDS PXE boot isn't affected. You can still use WDS to PXE boot devices to custom boot images. You can also still [run setup from a network share](/windows-hardware/manufacture/desktop/deploy-a-custom-image). Workflows that use custom `boot.wim` images, such as with Configuration Manager or MDT, aren't impacted. |

54 +| Windows Deployment Services (WDS) boot.wim image deployment | The operating system deployment functionality of WDS is being partially deprecated. Workflows that rely on `boot.wim` from Windows Server 2022 installation media show a non-blocking deprecation notice, but the workflows aren't impacted. Windows 11 workflows and workflows for future versions of Windows Server that rely on `boot.wim` from installation media are blocked. Alternatives to WDS, such as [Microsoft Endpoint Configuration Manager](/mem/configmgr/) or the [Microsoft Deployment Toolkit](/windows/deployment/deploy-windows-mdt/get-started-with-the-microsoft-deployment-toolkit) (MDT), provide a better, more flexible, and feature-rich experience for deploying Windows images. We recommend that you use one of these solutions instead. WDS PXE boot isn't affected. You can still use WDS to PXE-boot devices to custom boot images. You can also still [run setup from a network share](/windows-hardware/manufacture/desktop/deploy-a-custom-image). Workflows that use custom `boot.wim` images, such as with Configuration Manager or MDT, aren't impacted. |

5555 | Windows Internet Name Service (WINS) | WINS is a legacy computer name registration and resolution service. You should replace WINS with Domain Name System (DNS). For more information, see [Windows Internet Name Service (WINS)](../networking/technologies/wins/wins-top.md). |

56 −| XDDM-based remote display driver | Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote display indirect display driver, see [Updates for IddCx versions 1.4 and later](/windows-hardware/drivers/display/iddcx1.4-updates). |

56 +| XDDM-based remote display driver | Starting with this release, Remote Desktop Services uses a Windows Display Driver Model (WDDM) based indirect display driver (IDD) for a single-session remote desktop. Support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent software vendors that use XDDM-based remote display drivers should plan a migration to the WDDM driver model. For more information on implementing remote indirect display drivers, see [Updates for IddCx versions 1.4 and later](/windows-hardware/drivers/display/iddcx1.4-updates). |

5757

5858 # [Windows Server 2019](#tab/ws19)

5959

6060 | Feature | Explanation |

6161 |--|--|

62 −| Host Guardian Service Active Directory attestation mode | We're no longer developing Host Guardian Service Active Directory attestation mode. Instead, a new attestation mode is added, [host key attestation](../security/guarded-fabric-shielded-vm/guarded-fabric-create-host-key.md). Host key attestation is simpler and equally as compatible as Active Directory based attestation. This new mode provides equivalent functionality with a setup experience, simpler management, and fewer infrastructure dependencies than the Active Directory attestation. Host key attestation has no extra hardware requirements beyond what Active Directory attestation required, so all existing systems remain compatible with the new mode. To learn more about your attestation options, see [Deploy guarded hosts](../security/guarded-fabric-shielded-vm/guarded-fabric-configure-hgs-with-authorized-hyper-v-hosts.md). |

63 −| IIS Digest Authentication | This authentication method is planned for replacement. Instead, you should start using other authentication methods such as Client Certificate Mapping. To learn more, see [Configuring One-to-One Client Certificate Mappings](/iis/manage/configuring-security/configuring-one-to-one-client-certificate-mappings) and [Application Settings](/iis-administration/configuration/appsettings.json). |

62 +| Host Guardian Service Active Directory attestation mode | We're no longer developing Host Guardian Service Active Directory attestation mode. Instead, a new attestation mode is added, [host key attestation](../security/guarded-fabric-shielded-vm/guarded-fabric-create-host-key.md). Host key attestation is simpler and as compatible as Active Directory-based attestation. This new mode provides equivalent functionality with a setup experience, simpler management, and fewer infrastructure dependencies than the Active Directory attestation. Host key attestation has no extra hardware requirements beyond what Active Directory attestation required, so all existing systems remain compatible with the new mode. To learn more about your attestation options, see [Deploy guarded hosts](../security/guarded-fabric-shielded-vm/guarded-fabric-configure-hgs-with-authorized-hyper-v-hosts.md). |

63 +| IIS Digest Authentication | This authentication method will be replaced. Instead, you should start using other authentication methods such as Client Certificate Mapping. To learn more, see [Configuring One-to-One Client Certificate Mappings](/iis/manage/configuring-security/configuring-one-to-one-client-certificate-mappings) and [Application Settings](/iis-administration/configuration/appsettings.json). |

6464 | IIS 6 Management compatibility | Specific features being considered for replacement are: <li>IIS 6 Metabase Compatibility (Web-Metabase)</li><li>IIS 6 Management Console (Web-Lgcy-Mgmt-Console)</li><li>IIS 6 Scripting Tools (Web-Lgcy-Scripting)</li><li>IIS 6 WMI Compatibility (Web-WMI)</li> IIS 6 Metabase Compatibility acts as an emulation layer between IIS 6-based metabase scripts and the file-based configuration used by IIS 7 or newer versions. You should start migrating management scripts to target IIS file-based configuration directly, by using tools such as the `Microsoft.Web.Administration` namespace. You should also start migration from IIS 6.0 or earlier versions, and move to the latest version of IIS, which is always available in the most recent release of Windows Server. |

6565 | Internet Storage Name Service (iSNS) | The Server Message Block (SMB) feature offers essentially the same functionality with more features. See [Server Message Block Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831795(v=ws.11)) for background information on this feature. |

6666 | IPv4/6 Transition Technologies | 6to4 is disabled by default since Windows 10, version 1607 (the Anniversary Update). ISATAP is disabled by default since Windows 10, version 1703 (the Creators Update). Direct Tunnels is disabled by default. Use native IPv6 support instead. |

⋯ 74 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.