Microsoft to Phase Out Windows Deployment Services from Windows Server

⚡ The 5-Second Summary - Microsoft is ending support for Windows Deployment Services (WDS) starting with the next release of Windows Server. - The notice was published on September 21, 2026 (KB ID 5129631) and applies to Windows Server 2016, 2019, 2022, version 23H2, and Windows Server 2025. - The company classifies this as a deprecation: WDS will continue to work on supported versions but will be removed from future OS releases. No exact date has been given. ### 🔍 What Was Discovered On September 21, 2026, Microsoft published a notice about deprecating the Windows Deployment Services role in the next release of Windows Server. WDS is a technology that allows administrators to deploy Windows to dozens or hundreds of machines over the network; it descends from the earlier Remote Installation Services tool. The notice covers the entire WDS role, including Deployment Server and Transport Server, PXE boot and network boot, management tools, CLI and APIs, multicast transport for large-scale deployments, and the WinPE-WDS-Tools components. This is already the third restriction: in 2021, Microsoft deprecated Windows Setup scenarios using boot.wim for Windows 11 and later, and after the CVE-2026-0386 vulnerability (an unauthenticated RPC channel with unattend.xml leading to credential theft or remote code execution), the hands-free deployment feature could first be manually disabled via registry keys starting January 13, 2026, and then, as of April 14, 2026, it was disabled by default on systems with updates installed after that date. ### 💡 Why It Matters Organizations relying on WDS should plan their migration in advance. Microsoft notes that OS deployment in Configuration Manager is not affected, but if ConfigMgr uses WDS-backed PXE or multicast, those dependencies will have to be dropped, since the built-in PXE responder without WDS supports unicast only. This will require additional distribution point capacity, more network bandwidth, or smaller deployment waves. HTTP(S) Boot can serve as a firmware-level replacement, but Microsoft warns that it is not a substitute for PXE deployment in Configuration Manager. Third-party products and independent PXE implementations that do not use the built-in WDS role are not affected. ### 🧩 Context Prior to the latest notice, Microsoft had already narrowed WDS functionality twice: in 2021 for Windows 11 and later installation scenarios, and then due to CVE-2026-0386. The company emphasizes that deprecation is not removal: WDS will remain in supported versions of Windows Server until the end of their lifecycle. Microsoft advises administrators to inventory servers with the WDS role and identify which deployment, recovery, or network boot processes depend on it. The KB article will be updated once the release schedule for the next version of Windows Server and the removal stages are finalized.

🔗 Read on betanews.com