Steps for in-place system upgrades for supported Windows 10 Azure VMs and workarounds for unsupported versions
This article describes how to do an in-place system upgrade of supported Windows 10-based Azure virtual machines (Azure VMs). This article also describes workarounds for Azure VMs that are not supported for in-place system upgrades.
Original product version: Windows Server version 1709, Windows Server version 1803, Windows 10, version 1709, all editions, Virtual Machine running Windows, Windows Server 2016, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Datacenter, Windows 10, Windows 8.1, Windows 7 Enterprise, Windows 10, version 1803, all editions, Windows Server version 1803
Original KB number: 4014997
Consider the following scenario:
- You have a virtual machine (VM) that is running Windows in a Microsoft Azure environment.
- You run an in-place upgrade of the VM to a newer version of the operating system.
In this scenario, the upgrade may fail or become blocked and require direct console access.
In-place system upgrades are supported for specific versions of Azure Windows VMs. We’re working to broaden support of in-place system upgrade (as a Feature Update) to other versions soon.
Windows versions supported for in-place system upgrades:
- Windows 10 single-session, all editions, all versions
- Windows 10 Enterprise multi-session, all versions
Windows versions not yet supported for in-place system upgrades (consider using a workaround):
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2 Datacenter
- Windows Server 2012 R2 Standard
- Windows Server 2012 Datacenter
- Windows Server 2012 Standard
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Standard
- Windows 8.1
- Windows 7 Enterprise
- Windows Server, version 1709
- Windows Server, version 1803
In-place system upgrade process for a Windows 10 VM
This process requires 45-60 minutes to complete and for the VM to restart. To do the in-place system upgrade, follow these steps:
Verify that the Windows 10 VM has at least 2 GB of RAM, and 12 GB of free disk space on the system disk.
Check whether the backup was successful. To do so, turn off the original Windows 10 VM. Verify that a new VM can be successfully restored from the backup, and that all applications are running successfully.
Either the original Windows 10 VM or the restored VM can be used as a source for in-place system upgrade. But both VMs can’t be running at the same time, unless the system name of the VM and the IP addresses on one of the VMs was changed to prevent conflicts.
Connect to the Windows 10 VM, and go to Settings > Updates & Security > Windows Update.
In Windows Update, select Check for updates.
When the Feature Update item appears, select Download and install now.
The update will download and install. User settings and data will be preserved, and the VM will restart automatically.
If you have general questions about this procedure, post to Microsoft Q&A and add the
azure-virtual-machines tag to your question.
To work around this issue, create an Azure VM that's running a supported version. And then either migrate the workload (Method 1, preferred), or download and upgrade the VHD of the VM (Method 2).
Method 1: Deploy a newer system and migrate the workload
Create an Azure VM that runs a supported version of the operating system, and then migrate the workload. To do so, you will use Windows Server migration tools. For instructions to migrate Windows Server roles and features, see the following article:
Method 2: Download and upgrade the VHD
Step 1: Do an in-place upgrade in a local Hyper-V VM
- Download the VHD of the VM.
- Attach the VHD to a local Hyper-V VM.
- Start the VM.
- Run the in-place upgrade.
Step 2: Upload the VHD to Azure
Follow the steps in the following article to upload the VHD to Azure and to deploy the VM.
Method 3: Request to join Azure VM Upgrade Preview
If you’re interested in upgrading an operating system version that’s not yet supported, you may join a Private or Public Preview program, depending on capacity and availability. Email your request to firstname.lastname@example.org.