Original publish date: September 21, 2026
KB ID: 5129631
Summary
Microsoft plans to deprecate the Windows Deployment Services (WDS) server role beginning with the next release of Windows Server. This includes the inbox WDS role, WDS services, management tools, and interfaces, and WDS-provided Preboot Execution Environment (PXE) boot functionality.
Deprecated products are supported until they are eventually removed from a future OS version. While deprecated, WDS will continue to work on all currently supported Windows Server versions according to their published servicing lifecycles. This announcement does not change WDS availability or support on those releases. Learn more at Deprecation: What it means in the Windows lifecycle.
Begin planning your migration from the deprecated WDS to alternatives. For example, Microsoft Configuration Manager provides a better, more flexible, and feature-rich experience for deploying Windows images.
Important
This is an early notice to help organizations identify dependencies and begin migration planning. Microsoft will update this article as the release schedule, deprecation and removal milestones, and additional migration guidance become available.
What is changing
In the next release of Windows Server, Microsoft plans to deprecate the inbox WDS server role and associated WDS functionality, including:
- The Windows Deployment Services server role and its Deployment Server and Transport Server role services
- WDS-provided PXE boot and network bootstrap functionality
- WDS management tools, command-line interfaces, APIs, and related service activation paths
- WDS multicast transport and WDS-dependent multicast deployment workflows
- Related Windows Preinstallation Environment components that are used specifically to create or operate WDS clients, including WinPE-WDS-Tools
However, deprecated products are no longer the recommended solution. Organizations should plan to transition to the recommended replacement before the deprecated feature is removed in future releases.
What is not changing
- WDS remains available on currently supported Windows Server releases, including Windows Server 2025 and earlier. Consult your release’s published support lifecycle at Microsoft Lifecycle.
- Independent PXE implementations and non-Microsoft deployment products that do not depend on the inbox WDS role are not affected by this change.
- Microsoft Configuration Manager operating system deployment is not being affected. However, begin migrating Configuration Manager environments that still use WDS-backed PXE or WDS-dependent multicast away from those WDS dependencies.
- HTTP(S) Boot is a separate firmware and deployment capability. It may be an alternative for applicable deployment solutions, but it is not a replacement for Configuration Manager PXE-based operating system deployment.
Timeline
| Milestone | Change |
|---|---|
| 2021 | Windows Setup workflows that use boot.wim from installation media in WDS mode were deprecated for Windows 11 and later Windows releases. Custom-image PXE scenarios remained available. |
| April 2026 | WDS hands-free deployment scenarios were disabled by default and became unsupported after installation of Windows updates released on or after April 14, 2026. |
| Current | Microsoft is providing early notice of the planned deprecation of the WDS server role and WDS-provided PXE functionality with the next release of Windows Server. |
| Next Windows Server release | The WDS server role and associated inbox WDS functionality are planned for deprecation. This article will be updated when public release and milestone information is available. |
Take action
If your organization uses WDS, begin dependency discovery and migration planning now.
- Inventory WDS deployments. Identify servers with the WDS role or WDS role services installed. Determine which deployment, recovery, imaging, or network boot workflows depend on them.
- Identify indirect dependencies. Review Configuration Manager, custom Windows PE images, scripts, automation, WDS APIs, WDSUTIL usage, multicast workflows, and applications that call WDS components.
- Validate alternatives. Evaluate the replacement approach with representative device firmware, network conditions, security controls, image sizes, and deployment volumes.
- Plan capacity changes. If moving from multicast to unicast deployment, assess distribution point capacity, network bandwidth, deployment scheduling, and deployment wave size.
- Retain supported systems during transition. Organizations that need additional migration time can continue using WDS on a currently supported Windows Server release, subject to that release’s lifecycle and applicable WDS security guidance.
Migration considerations
If you have a scenario not covered here, please post your question on the Windows Server for IT Pro discussion board.
| Current dependency | Mitration consideration |
|---|---|
| Configuration Manager with WDS-backed PXE | Configure and validate the Configuration Manager PXE responder without WDS. |
| Configuration Manager multicast | The Configuration Manager PXE responder without WDS supports unicast, not WDS-dependent multicast. Plan for unicast deployment. Evaluate whether additional distribution points, network capacity, or smaller deployment waves are required. |
| Direct WDS or custom PXE workflows | Evaluate non-Microsoft PXE and deployment solutions. HTTP(S) Boot may be an option when it is supported by the device firmware, network environment, and selected deployment solution. |
| Custom Windows PE WDS clients | Identify dependencies on WinPE-WDS-Tools and WDS client APIs. Then redesign the workflow around a deployment solution that does not require inbox WDS components. |
Frequently asked questions
What does deprecation mean?
Deprecated components are still available for use and in support per the lifecycle of the product. However, they are no longer recommended as the best solution and are not being developed further. Deprecation period is designed to begin migration to newer and better alternatives. Deprecation precedes complete removal at the end of the official product lifecycle. Learn more at Deprecation: What it means in the Windows lifecycle.
Is WDS already deprecated?
Yes, it is partially deprecated. Windows Setup workflows that rely on boot.wim from installation media in WDS mode were previously deprecated, and WDS has been listed as no longer being actively developed. This announcement provides early notice of the planned deprecation of the remaining inbox WDS role and WDS-provided PXE functionality.
Does this change affect WDS on Windows Server 2025 or earlier releases?
No immediate functionality change is being made by this announcement. WDS remains available on currently supported Windows Server releases according to their published servicing lifecycles. Customers must continue to apply applicable security updates and follow current WDS security guidance.
Is Configuration Manager operating system deployment being deprecated?
No. Configuration Manager operating system deployment is not being depreciated. Customers using its WDS-backed PXE option should migrate to the Configuration Manager PXE responder without WDS. WDS-dependent multicast is not supported by that responder.
Can HTTP(S) Boot replace Configuration Manager PXE-based operating system deployment?
No. HTTP(S) Boot should not be presented as a replacement for Configuration Manager PXEbased operating system deployment. It may be an alternative for other deployment solutions when supported by device firmware and the network environment.
Will WDS be completely removed at some point?
Yes. A natural lifecycle milestone after deprecation is removal in a future OS release. Removal is when a feature or functionality is no longer available for use and has been removed from a product or service. Removal can happen in the next Long-Term Servicing Channel (LTSC) release, or it can be several releases away. We will update this page when this timeline is available.
Additional resources
- Windows Deployment Services (WDS) boot.wim support
- Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance related to CVE-2026-0386
- Introduction to operating system deployment in Configuration Manager
- Features removed or no longer developed in Windows Server
- Windows Server for IT Pro discussion board
Change log
| Change date | Change description |
|---|---|
| September 21, 2026 | Published early notice of the planned deprecation of the WDS server role and WDS-provided PXE functionality. |