In short
Yes. Windows Server 2016 can be upgraded directly to Windows Server 2025 in supported nonclustered member-server and application-server scenarios using Windows Server 2025 installation media. You do not need to upgrade through Server 2019 or 2022 first.
The decision changes when the server is a domain controller. For AD DS, Microsoft recommends deploying a clean Windows Server 2025 machine, promoting it as a new DC, replicating Active Directory, transferring FSMO roles, and then demoting the Server 2016 DC instead of treating the DC like a normal in-place OS upgrade.
Windows Server 2016 reaches the end of extended support on January 12, 2027. For most production environments, plan the move role by role: direct in-place upgrade can be efficient for a simple supported member server, while side-by-side migration is usually easier to validate for domain controllers, file servers, SQL Server, DHCP, RDS, and mixed line-of-business workloads. If the migration also means moving infrastructure, Raff can be used as the Windows Server 2025 destination while you keep the old Server 2016 system available for validation and rollback.
Can you upgrade Windows Server 2016 directly to 2025?
Yes. You can upgrade Windows Server 2016 to 2025 directly with installation media on a nonclustered member or application server. Windows Server 2025 extended the supported in-place upgrade path back to Windows Server 2012 R2, so 2016 no longer needs an intermediate hop through 2019 or 2022. Domain controllers and clustered hosts are the exception: migrate those side by side instead.
That means a normal member or application server can have a valid Windows Server 2016 → Windows Server 2025 in-place upgrade path without stepping through intermediate Windows Server releases first. Before using it, verify edition compatibility, application support, backup/restore readiness, and Microsoft's current in-place upgrade prerequisites.
The important distinction is the upgrade method and server role:
| Scenario | Recommended approach |
|---|---|
| Server 2016 member/app server | Direct in-place upgrade can be supported after compatibility and backup checks |
| Server 2016 domain controller | Deploy a fresh Server 2025 DC, replicate, transfer roles, then demote the old DC |
| Server 2016 file server | Side-by-side file migration is usually easier to validate and roll back |
| Server 2016 SQL host | Build the target SQL environment, migrate user databases and server objects separately |
| Server 2016 DHCP server | Migrate DHCP configuration and leases, authorize the new server, then retire the old role |
| Server 2016 RDS host | Validate application compatibility, RDS licensing, profiles, certificates, and user cutover before migration |
| Failover cluster | Follow the cluster-specific rolling upgrade path; do not treat it like a normal standalone server |
One more distinction matters: Microsoft's current Windows Update upgrade path to Windows Server 2025 is for eligible Windows Server 2019 and 2022 systems. A Server 2016 → 2025 direct upgrade should therefore be planned around the supported installation-media path, not assumed to appear as a normal Windows Update feature upgrade.
Windows Server 2016 support ends in January 2027
![]()
Microsoft's current lifecycle information lists:
| Version | Mainstream support | Extended support |
|---|---|---|
| Windows Server 2016 | Ended | January 12, 2027 |
| Windows Server 2025 | Through 2029 | Through 2034 |
After extended support ends, Server 2016 no longer receives normal security updates through the standard lifecycle. Organizations that cannot migrate in time should evaluate Microsoft's current Extended Security Updates options directly rather than relying on old percentage-based pricing examples, because ESU availability and commercial terms can change. The full schedule for every version is in the Windows Server end-of-life dates table.
For a production business server, the practical goal is to finish compatibility testing and cutover before the January 2027 deadline, not begin the project when the deadline arrives.
Choose the migration path by workload
The old server's role determines the safest approach.
Domain controller
Use a side-by-side Active Directory migration. This is the cleanest path because you keep the existing DC available while the new Server 2025 DC replicates and is validated.
File server
Use a side-by-side migration with Storage Migration Service or a controlled file-copy workflow. Validate NTFS ACLs, share permissions, paths, quotas, and client mappings before retiring the source.
SQL Server
Build and patch the destination SQL Server first, then migrate user databases and recreate or transfer instance-level objects such as logins, SQL Agent jobs, credentials, linked servers, and configuration.
Do not plan a cross-version migration by restoring old master, model, or msdb system database backups onto a new major SQL Server version. Treat server-level configuration as a separate migration task.
Line-of-business application server
Check the application vendor's Windows Server 2025 support matrix first. A technically supported Windows in-place upgrade does not guarantee that your ERP, accounting, tax, document-management, or legacy application supports the new OS.
DHCP
Treat DHCP as its own migration step. Export the existing scopes and leases, install and authorize the DHCP role on the new server, import the configuration, update failover or relay settings if used, then validate clients before removing the old DHCP service.
Remote Desktop Services
RDS migrations need additional planning around Session Host roles, licensing, user profiles, certificates, applications, Group Policy, and client access. Administrative RDP and a true multi-user RDS deployment are not the same architecture. See Multi-User RDP vs RDS Session Host. Budget for Windows Server 2025 RDS CALs before cutover; 2016-era CALs will not license the new host.
Side-by-side migration vs in-place upgrade
Both approaches are valid tools. The role and rollback requirement decide which one you should use.
| Area | In-place upgrade | Side-by-side migration |
|---|---|---|
| Keeps existing apps/settings | Yes | Rebuild and migrate |
| Requires second server | No | Yes |
| Rollback simplicity | Depends heavily on backup/restore | Old server remains available during validation |
| Removes years of OS state | No | Yes |
| Best for DC migration | Not preferred | Preferred |
| Best for simple member server | Often reasonable | Also valid |
| Best for hardware/cloud move | Limited | Strong fit |
| Best for role separation | No | Strong fit |
If the Server 2016 machine is a simple, well-documented member server and every installed application supports Server 2025, an in-place upgrade can reduce migration work.
If it is a domain controller, combined file/application server, poorly documented legacy machine, or the migration also moves workloads into a new cloud environment, side-by-side is usually easier to test and recover from.


