Microsoft has given IT teams an early warning: the built-in Windows Deployment Services role and WDS-provided PXE boot are planned for deprecation beginning with the next Windows Server release. The September 24 Windows Message Center notice points to Microsoft Support article KB5129631 and tells organizations to begin migration planning.[1][2]
The short version
- This is a lifecycle advisory, not a patch: KB5129631 is the documentation ID; Microsoft did not release a new Windows Server build with this announcement.[1][2][5]
- Nothing stops today: WDS remains available on supported Windows Server 2025 and earlier releases, subject to each release’s lifecycle and current security guidance.[2]
- The scope is broad: Microsoft names the inbox WDS role, WDS services and tools, WDS-provided PXE, APIs, multicast workflows, and WDS-specific Windows PE components.[2]
- Configuration Manager is not being deprecated: organizations using its WDS-backed PXE path should migrate to the Configuration Manager PXE responder without WDS.[2][3]
- Home users: ordinary home PCs do not use the Windows Server WDS role and need no action because of this notice.
- Apple check: Apple’s official ledgers showed no September 24 macOS security or system release at our cutoff; the same-day Developer entry was TestFlight 4.4.0, not macOS.[6][7][8]
Reporting cutoff: September 24, 2026 at 7:10 p.m. EDT (23:10 UTC). Microsoft posted the Windows Message Center announcement at 3:00 p.m. Pacific / 6:00 p.m. Eastern on September 24; the underlying support article shows an original publication date of September 21.[1][2]
What Microsoft announced
Microsoft plans to mark the remaining inbox WDS server role and WDS-provided PXE functionality as deprecated in the next Windows Server release.[2] Deprecation means the components are no longer the recommended path and organizations should migrate, but it is not the same as immediate removal.[2]
Microsoft has not published the next Windows Server release date, the exact deprecation milestone, or the later removal release.[2] Its advisory says removal could occur in the next Long-Term Servicing Channel release or several releases later, and promises updates when the timeline is available.[2] That uncertainty is why this is a planning deadline rather than an emergency change window.
Affected and not affected
Phone readers: swipe the table left to see every column. Treat “affected” here as a migration dependency—not proof that a working server has failed.
| Environment or workflow | Status | Practical meaning |
|---|---|---|
| Direct WDS imaging or custom PXE workflows | Affected dependency | Inventory the WDS role, WDSUTIL, APIs, custom Windows PE clients, boot images, scripts, and network-boot paths; evaluate a non-WDS deployment design.[2] |
| Configuration Manager using WDS-backed PXE | Affected dependency | Configuration Manager remains supported, but Microsoft says to move its PXE path to the Configuration Manager PXE responder without WDS.[2][3] |
| WDS-dependent multicast | Affected dependency | The Configuration Manager PXE responder without WDS is unicast.[2] Capacity, bandwidth, distribution points, scheduling, and deployment-wave size may need redesign.[2] |
| Windows Server 2025 or earlier with WDS | No immediate shutdown | WDS stays available on currently supported releases according to their servicing lifecycles, but it is no longer the recommended long-term architecture.[2][9] |
| Independent PXE or third-party deployment tools that do not use inbox WDS | Not directly affected | Microsoft says independent PXE implementations and non-Microsoft tools without a WDS dependency are outside this change.[2] |
| HTTP(S) Boot | Possible alternative in some designs | It may fit supported firmware and network environments, but Microsoft explicitly says it is not a replacement for Configuration Manager PXE-based OS deployment.[2] |
| Home Windows PC or Mac | Not affected by this advisory | This concerns a Windows Server deployment role, not the update mechanism on an ordinary home computer. |
KB and build details: what changed today
KB5129631 is the support-article identifier for this lifecycle notice; it is not a cumulative update package.[2] The official Windows Server release table showed no September 24 Server build at our cutoff.[5]
| Windows Server release | Latest listed production update | Build | Classification |
|---|---|---|---|
| Windows Server 2025 | KB5129235 | 26100.33451 | September 14 out-of-band update—not today’s WDS advisory.[5] |
| Windows Server 2022 | KB5129237 | 20348.5631 | September 14 out-of-band update—not today’s WDS advisory.[5] |
| Windows Server 2019 | KB5129238 | 17763.9247 | September 14 out-of-band update—not today’s WDS advisory.[5] |
| Windows Server 2016 | KB5129239 | 14393.9514 | September 14 out-of-band update—not today’s WDS advisory.[5] |
For desktop Windows, Microsoft’s latest production entries remained the September 22 optional D-preview packages for Windows 11 26H1, 25H2, and 24H2; those are separate from WDS.[10] The September MSRC cycle still carries an initial release date of September 8, so today’s notice should not be described as Patch Tuesday or a new security release.[11] For the current security baseline and the September 14 out-of-band fixes, use our Windows and macOS update guide.
The migration traps to test
This advisory does not publish a new patch with a “known issues” table. The practical risks are architectural: hidden WDS dependencies can survive in custom Windows PE images, WDSUTIL scripts, APIs, multicast jobs, DHCP/IP-helper configuration, firmware boot order, network access controls, and disaster-recovery runbooks.[2]
- Multicast-to-unicast capacity: a design that worked because one image stream served many PCs can overload links or distribution points when converted without capacity testing.[2]
- False replacement assumptions: HTTP(S) Boot is useful in some environments, but Microsoft says not to present it as a drop-in replacement for Configuration Manager PXE deployment.[2]
- Old hands-free workflows: WDS hands-free deployment scenarios were disabled by default and became unsupported after installing updates released on or after April 14, 2026.[2][4]
- Boot-image blind spots: a lab test should include real firmware modes, network segments, drivers, BitLocker/recovery procedures, security controls, image sizes, and representative deployment volume.
- Rollback without recovery: do not remove the known-good WDS path until the replacement can deploy, recover, and troubleshoot representative devices under controlled conditions.
What businesses should do now
- Find every WDS server and indirect dependency. Inventory installed roles and services, WDSUTIL, APIs, Windows PE tooling, custom scripts, Configuration Manager settings, multicast jobs, DHCP/IP helpers, and recovery documentation.
- Name an owner and a target architecture. Decide whether the destination is Configuration Manager’s PXE responder without WDS, a supported third-party deployment platform, or another tested design appropriate to your fleet.
- Build a representative pilot. Include UEFI firmware variations, VLANs, remote sites, security controls, large images, high-concurrency deployment, driver injection, and failure recovery.
- Measure before replacing multicast. Record bandwidth, distribution-point load, deployment time, and concurrency; add capacity or smaller waves before switching to unicast.
- Keep a supported bridge. Microsoft says organizations needing more time may continue using WDS on a currently supported Windows Server release, subject to that release’s lifecycle and applicable WDS security guidance.[2]
- Document the exit. Preserve rollback steps, remove stale automation only after acceptance, and update onboarding, recovery, and audit evidence.
What home users should do
Nothing because of this announcement. WDS is a Windows Server deployment role used to install or recover multiple computers over a network. It is not the Windows Update service on your PC, and this notice does not mean Windows 11, Windows 10, or a home router will stop booting. Keep normal backups and install the appropriate security updates for your device; do not download a “WDS fix” from an unofficial site.
Good
- Microsoft gave advance notice instead of removing WDS without warning.
- Current supported Windows Server releases keep WDS during the transition.
- The advisory names direct and indirect dependencies that teams can inventory.
- Configuration Manager has a Microsoft-supported PXE responder path that does not require WDS.
Bad / caution
- Microsoft has not yet supplied exact deprecation or removal dates.
- WDS dependencies can hide in imaging, recovery, multicast, scripts, APIs, and Windows PE.
- Moving multicast workloads to unicast can create capacity problems.
- HTTP(S) Boot is not a universal substitute for Configuration Manager PXE deployment.
Apple check: no same-day Mac update
Apple’s security-release page showed no September 24 macOS or Safari release at our cutoff.[6] The newest Mac production entries remained macOS Golden Gate 27, macOS Tahoe 26.7, macOS Sequoia 15.8, and Safari 27 from September 14.[6] Apple’s Background Security Improvements page still showed March 17 as its newest dated entry, while Apple Developer’s September 24 listing was TestFlight 4.4.0 rather than a macOS build.[7][8]
Frequently asked questions
Is WDS shutting down now?
No. Microsoft says WDS remains available and supported on currently supported Windows Server releases, including Windows Server 2025 and earlier. The next Windows Server release is planned to begin deprecation; a later removal date has not been announced.[2]
Is KB5129631 an update I should install?
No. KB5129631 identifies the Microsoft Support advisory. It is not a cumulative update package and does not correspond to a new September 24 Windows Server build.[2][5]
Is Configuration Manager OS deployment going away?
No. Microsoft says Configuration Manager operating-system deployment is not being deprecated. The affected dependency is its WDS-backed PXE option; Microsoft directs those environments toward the Configuration Manager PXE responder without WDS.[2][3]
Can I just replace WDS with HTTP(S) Boot?
Not automatically. Microsoft says HTTP(S) Boot may fit some deployment solutions when firmware and networking support it, but it is not a replacement for Configuration Manager PXE-based operating-system deployment.[2]
Should I remove WDS this week?
No—not without a tested successor. Start discovery and a controlled pilot now, but keep the known-good supported path until the replacement passes deployment, recovery, performance, security, and rollback checks.
If your business uses Windows Server imaging, PXE boot, Configuration Manager, or custom Windows PE workflows and needs help identifying dependencies, schedule The IT Guys for practical support in Port Saint Lucie, Jensen Beach, Fort Pierce, and Vero Beach. For broader lifecycle planning, see our Windows Server 2022 support-transition guide.
Official sources checked
- Microsoft — Windows Message Center.
- Microsoft Support — Windows Deployment Services deprecation (KB5129631).
- Microsoft Learn — Operating-system deployment in Configuration Manager.
- Microsoft Support — WDS hands-free deployment hardening guidance.
- Microsoft — Windows Server release information.
- Apple — Apple security releases.
- Apple — Background Security Improvements by date.
- Apple Developer — Software Releases.
- Microsoft Lifecycle — Windows Server 2025.
- Microsoft — Windows 11 release information.
- Microsoft Security Response Center — CVRF update index.