title	Features Removed or No Longer Developed in Windows Server
description	Learn about the features and functionalities removed or no longer developed in Windows Server.
ms.topic	concept-article
author	robinharwood
ms.author	roharwoo
ms.date	09/24/2025

Features removed or no longer developed in Windows Server

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.

Tip

You can get early access to Windows Server builds by joining the Windows Insider Program for Windows Server, which is a great way to test feature changes.

Note

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:

This list is subject to change and might not include every affected feature or functionality.

Features no longer in development

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.

Windows Server 2025

Feature	Explanation
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 the CIFS Browser Protocol used by the Computer Browser drive and service, see MS-BRWS Common Internet File System.
Failover Clustering Cluster Sets	The Failover Clustering Cluster Sets feature is no longer in active feature development and is deprecated.
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?
NTLM	NTLMv1 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, which tries to authenticate with Kerberos and only fall back to NTLM when necessary. For more information, see The evolution of Windows authentication.
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 25314. For more information on Remote Mailslots, see About Mailslots and [MS-MAIL]: Remote Mailslot Protocol.
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. 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.
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 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.
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 replaces the WMIC tool. Use PowerShell or programmatically query WMI as a replacement for WMIC. To learn more about WMIC deprecation, see WMI command line (WMIC) utility deprecation: Next steps.
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. 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.
Windows Server Update Services (WSUS)	WSUS is no longer actively developed. All the existing capabilities and content continue to be available for your deployments.
Rivest Cipher 4 (RC4) usage in Kerberos	RC4 usage in the Kerberos authentication protocol is deprecated. RC4 is a weak algorithm that can be abused for stealing credentials. Stronger algorithms, like AES-SHA1, should be used instead. For more information, see Detect and Remediate RC4 Usage in Kerberos.

Windows Server 2022

Feature	Explanation
Guarded Fabric and Shielded VMs	Windows Server and Azure Local are aligning with Azure to take advantage of continuing enhancements to Azure confidential computing and 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.
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). This change only applies to Hyper-V. LBFO is still fully supported for other non-Hyper-V scenarios.
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`.
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.
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 nonblocking 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 Configuration Manager, provide a better, more flexible, and feature-rich experience for deploying Windows images. 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. Workflows that use custom `boot.wim` images, such as with Configuration Manager or MDT, aren't impacted.
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).
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 Server 2019

Feature	Explanation
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. 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.
IIS Digest Authentication	This authentication method will be replaced. You should start using other authentication methods, like Client Certificate Mapping. To learn more, see Configuring One-to-One Client Certificate Mappings and Application Settings.
IIS 6 Management compatibility	Specific features being considered for replacement are: IIS 6 Metabase Compatibility (Web-Metabase) IIS 6 Management Console (Web-Lgcy-Mgmt-Console) IIS 6 Scripting Tools (Web-Lgcy-Scripting) IIS 6 WMI Compatibility (Web-WMI) 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 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.
Internet Storage Name Service (iSNS)	The Server Message Block (SMB) feature offers essentially the same functionality with more features. See Server Message Block Overview for background information on this feature.
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.
Key Storage Drive in Hyper-V	We're no longer working on the Key Storage Drive feature in Hyper-V. If you use generation 1 VMs, check out Generation 1 VM Virtualization Security for information about options. If you're creating new VMs, use generation 2 VMs with TPM devices for a more secure solution.
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 2019 as long as they remain unchanged and don't require re-signing.
OneSync service	The OneSync service synchronizes data for the Mail, Calendar, and People apps. A sync engine to the Outlook app that provides the same synchronization was added.
Remote Differential Compression API support	Remote Differential Compression API support enabled synchronizing data with a remote source by using compression technologies, which minimized the amount of data sent across the network.
RSA/AES Encryption for IIS	We're considering replacing this encryption method because the superior Cryptography API: Next Generation (CNG) method is already available. To learn more, see About CNG.
Storage Spaces in a Shared configuration using a SAS fabric	Deploy Storage Spaces Direct instead. Storage Spaces Direct supports the use of HLK-certified SAS enclosures, but in a nonshared configuration, as described in the Storage Spaces Direct hardware requirements.
Trusted Platform Module (TPM) management console	The information previously available in the TPM management console is now available on the Device security page in Windows Security settings.
WFP lightweight filter switch extension	The WFP lightweight filter switch extension enables developers to build simple network packet filtering extensions for the Hyper-V Virtual Switch. You can achieve the same functionality by creating a full filtering extension. Therefore, we're removing this extension in the future.
Windows PowerShell 2.0	Migrate to Windows PowerShell 5.0 or later for the best features and performance. For more information, see PowerShell Documentation.
Windows Server Essentials Experience	We're no longer developing the Essentials Experience role for the Windows Server Standard or Windows Server Datacenter SKUs. If you need an easy-to-use server solution for small-to-medium businesses, check out Microsoft 365 for business, or use Windows Server 2016 Essentials.
MultiPoint Services	We're no longer developing the MultiPoint Services role as part of Windows Server. MultiPoint Connector services are available through Features on Demand for both Windows Server and Windows 10. You can use Remote Desktop Services, in particular the Remote Desktop Services Session Host, to provide RDP connectivity.
Offline symbol packages (Debug symbol MSIs)	We're no longer making the symbol packages available as a downloadable MSI. Instead, Microsoft symbol server is becoming an Azure-based symbol store. If you need the Windows symbols, connect to the Microsoft symbol server to cache your symbols locally, or use a manifest file with SymChk.exe on a computer with internet access.
Software Restriction Policies in Group Policy	Instead of using Software Restriction Policies through Group Policy, you can use AppLocker or Application Control for Windows. You can use AppLocker and Windows Defender Application Control to manage which apps users can access and what code can run in the kernel.

Windows Server 2016

Feature	Explanation
Configuration tools	`scregedit.exe` is deprecated. If you have scripts that depend on `scregedit.exe`, adjust them to use `reg.exe` or PowerShell methods.
NetCfg custom APIs	Installation of PrintProvider, NetClient, and ISDN using NetCfg custom APIs is deprecated.
Remote management	`WinRM.vbs` is deprecated. Instead, use functionality in the WinRM provider of PowerShell.
Sconfig.exe	Use Sconfig.cmd instead.
SMB 2 and later over NetBT	SMB 2 and later over NetBT is deprecated. Instead, implement SMB over TCP or RDMA.