What’s changed
Windows 11, version 25H2 is now a supported target release. In practical terms, that means admins can build, deploy and upgrade to 25H2 using the same familiar workflows already in place for earlier Windows 11 releases, without falling outside supported configurations.
Supported scenarios
Support covers the two paths most organisations rely on when moving devices to a new feature release:
- Operating system deployment: provisioning devices with Windows 11, version 25H2 as the installed build.
- In-place upgrade: moving existing devices to 25H2 while preserving apps, data and settings.
Why it matters for IT admins
Formal support for a new feature release is the signal that it is safe to plan broad rollouts. Until that point, admins are typically limited to pilot rings and evaluation devices. With 25H2 covered for both fresh deployment and in-place upgrade, you can align imaging, task sequences and upgrade rings on a single target version and reduce the number of Windows builds you carry in production.
Suggested next steps
Treat the move to 25H2 as a standard feature-update project rather than a one-off task. A staged approach keeps risk low while you validate business-critical applications.
- Confirm your deployment tooling and any supporting components are up to date before targeting 25H2.
- Validate line-of-business applications, drivers and security agents on a pilot ring.
- Update image builds and task sequences to reference 25H2 media.
- Roll out in phased rings, monitoring upgrade success rates and rollbacks before expanding scope.
Source: Microsoft Learn. Summarised independently — check the source for the latest detail.