Perform an in-place upgrade of Windows Server

You can use an in-place operating system upgrade (a feature update) to go from an older operating system to a newer one while keeping your settings, server roles, and data intact. This article shows you how to move to a later version of Windows Server using installation media.

Prerequisites

Before you start upgrading, complete the following prerequisites:

• The setup media for the version of Windows Server that you want to upgrade to.
  • For information about available Windows Server versions and supported upgrade paths, see Which version of Windows Server should I upgrade to?.
  • You can obtain setup media for your target version of Windows Server from an original equipment manufacturer (OEM), a retail distribution channel, a Visual Studio subscription, and the Microsoft 365 admin center.
• A valid product key and activation method. Keys and methods can vary depending on the distribution channel you receive Windows Server media from. Examples of channels include a Commercial Licensing program, a retail channel, or an OEM.
• A location to store files away from your computer, such as a USB flash drive or network location.
• Knowledge of:
  • The roles and features that support an in-place upgrade. See Upgrade and migrate roles and features in Windows Server.
  • The Microsoft server applications that are supported on Windows Server. See Microsoft server applications compatibility for Windows Server.
  • Any non-Microsoft application vendor support requirements.
• A computer that:
  • Meets or exceeds the hardware requirements for Windows Server.
  • Isn't running in Azure.
  • Isn't clustered. If you're running a cluster, instead use the Cluster-Aware Updating feature or a cluster operating system rolling upgrade.
• A full backup of your computer. The backup should include the operating system, apps, data, and any VMs running on the server. You can use Windows Server Backup or a partner backup solution.

Collect diagnostic information

We recommend that you collect some information from your devices for diagnostic and troubleshooting purposes in case the feature update is unsuccessful. We also recommend you store the information somewhere you can access even if your device is unavailable.

To collect your information:

1. Open an elevated PowerShell prompt, make a note of your current directory, and run the following commands:

   Get-ComputerInfo -Property WindowsBuildLabEx,WindowsEditionID | Out-File -FilePath .\computerinfo.txt
   systeminfo.exe | Out-File -FilePath systeminfo.txt
   ipconfig /all | Out-File -FilePath ipconfig.txt
   

   Tip

   The Get-ComputerInfo command requires PowerShell 5.1 or later. If your Windows Server version doesn't include PowerShell, you can look in the registry for the information that the Get-ComputerInfo command returns:

   1. Open Registry Editor.
   2. Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion key.
   3. Copy the Windows Server BuildLabEx and EditionID values.

2. Open File Explorer, go to the directory you noted down, and copy the files to a USB flash drive or network location off your computer.

After you collect your Windows Server-related information, we recommend that you back up your server operating system, apps, and VMs. You must also shut down, quick migrate, or live migrate any VMs currently running on the server. You can't have any VMs running during the feature update.

Perform the in-place upgrade

In this section, you use Windows Server Setup to select the settings for the in-place upgrade. Windows Server Setup uses these settings to update your version of Windows Server. During the update, your computer restarts several times.

To perform the in-place upgrade:

1. Open File Explorer, go to the Windows Server Setup media, and then open setup.exe. If you're using removal media, the file path might be D:\setup.exe.

   Important

   Depending on your security settings, the User Account Control dialog might prompt you to allow the setup to make changes to your device. If you agree to the conditions, select Yes.

2. By default, the setup automatically downloads updates for the installation. If you're okay with the default settings, select Next to continue.

   If you don't want the setup to automatically download updates, select Change how Setup downloads updates, select the option that's appropriate for your environment, and then select Next.

3. If prompted, enter your product key, and then select Next.

4. Select the edition of Windows Server you want to install, and then select Next.

5. Review the applicable notices and license terms. If you agree to the terms, select Accept.

6. To do an in-place upgrade, select Keep files, settings, and apps, and then select Next.

7. After the setup finishes analyzing your device, it displays the Ready to install screen. To start the in-place upgrade, select Install.

The in-place upgrade starts, and the progress is displayed on the screen. After the in-place upgrade finishes, your server restarts.

Check your in-place upgrade

When the in-place upgrade to Windows Server is complete, take the following steps to make sure the upgrade was successful:

1. Open an elevated PowerShell prompt. Run the following command to verify that the version and edition match the media and values you selected during setup.

   Get-ComputerInfo -Property WindowsProductName
   

2. Make sure all your applications are running and that your client connections to the applications are successful.

If your computer isn't working as expected after the feature update and you need technical assistance, you can contact Microsoft Support.

Related content

The following articles can help you prepare for and use your new Windows Server version:

• Install or uninstall roles, role services, or features
• Windows Server management overview
• Get started with Windows Admin Center
• Key Management Services (KMS) activation planning
• Activate using Active Directory-based activation

To learn more about deployment and post-installation configuration and activation options, see the Windows Server deployment, configuration, and administration learning path.