Skip to content
Deploy

Server updates

Upgrade Windows Server 2016 to 2022 or 2025: in place or a new server?

Microsoft supports an in-place upgrade from Windows Server 2016 straight to 2025 for most servers, but on a rented RDP server a new server is usually safer. The supported paths, what blocks an upgrade, the license you need and the steps for each route.

RyzenRDP guide cover: upgrade Windows Server 2016 to 2022 or 2025, in place or a new server

Key takeaways

  • Windows Server 2016 upgrades in place straight to 2019, 2022 or 2025 from installation media, unless it runs the Remote Desktop Services role: Microsoft's RDS upgrade page still allows two versions per step. Windows Update offers Windows Server 2025 only to 2019 and 2022.
  • A new server is usually the safer route for a rented RDP server: the old one keeps running until the new one works.
  • Every upgrade needs a license for the new version. Microsoft says each Windows Server upgrade requires a separate license, with a valid product key and activation.
  • Domain controllers and Remote Desktop session hosts have their own rules: Microsoft advises against upgrading a domain controller in place, and its RDS upgrade page still allows two versions per step.
On this page
  1. Short answer
  2. Can Windows Server 2016 upgrade straight to 2025?
  3. In-place upgrade or a new server: which is safer?
  4. What blocks an in-place upgrade?
  5. Do I need a new license to upgrade?
  6. How do I run an in-place upgrade?
  7. How do I move a Windows Server 2016 VPS to 2022 or 2025 without losing my apps?
  8. Should I pick Windows Server 2022 or 2025?
  9. Do it yourself, or have the move done for you

Short answer

Windows Server 2016 can be upgraded in place straight to Windows Server 2025, or to 2019 or 2022, when you run Setup from installation media, unless it runs the Remote Desktop Services role: for that role, Microsoft's RDS upgrade page still allows two versions per step. Windows Update has no upgrade path from 2016. For a rented server that people reach over Remote Desktop, a new Windows Server 2022 or 2025 server with your data and apps moved across is usually the safer route, because the old server keeps running until the new one works. Either way you need a license for the new version: Microsoft notes that "unlike Windows client, each Windows Server upgrade requires a separate license."

Microsoft lists the end of extended support for Windows Server 2016 as 12 January 2027. The dates and your options are on our Windows Server 2016 page.

Can Windows Server 2016 upgrade straight to 2025?

Yes, with installation media: the Windows Server 2025 upgrade path from 2016 is a single step. Microsoft's "Plan your Windows Server upgrade path" page (updated 14 April 2026) says that a server that is not clustered can upgrade up to four versions at a time to Windows Server 2025, so Windows Server 2012 R2 and later can go straight to 2025.

From Windows Server 2016 to With installation media With Windows Update
Windows Server 2019 Yes No
Windows Server 2022 Yes No
Windows Server 2025 Yes No

The Windows Update route reaches Windows Server 2025 only from 2019 or 2022. That is how to upgrade Windows Server 2019 to 2025, or 2022 to 2025, without an ISO. The steps from Microsoft's "Upgrade Windows Server in place" page:

  1. Install the March 2026 cumulative update or later (KB5078752 on 2019, KB5078766 on 2022), and restart if asked. Our guide to installing Windows updates with PowerShell shows how.

  2. In PowerShell as Administrator, add the policy value that turns the offer on:

    New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate"
    New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate" -Name "AllowWindowsServerFeatureUpdate" -PropertyType DWord -Value 1
    
  3. Open Settings > Windows Update, select Download and install on the Windows Server 2025 feature update, read the notes on licenses, then select Accept and install. The server restarts during the installation.

The same groundwork applies as for an upgrade from installation media: a full backup with a restore test, a license for Windows Server 2025, and a check with your provider first.

Two cases move in smaller steps:

  • Failover clusters move one version at a time, with a cluster OS rolling upgrade.
  • Servers with the Remote Desktop Services role installed, such as an RD Session Host for more than two users. Microsoft's RDS upgrade page, dated July 2024, still allows two versions at a time (its example is 2019 to 2025) and does not mention the four-version rule. Until Microsoft updates it, plan a 2016 session host as two upgrades (to 2019 or 2022, then to 2025) or as a new server. The two admin sessions of plain Remote Desktop do not need that role.

In-place upgrade or a new server: which is safer?

Microsoft's planning page calls migration the better choice when you move to new hardware, and a replacement server you rent is new hardware.

In-place upgrade New server (migration)
What happens Setup installs the new version over Windows Server 2016, keeping files, settings, roles and apps A clean Windows Server 2022 or 2025 server; you copy the data and reinstall the apps
If it goes wrong You restore your own full backup The old server is still running, so you keep using it
Downtime Offline during Setup, which restarts the server several times Only at the switch, when users and DNS move to the new address
Apps Kept, if each one supports the new version Reinstalled from your installers, then re-activated
Domain controller Not recommended by Microsoft Microsoft's path: promote new domain controllers, then demote the old ones
Windows Server license A key and activation for the new version A license for the new server
Running cost One server Two servers while both run

An in-place upgrade suits a single server with few apps, a full backup you have restored at least once, and a provider that allows it. For a server people rely on every day, build the new server alongside the old one.

What blocks an in-place upgrade?

Microsoft's planning page lists these restrictions for installations that are already licensed (not evaluation copies), and its role pages add the last two:

  • You cannot change the system language, or switch between Server Core and Server with Desktop Experience.
  • You cannot upgrade to an evaluation copy.
  • The edition can move up, from Standard to Datacenter, but never down.
  • NIC Teaming must be turned off first; you can turn it on again afterwards.
  • Servers that boot from a VHD, and Windows Storage Server editions, cannot be upgraded in place.
  • Domain controllers: Microsoft says not to upgrade servers that run Active Directory Domain Services in place.
  • RD Session Hosts: Microsoft says to uninstall all applications before the upgrade and reinstall them after.

Microsoft also says that some public and private cloud providers support in-place upgrades, and to check with yours; its installation-media method applies only to servers outside Azure. On a RyzenRDP server, ask us in a support ticket before you start one.

Check the server first, in PowerShell as Administrator. The first three lines come from Microsoft's in-place upgrade guide, and the last two save the installed roles and any NIC teams; copy the five files they save off the server.

Get-ComputerInfo -Property WindowsBuildLabEx,WindowsEditionID | Out-File -FilePath .\computerinfo.txt
systeminfo.exe | Out-File -FilePath systeminfo.txt
ipconfig /all | Out-File -FilePath ipconfig.txt
Get-WindowsFeature | Where Installed | Out-File -FilePath features.txt
Get-NetLbfoTeam | Out-File -FilePath nicteams.txt

features.txt lists the roles and features in use, and nicteams.txt stays empty when the server has no NIC teams.

Do I need a new license to upgrade?

Yes. Microsoft says to have a valid product key and activation method for the target version before you upgrade, and that each Windows Server upgrade requires a separate license. Keys and activation depend on where your media came from: a commercial licensing program, a retail channel or an OEM.

The Windows license of your old server does not move with your data. On RyzenRDP, the Windows Server license is not included in the plan price: Windows Server is installed for you but not activated, and you license and activate it yourself. We do not sell licenses or product keys. Which licenses can be used on a hosting provider's servers is in the licensing answer in our FAQ.

If more than two people need to sign in at once, the server needs the RD Session Host role, and then every user or device that connects needs a Remote Desktop Services client access license (RDS CAL) of the new version or later. Microsoft's compatibility table shows that Windows Server 2016 CALs do not work with a 2019, 2022 or 2025 session host.

How do I run an in-place upgrade?

Only after your provider has said yes and you have a full backup. Microsoft's prerequisites include a full backup of the operating system, apps and data with a restore test, a maintenance window, installation media for the target version and a valid product key. RyzenRDP takes no backups or snapshots of your server, so that copy is yours to make.

  1. Copy the five files from the check above off the server, and shut down any virtual machines running on it.
  2. Mount a Windows Server 2025 ISO from your licensing channel (an OEM, a retail channel, a Visual Studio subscription or the Microsoft 365 admin center, as Microsoft lists them) and run setup.exe from its root, for example D:\setup.exe. The evaluation ISO cannot be used for an upgrade.
  3. Choose how Setup downloads updates, enter your product key if asked, and pick the edition.
  4. Accept the license terms, choose Keep files, settings, and apps, then select Install. The server restarts several times.
  5. Confirm the result with Get-ComputerInfo -Property WindowsProductName, then test every app and connection.

If Setup fails or rolls back, read setuperr.log and setupact.log in the hidden folders C:\$Windows.~BT\Sources\Panther and C:\$Windows.~BT\Sources\Rollback, or run Microsoft's SetupDiag tool. After a finished upgrade that misbehaves, Microsoft points to C:\Windows\Panther. In a November 2026 Microsoft Q&A thread, the person whose 2016 to 2025 upgrade failed reported that setuperr.log pointed to installed applications.

How do I move a Windows Server 2016 VPS to 2022 or 2025 without losing my apps?

Build a new Windows Server 2022 or 2025 VPS, reinstall your apps from their installers, copy their data across, test, then switch; the old VPS keeps running until you are sure.

  1. Inventory the old server. Keep the five files from the check above, and list your apps with their installers and license details, scheduled tasks, IIS sites, SQL Server databases and user accounts.

  2. Order the new server, license and activate Windows Server, and add the same roles and features with Server Manager or Install-WindowsFeature, using the names in features.txt, for example Install-WindowsFeature -Name Web-Server -IncludeManagementTools.

  3. Copy the data with robocopy over an encrypted share. The copy runs on the new server and pulls from the old one, in one direction only. The examples use 203.0.113.10 for the old server, 198.51.100.20 for the new one and C:\Data for the folder; put in your own addresses and folders.

    On the old server, in PowerShell as Administrator, create a temporary account (Windows asks you for its password), share the folder read-only to that account with SMB encryption required, and allow file sharing only from the new server's address:

    New-LocalUser -Name moveuser
    New-SmbShare -Name MoveData -Path C:\Data -ReadAccess "$env:COMPUTERNAME\moveuser" -EncryptData $true
    New-NetFirewallRule -DisplayName 'Move-SMB-from-new-server' -Direction Inbound -Protocol TCP -LocalPort 445 -RemoteAddress 198.51.100.20 -Action Allow
    

    With encryption on the share, Windows refuses any connection that cannot encrypt, so your files cross the internet encrypted (Microsoft's "SMB security enhancements" page). The account also needs read permission on the folder itself; if robocopy reports "Access is denied", add it in the folder's Properties > Security.

    On the new server, in PowerShell as Administrator, check that port 445 on the old server answers, connect with the temporary account (the * makes Windows ask for its password; OLD-SERVER stands for the old server's computer name, which hostname shows there), and copy:

    Test-NetConnection 203.0.113.10 -Port 445
    net use \\203.0.113.10\MoveData * /user:OLD-SERVER\moveuser
    New-Item -ItemType Directory -Path C:\Logs -Force
    robocopy \\203.0.113.10\MoveData C:\Data /E /Z /COPY:DAT /DCOPY:DAT /R:2 /W:5 /LOG:C:\Logs\copy-data.log
    

    TcpTestSucceeded : False means port 445 is blocked on the way, and some providers block it. Ask your old provider to allow it for the new server's address, or have our Server move do the copy. Robocopy keeps attributes and timestamps and can restart an interrupted file. Leave out /MIR and /PURGE: Microsoft's robocopy reference explains that they delete destination files that are not in the source. You remove the account, share and rule after the final copy in step 8.

  4. Use Microsoft's migration tools where they fit. For a file server with many shares, Storage Migration Service inventories the old server, transfers files, shares and their security settings, and can take over the old server's name at cut-over. It accepts Windows Server 2016 as a source, runs from Windows Admin Center, asks for a destination on Windows Server 2019 or later (which can also be the orchestrator for a single server), and needs the SMB, Netlogon and WMI firewall rules open between the servers. Windows Server Migration Tools, a feature you add in Server Manager, moves roles, settings and shares, though its install guide dates from Windows Server 2012 R2.

  5. Move websites and databases. For IIS, Microsoft's role guide points to Web Deploy, which syncs a site's content, IIS settings and SSL certificates to another server. For SQL Server, back up each database, copy the .bak file and restore it on the new server. A backup never restores on an earlier SQL Server version, and you may have to re-create logins and jobs.

  6. Reinstall your apps from their installers and re-activate them with each vendor. Some software licenses do not allow use on a hosting provider's shared servers, so check each one first.

  7. Test with real user accounts: sign in over Remote Desktop, run each app and open recent files.

  8. Switch over. Run the robocopy command once more so it copies only what changed, then point DNS, saved .rdp files and your users to the new address. Keep the old server running until you are sure.

    Then remove what you added for the copy. On the new server, net use \\203.0.113.10\MoveData /delete closes the connection. On the old server, in PowerShell as Administrator:

    Remove-SmbShare -Name MoveData -Force
    Remove-NetFirewallRule -DisplayName 'Move-SMB-from-new-server'
    Remove-LocalUser -Name moveuser
    

    Removing the share leaves the folder and its files in place.

Should I pick Windows Server 2022 or 2025?

Pick the newest version your apps support. The facts that decide most cases:

Windows Server 2022 Windows Server 2025
End of extended support, as Microsoft lists it 14 October 2031 14 November 2034
Mainstream support Ended 13 October 2026 Runs to 13 November 2029
In place from 2016 with the RDS role installed Yes, in one step Two steps, or a new server
SQL Server versions Microsoft supports on it 2017, 2019, 2022 and 2025 2019, 2022 and 2025
RDS CALs a session host needs 2022 or 2025 CALs 2025 CALs

On a RyzenRDP Windows VPS you choose Windows Server 2019, 2022 or 2025 at order.

Do it yourself, or have the move done for you

A server with a few apps you can reinstall is a reasonable job to do yourself. SQL Server databases, IIS sites with certificates, many user profiles, or apps whose vendors must re-activate them take more work.

RyzenRDP's Server move takes the new-server route for you, from any provider to a RyzenRDP server:

Move Price What it covers
Assisted move Free with a yearly plan You copy with our pre-flight script and guide, then run our check script on the new server; we compare its report with the one from the old server. One per yearly server
Windows Server 2016 to 2025, done for you $249 one-off Data, user profiles and up to 5 apps, with a test checklist
Windows server move, done for you $199 one-off Data, user profiles, scheduled tasks and websites, and up to 3 apps
Larger jobs Quoted More data or apps than these limits, or several servers, quoted before any work starts

You bring your own Windows Server license for the new server and activate it, re-activate your apps' licenses, and test and sign off. Your old server keeps running until you sign off, and we delete nothing on it: we add only a temporary account, a working folder and a temporary firewall rule for the copy, and remove all three at sign-off. Moves are booked into weekly slots, and the date we confirm is the day we plan to start.

Every move price and step is in Server move, and yearly plan prices are on the pricing page. All our fixed-price services are listed on Server services. Questions before you order? Ask the sales team.

FAQ

Can I upgrade Windows Server 2016 to 2025 directly?

Yes, with Windows Server 2025 installation media. Microsoft's upgrade path table lists Windows Server 2016 to 2019, 2022 and 2025 as supported in-place upgrades for servers that are not clustered. For a server with the Remote Desktop Services role, Microsoft's RDS upgrade page still allows two versions per step, so plan a 2016 session host as two upgrades or a new server. Microsoft also advises against upgrading a domain controller in place.

Do I need a new Windows Server license to upgrade?

Yes. Microsoft says each Windows Server upgrade requires a separate license, with a valid product key and activation for the new version. On RyzenRDP the Windows Server license is not included in the plan price. Windows Server is installed for you but not activated, and you license and activate it yourself.

Can I upgrade Windows Server 2016 through Windows Update?

No. Microsoft offers the Windows Server 2025 feature update in Windows Update only to Windows Server 2019 and 2022 with the March 2026 cumulative update or later. A Windows Server 2016 server upgrades in place only from installation media.

Will an in-place upgrade keep my apps and data?

It is meant to. The "Keep files, settings, and apps" choice in Setup keeps them, but each app must support the new version. Microsoft requires a full backup with a restore test first, and on a Remote Desktop Session Host it says to uninstall apps before the upgrade and reinstall them after.

Windows Server 2022 vs 2025: which should I move to?

Windows Server 2025 for the longest support, to 14 November 2034, if your apps and your SQL Server version run on it. Windows Server 2022 if a 2016 session host must upgrade in place in one step. If more than two people sign in at once, every user or device that connects needs an RDS CAL of the chosen version or later. The 2022 or 2025 comparison table has the rest.

What happens to my Windows Server 2016 server after 12 January 2027?

It keeps running, but Microsoft lists 12 January 2027 as the end of extended support for Windows Server 2016 and releases no more security updates for it after that, unless you pay for Extended Security Updates, one year at a time, to 8 January 2030. See our Windows Server 2016 page.

Can you move my Windows Server 2016 VPS for me, and what does it cost?

Yes, to a RyzenRDP server, from any provider. Done for you, a move from Windows Server 2016 to Windows Server 2025 costs $249 one-off for data, user profiles and up to 5 apps. The assisted move is free with a yearly plan, one for each yearly server. Larger jobs are quoted before any work starts, and your old server keeps running until you sign off. You bring your own Windows Server license for the new server.

Sources

Read on 14 November 2026:

  1. Microsoft Learn: Plan your Windows Server upgrade path (supported paths, the four-version rule, restrictions, licensing; updated 14 April 2026)
  2. Microsoft Learn: Upgrade Windows Server in place (prerequisites, where installation media comes from, the Windows Update route and its registry value, Setup steps, logs after an upgrade; the former "Perform an in-place upgrade" page)
  3. Microsoft Learn: Log files and resolving upgrade errors (where setupact.log and setuperr.log are written in each Setup phase, including a rollback)
  4. Microsoft Learn: Upgrade and migrate roles and features in Windows Server (role matrix, Windows Server Migration Tools)
  5. Microsoft Learn: Upgrade Remote Desktop Services deployments (dated 3 July 2024) and Upgrading your Remote Desktop Session Host
  6. Microsoft Learn: Storage Migration Service overview
  7. Microsoft Learn: License Remote Desktop Services with client access licenses (CALs) (who needs a CAL, CAL version compatibility)
  8. Microsoft Learn: SMB security enhancements (SMB encryption on a share; clients that cannot encrypt are refused)
  9. Microsoft Learn command references: robocopy, Get-WindowsFeature, Install-WindowsFeature, Get-NetLbfoTeam, New-LocalUser, Remove-LocalUser, New-SmbShare, Remove-SmbShare, New-NetFirewallRule, Remove-NetFirewallRule, Test-NetConnection and Net use
  10. Microsoft Learn: Microsoft server applications compatibility for Windows Server, SQL Server 2025: Hardware and Software Requirements (updated 20 July 2026) and Copy databases with backup and restore (SQL Server)
  11. IIS.net: Web Deploy
  12. Microsoft Learn: lifecycle pages for Windows Server 2016, Windows Server 2022 and Windows Server 2025
  13. Microsoft Q&A: Windows Server 2016 in-place upgrade to Windows Server 2025 fails during system reboot (4 November 2026)

Run Windows Server on AMD Ryzen or AMD EPYC

Full Administrator access, Remote Desktop ready, set up instantly. Plans from $14.99/mo.