Microsoft to Retire Windows Deployment Services After Windows Server 2025
Microsoft announced on September 21, 2026 (via support notice KB5129631) that it will deprecate the Windows Deployment Services (WDS) server role, starting with the next Windows Server release after Windows Server 2025. WDS — a successor to the older Remote Installation Services (RIS) — has been the built-in mechanism IT administrators use to network-boot and image fleets of machines via PXE (Preboot Execution Environment), and its wind-down has been underway in stages for years. Microsoft says the inbox WDS role, its management tools and APIs, WDS-provided PXE boot and network bootstrap, and WDS multicast transport are all on the deprecation list, and it is directing organizations toward Microsoft Configuration Manager operating system deployment as the supported path forward.
Details
| Attribute | Value |
|---|---|
| Feature being deprecated | Windows Deployment Services (WDS) server role — Deployment Server and Transport Server role services, PXE boot/network bootstrap, management tools/CLI/APIs, multicast transport, WinPE-WDS-Tools |
| Deprecation announced | September 21, 2026 (Microsoft support notice, KB5129631) |
| Starting release | The next Windows Server release after Windows Server 2025 |
| Currently affected releases | None yet — Windows Server 2025 and all currently supported earlier releases keep WDS per their published servicing lifecycles |
| Replacement technology | Microsoft Configuration Manager operating system deployment (PXE responder without WDS); third-party PXE/deployment platforms for standalone WDS use cases |
| Current support status | WDS remains fully available and supported on all currently supported Windows Server versions; only future removal is affected |
| Prior partial deprecations | boot.wim support removed (2021); hands-free deployment disabled by default (January 2026, effective with April 2026 cumulative updates) |
| Removal date | Not yet specified — Microsoft has committed only to a "future" Windows Server release |
What This Means for IT Admins
Windows Server 2025 is unaffected for now
Microsoft was explicit that this is a deprecation announcement, not an immediate removal. The company stated that "while deprecated, WDS will continue to work on all currently supported Windows Server versions according to their published servicing lifecycles," and that the notice "does not change WDS availability or support" on those releases. Admins running WDS on Windows Server 2025 or earlier, currently supported versions do not need to take emergency action, but the direction of travel is clear: WDS has no long-term future in Windows Server.
A years-long wind-down, not a surprise cut
This announcement extends a pattern Microsoft has followed since at least 2021, when it dropped boot.wim support from WDS. More recently, Microsoft disabled hands-free deployment by default starting in January 2026, a change that took effect for customers who installed the April 2026 cumulative update or later. Since the arrival of Windows 11, Microsoft has already stopped supporting WDS for deploying standard desktop operating systems via its native setup engine, restricting the role to deploying Windows Server itself or booting custom deployment environments. The latest announcement is the clearest signal yet that WDS as a whole — not just individual features — is being phased out.
Configuration Manager users are not exempt from planning
Microsoft was careful to note that "Microsoft Configuration Manager operating system deployment is not being affected" by this deprecation. However, many Configuration Manager (formerly SCCM) environments still rely on WDS under the hood for their PXE-backed deployment point and for multicast imaging jobs. Microsoft is explicitly telling those organizations to "begin migrating Configuration Manager environments that still use WDS-backed PXE or WDS-dependent multicast away from those WDS dependencies" — even though Configuration Manager itself continues to be supported.
Multicast imaging has no direct replacement yet
The most consequential gap in the announcement is multicast. Configuration Manager's own PXE responder — the one that does not depend on WDS — supports unicast only. Organizations that use WDS-backed multicast to image large numbers of machines simultaneously over constrained network links (a common pattern in classroom labs, retail rollouts, and bulk device refreshes) will need a different strategy once multicast support is gone, since there is currently no like-for-like Microsoft replacement for that specific capability.
Recommendations
For admins still running WDS-backed PXE imaging
- Inventory every deployment point, task sequence, and boot image that currently depends on WDS, including standalone WDS servers not managed through Configuration Manager.
- If already on Configuration Manager, begin testing the PXE responder without WDS in a lab environment, and confirm task sequences and drivers work correctly under the unicast-only model.
- If running WDS outside of Configuration Manager for custom PXE or deployment environments, start evaluating third-party PXE and deployment platforms now rather than waiting for a removal date.
For environments that rely on multicast deployment
- Flag multicast-dependent imaging workflows as a priority migration item, since Configuration Manager's WDS-free PXE responder cannot replicate multicast today.
- Model the network impact of switching affected imaging jobs to unicast, particularly for large simultaneous rollouts over bandwidth-constrained links, and budget for potential infrastructure changes (additional bandwidth, staggered imaging windows, or local caching/distribution points).
- Track Microsoft's guidance for any future multicast-capable alternative before committing to a permanent workaround.
For organizations considering modern alternatives
- Evaluate HTTP(S) Boot where device firmware and network infrastructure support it — Microsoft notes it can work in some environments but stresses it does not directly replace Configuration Manager PXE deployment.
- Consider whether cloud-based provisioning (e.g., Windows Autopilot/Intune-driven deployment) fits use cases currently handled by on-premises PXE imaging, especially for standard desktop OS deployment where WDS support was already curtailed after Windows 11's release.
- Treat this as an opportunity to reduce reliance on legacy, on-premises-only imaging infrastructure ahead of a hard cutoff, rather than migrating reactively once a removal date is set.
Key Takeaways
- Microsoft announced on September 21, 2026 that it will deprecate the Windows Deployment Services (WDS) server role, starting with the next Windows Server release after Windows Server 2025.
- WDS remains fully supported and unchanged on Windows Server 2025 and all currently supported earlier releases — no removal date has been set yet.
- The deprecation covers the WDS role, PXE boot/network bootstrap, management tools and APIs, and multicast transport; non-Microsoft PXE implementations are unaffected.
- Microsoft Configuration Manager operating system deployment is the recommended replacement path, but Configuration Manager environments still using WDS-backed PXE or WDS-dependent multicast need to migrate away from those dependencies.
- Configuration Manager's PXE responder without WDS supports unicast only — there is currently no direct replacement for WDS-backed multicast imaging.
- This follows earlier partial cuts (boot.wim removed in 2021, hands-free deployment disabled by default in January 2026), confirming a multi-year wind-down rather than a single abrupt change.