My Windows 11 Pro Vm was deprecated - please provide instructions as to how I can restore the image that was created prior to deprecation

Karl Pozmann 40 Reputation points
2026-08-26T11:43:44.4533333+00:00

Here is the latest analysis showing the current state of the Windows VM Adastra - Looks like an upgrade to Standard_DC4ads_V5 is needed - after that how can the image be restored from prior to deprecation? Note that the current VM cannot be started so no further diagnostics are available

Root Cause Analysis Summary: The Virtual Machine (VM) "AdAstra" is currently not running because it was explicitly stopped and deallocated by a user action, which is why it is in an "Unavailable" state. Attempts to start the VM were met with a "Conflict" error, suggesting conflicting actions or constraints at the time of starting. The provisioning state of the VM is "Succeeded", implying no provisioning-related issues.

A critical issue is present with the VM's AmdGpuDriverWindows extension, which is in a "Failed" provisioning state. The VM's operating system and security configurations are normal, with Windows 11 version 22H2 Pro installed, Trusted Launch enabled, and automatic updates turned on.

To address these issues:

  1. Start the VM to perform further diagnostics.
  2. Troubleshoot the AmdGpuDriverWindows extension by checking Azure Activity Logs or VM Extension logs for specific errors. Disabling or reinstalling the extension might be considered if it is not critical for your use case.
  3. Review recent user actions or automated processes that might have stopped the VM to prevent recurrence.
  4. Investigate any resource dependencies or constraints that could be causing the conflict error during VM start attempts. If unresolved, seek assistance from Azure Support for further guidance.

Azure CLI command (Manual)

You can copy and run the following Azure CLI command(s) in the cloud shell:

 

az account set --subscription 71801194-822f-4507-aa04-2fca7d75ca0c

az stack-hci-vm start --name AdAstra --resource-group AdAstra 

 

After selecting the question mark at the top:

 

Root Cause Analysis Summary: The virtual machine (VM) "AdAstra" in the resource group "AdAstra" is not starting because it is currently powered off, which prevents further diagnostics from being run. Additionally, a conflict error (HTTP Status Code: 409) was detected, indicating that the VM is in a deallocated state due to resource availability issues. This error often occurs when Azure's infrastructure cannot allocate enough resources for the requested VM size in the specified availability zone, particularly when there is high demand or limited capacity.

The VM is configured with the "Standard_DC4s_v2" size, which could be facing capacity constraints. To address this, you can try starting the VM in a different availability zone, resizing it to a different size, or waiting for off-peak hours when more resources might become available. There are no issues with the VM's configuration or provisioning state, and resolving the resource allocation constraints should enable the VM to start successfully.

For additional guidance, you can refer to the Azure documentation on VM allocation failures: Azure VM allocation failures

.

Azure CLI commands (Manual)

You can copy and run the following Azure CLI command(s) in the cloud shell:

 

az account set --subscription 71801194-822f-4507-aa04-2fca7d75ca0c

az vm show --resource-group AdAstra --name AdAstra --query hardwareProfile.vmSize

az vm list-vm-resize-options --resource-group AdAstra --name AdAstra --query [].name

az vm resize --resource-group AdAstra --name AdAstra --size Standard_D4s_v3

az vm start --resource-group AdAstra --name AdAstra

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

Answer accepted by question author
Jose Benjamin Solis Nolasco 12,201 Reputation points Volunteer Moderator
2026-08-26T13:17:31.28+00:00

Welcome to Microsoft Q&A!

Hello Karl,

 

You dont need to retore your image Your data, operating system, and applications are perfectly safe.

 

In Azure, the compute hardware (the VM size) and the storage (the OS disk) are decoupled. The "deprecation" and the HTTP 409 Conflict error you are seeing simply mean that Azure currently lacks the physical capacity to allocate your specific VM size (Standard_DC4s_v2) in your current availability zone.

 

When you resize the VM, Azure simply unplugs your existing, fully intact OS disk and attaches it to a newer, available physical server (such as Standard_DC4ads_v5 or Standard_D4s_v3). All your files remain exactly as they were the moment the VM was shut down.

Step 1: Resize the VM to bypass the 409 Error

Since the VM is already in a stopped (deallocated) state, it is in the perfect condition to be resized:

  1. Go to the Azure Portal and navigate to your AdAstra virtual machine.

 

  1. In the left-hand menu, under Settings, select Size.

 

  1. Search for and select the new size you want to use (such as Standard_DC4ads_v5 or Standard_D4s_v3).

 

  1. Click the Resize button at the bottom of the screen.

 

  1. Once the resize operation completes successfully, click Start on the VM overview page.

 

Step 2: Clear the Failed Extension

The root cause analysis noted a failed AmdGpuDriverWindows extension. The Standard_DC and Standard_D series do not have physical GPUs, so the extension is failing because it cannot find an AMD GPU to install drivers for.

 

Once the VM is running, you should remove this extension to clear the error state:

  1. On the VM page in the Azure Portal, go to Settings > Extensions + applications.

 

  1. Locate the AmdGpuDriverWindows extension.

 

  1. Select it and click Uninstall.

 

References:

 

 

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.