Microsoft Message
- Microsoft plans to deprecate the Windows Deployment Services (WDS) server role in the next Windows Server release.
- The deprecation covers the WDS role, services, management tools, interfaces, and WDS-provided PXE boot functionality.
- Organizations using WDS should inventory deployments, identify dependencies, and plan migration to supported alternatives such as Microsoft Configuration Manager.
- Existing supported Windows Server versions still retain WDS for now, but this is a migration window before eventual removal.
- Microsoft notes no compliance issues identified in this message.
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. Begin planning your migration to alternatives. For example, Microsoft Configuration Manager provides a better, more flexible, and feature-rich experience for deploying Windows images.
Message ID: MC1478819
Primary Service: Windows
Admin Impact: Medium
User Impact: Low
Release Start: 24 Sept 2026
Release End: 24 Sept 2026
Published: Sep 24, 2026
Services: Windows
Category: Stay informed
Tags: Admin Action
History
9/24/2026 Item Added to Message Center
Rollout schedule
- 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.
- Next Windows Server release: The WDS server role and associated inbox WDS functionality are planned for deprecation.
Impact on your organization
If your organization uses WDS, there’s no immediate functionality change. WDS remains available on currently supported Windows Server releases according to their published servicing lifecycles. However, deprecation period is designed to begin migration to newer and better alternatives before eventual removal.
Action required/recommendations
To start planning your migration:
- Inventory WDS deployments.
- Identify indirect dependencies.
- Validate alternatives.
- Plan capacity changes.
- Retain supported systems during transition.
For detailed guidance and special migration considerations, see Windows Deployment Services (WDS) deprecation in the next Windows Server release. If you have a scenario not covered here, please post your question on the Windows Server for IT Pro discussion board.
Compliance considerations
No compliance considerations are identified. Review as appropriate for your organization.