In-place upgrade for supported VMs running Windows in Azure
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 aren't supported for in-place system upgrades. For Azure VMs running Windows Server, see In-place upgrade for supported Windows Server VMs.
Looking for Windows Server?
For the in-place system upgrade procedure for virtual machines that are running Windows Server, see In-place upgrade for VMs running Windows Server in Azure.
Original product version: Windows 10, version 1803, all editions, Windows 10, version 1709, all editions, Virtual Machine running Windows, Windows 10, Windows 8.1, Windows 7 Enterprise
Original KB number: 4014997
Consider the following scenario:
- You have a virtual machine (VM) that's 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
It's not currently possible to upgrade an existing virtual machine that's running Windows 10 Professional or Enterprise to Windows 10 Enterprise multi-session.
Windows versions not yet supported for in-place system upgrades (consider using a workaround)
- Windows 8.1
- Windows 7 Enterprise
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 doesn't use Ephemeral OS Disk. This feature is currently not supported.
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 this, 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. Download and upgrade the VHD of the VM.
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.