Windows Server removed features

This page's changes and edits · All guidance changes

Microsoft's edit · 3 Jul 2025 19:16 UTC

update

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 210fc5a · +5 −5 lines · also on GitHub

⋯ 37 unchanged lines

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). |

4040 | 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) |

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). |

4242 | 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/). |

4343 | 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. |

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

⋯ 2 unchanged lines

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/). 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. |

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

5151 | 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. |

5252 | 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 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 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. |

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 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](/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). |

5656 | 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

⋯ 16 unchanged lines

7474 | 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](/windows-hardware/drivers/network/using-virtual-switch-filtering). You can achieve the same functionality by creating a full filtering extension. Therefore, we're removing this extension in the future. |

7575 | Windows PowerShell 2.0 | Migrate to Windows PowerShell 5.0 or later for the best features and performance. For more information, see [PowerShell Documentation](/powershell/index?view=powershell-5.1&preserve-view=true). |

7676 | 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](https://www.microsoft.com/microsoft-365/business), or use [Windows Server 2016 Essentials](/windows-server-essentials/get-started/get-started). |

77 −| [MultiPoint Services](../remote/multipoint-services/multipoint-services.md) | We're no longer developing the MultiPoint Services role as part of Windows Server. MultiPoint Connector services are available through [Feature on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) for both Windows Server and Windows 10. You can use [Remote Desktop Services](../remote/remote-desktop-services/remote-desktop-services-overview.md), in particular the Remote Desktop Services Session Host, to provide RDP connectivity. |

77 +| [MultiPoint Services](../remote/multipoint-services/multipoint-services.md) | We're no longer developing the MultiPoint Services role as part of Windows Server. MultiPoint Connector services are available through [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) for both Windows Server and Windows 10. You can use [Remote Desktop Services](../remote/remote-desktop-services/remote-desktop-services-overview.md), in particular the Remote Desktop Services Session Host, to provide RDP connectivity. |

7878 | [Offline symbol packages](/windows-hardware/drivers/debugger/debugger-download-symbols) (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](/archive/blogs/windbg/update-on-microsofts-symbol-server). 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. |

7979 | [Software Restriction Policies](../identity/software-restriction-policies/software-restriction-policies.md) in Group Policy | Instead of using Software Restriction Policies through Group Policy, you can use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) or [Application Control for Windows](/windows/security/threat-protection/windows-defender-application-control). You can use AppLocker and Windows Defender Application Control to manage which apps users can access and what code can run in the kernel. |

8080

⋯ 35 unchanged lines

116116 |--|--|

117117 | Business Scanning/ Distributed Scan Management (DSM) | We're removing this secure scanning and scanner management capability. There are no devices that support this feature. |

118118 | [File Replication Service](https://support.microsoft.com/help/4025991/windows-server-version-1709-no-longer-supports-frs) (FRS) | Distributed File System (DFS) replication replaces FRS. If you need to migrate any domain controllers that use FRS for the SYSVOL folder to DFS replication, see [Streamlined Migration of FRS to DFSR SYSVOL](https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405). |

119 −| Hyper-V Network Virtualization (HNV) | [Network virtualization](../networking/sdn/technologies/hyper-v-network-virtualization/whats-new-hyperv-network-virtualization-windows-server.md) is now included in Windows Server as part of [Software defined networking](/azure/azure-local/concepts/software-defined-networking?context=/windows-server/context/windows-server-edge-networking) (SDN). SDN also includes the Network Controller, Software Load Balancer, User Defined Routing, and access control lists. |

119 +| Hyper-V Network Virtualization (HNV) | [Network virtualization](../networking/sdn/technologies/hyper-v-network-virtualization/whats-new-hyperv-network-virtualization-windows-server.md) is now included in Windows Server as part of [software defined networking](/azure/azure-local/concepts/software-defined-networking?context=/windows-server/context/windows-server-edge-networking) (SDN). SDN also includes the Network Controller, Software Load Balancer, User Defined Routing, and access control lists. |

120120 | Nano Server installation option | Nano Server isn't available as an installable host operating system. Instead, Nano Server is available as a container operating system. To learn more about Nano Server as a container, see [Windows Container Base Images](/virtualization/windowscontainers/manage-containers/container-base-images). |

121121 | Print components (Now optional components for Server Core installations) | In previous releases of Windows Server, the print components were disabled by default in the Server Core installation option. We changed that in Windows Server 2016, enabling them by default. In Windows Server 2019, those print components are once again disabled by default for Server Core. If you need to enable the print components, you can do so by running the following cmdlet: `Install-WindowsFeature Print-Server` |

122122 | [Remote Desktop Connection Broker and Remote Desktop Virtualization Host](../remote/remote-desktop-services/desktop-hosting-service.md) in a Server Core installation | Most Remote Desktop Services deployments have these roles colocated with the Remote Desktop Session Host (RDSH), which requires Server with Desktop Experience. To be consistent with RDSH, we're changing these roles to also require Server with Desktop Experience. These RDS roles are no longer available for use in a [Server Core installation](../administration/server-core/what-is-server-core.md). If you need to [deploy these roles as part of your Remote Desktop infrastructure](../remote/remote-desktop-services/rds-deploy-infrastructure.md), you can [install them on Windows Server with Desktop Experience](../get-started/getting-started-with-server-with-desktop-experience.md). These roles are also included in the Desktop Experience installation option of Windows Server 2019. |

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