Azure VM stuck in updating status

Question

Azure VM stuck in updating status

matt sanders 0

Hello, I am new to the VM world. My VM is stuck in updating status and I have tried stopping and starting again, redeploying/reapplying with no luck.

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-11T12:48:25.14+00:00

Hello @matt sanders,

Additionally, have you made any recent changes? When was the last time the VM was running? Please also provide the VM type and location you are using.

Kindly review the activity logs and share them via private message for a better understanding of the issue.
matt sanders 0 Reputation points

2025-06-11T12:52:19.93+00:00

Thank you for the help! I have sent the activity log. Last time I used was 6 days ago. I did not make any recent changes other than trying to troubleshoot the updating issue.
matt sanders 0 Reputation points

2025-06-11T13:00:26.58+00:00

I will leave the VM updating for 8 hours and see what happens. I have the activity log if you could private message me please.
Palmer Wilson 80 Reputation points

2025-06-11T16:25:55.16+00:00
Experiencing the same issue.

Windows updates restarted the VM around midnight last night and the VM status remained in the "Updating" state until we revisited it around 8:00AM. This means we gave it the recommended 8 hours. These are the steps we have taken so fare:

Several reboot attempts

"In Place" restore from a backup from yesterday.

"In Place" restore from Monday

VM Redeploy

All of these attempts just result in the VM trying to start and then going back into the "Updating" status.

We are attempting a new deployment from backup instead of in place now and opening ticket to get the ball rolling for support.

Some info on the VM: Location: East US (Zone 1) Size: Standard D8as V6 VM: Generation V2 Source Image: 2022-datacenter-azure-edition

Additionally, the boot diagnostics is not producing any screenshots or serial logs on starting attempts.

The last screenshot provided by the boot diagnostics was a windows update image prior to rebooting itself around midnight.

Posted same response to another thread with the same issue this morning:
https://learn.microsoft.com/en-us/answers/questions/2282911/impossible-to-connect-to-an-azure-virtual-machine
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T09:51:34.7333333+00:00

Hello @matt sanders,

Checking to see whether you have resolved the issue with the solution provided above, or if you need any further assistance, please let us know. We are happy to help.

4 answers

Your answer

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-11T12:48:25.14+00:00

Hello @matt sanders,

Additionally, have you made any recent changes? When was the last time the VM was running? Please also provide the VM type and location you are using.

Kindly review the activity logs and share them via private message for a better understanding of the issue.
matt sanders 0 Reputation points

2025-06-11T12:52:19.93+00:00

Thank you for the help! I have sent the activity log. Last time I used was 6 days ago. I did not make any recent changes other than trying to troubleshoot the updating issue.
matt sanders 0 Reputation points

2025-06-11T13:00:26.58+00:00

I will leave the VM updating for 8 hours and see what happens. I have the activity log if you could private message me please.
Palmer Wilson 80 Reputation points

2025-06-11T16:25:55.16+00:00

Experiencing the same issue.

Windows updates restarted the VM around midnight last night and the VM status remained in the "Updating" state until we revisited it around 8:00AM. This means we gave it the recommended 8 hours. These are the steps we have taken so fare:

Several reboot attempts

"In Place" restore from a backup from yesterday.

"In Place" restore from Monday

VM Redeploy

All of these attempts just result in the VM trying to start and then going back into the "Updating" status.

We are attempting a new deployment from backup instead of in place now and opening ticket to get the ball rolling for support.

Some info on the VM: Location: East US (Zone 1) Size: Standard D8as V6 VM: Generation V2 Source Image: 2022-datacenter-azure-edition

Additionally, the boot diagnostics is not producing any screenshots or serial logs on starting attempts.

The last screenshot provided by the boot diagnostics was a windows update image prior to rebooting itself around midnight.

Posted same response to another thread with the same issue this morning:
https://learn.microsoft.com/en-us/answers/questions/2282911/impossible-to-connect-to-an-azure-virtual-machine
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T09:51:34.7333333+00:00

Hello @matt sanders,

Checking to see whether you have resolved the issue with the solution provided above, or if you need any further assistance, please let us know. We are happy to help.

Answer 1

Hello @matt sanders,

If your VM remains stuck in the "Updating" status, start by restarting it via the Azure Portal or using PowerShell commands to refresh its state. If the problem persists, check for potential disk space issues or try removing specific directories related to the VM's extensions before restarting the agent.

A Windows VM doesn't start. When you check the screenshots in the Boot diagnostics window, you see that the startup is stuck in the update process.

Depending on the number of updates that are getting installed or rolled backing, the update process can take a while. Leave the VM in this state for 8 hours. If the VM is still in this state after that period, restart the VM from the Azure portal, and see if it can start normally. If this step doesn't work, try the following solution- https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-stuck-updating-boot-error?source=recommendations

I would recommend check the logs and metrics to identify any specific errors or issues that could be causing the VMs to be stuck in an unknown or updating state.

If you have any further queries, do let us know.

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-17T17:40:46.1333333+00:00

Hello @matt sanders,

Thank you for your patience while we investigated the issue. Our team has confirmed that it has now been fully resolved.

The root cause was identified as a firmware misconfiguration in Underhill VMs, which resulted in TPM-related file corruption and VM failures. A hotfix has been applied to prevent this issue in all newly created v6 VMs. For existing affected VMs, the recommended steps are to either disable the vTPM and restart the VM or recreate the VM.

A permanent fix was deployed on June 16, 2025, at 4:00 AM UTC. Customers have been informed and can now safely re-enable the vTPM where applicable.

Answer 2

Blake Turner 15

We experienced the same issue earlier this morning. If you're currently using a v6-series VM, try resizing it to a v4 or v5 series instead. That resolved the issue for us, and the machine came back online shortly after the change.

If this resolved your issue please mark it the correct answer!

Palmer Wilson 80 Reputation points

2025-06-11T19:59:47.2966667+00:00

Yep you nailed it. Finally got a response from support:

After further investigation and internal discussions, we have identified the root cause:

Microsoft Azure team has completed its investigation into the recent v6 SKU VM start failures. The root cause was traced to a newly deployed underlying module update for the hypervisor on host nodes. This update inadvertently triggered a TPM issue, which resulted in failures when attempting to start VMs

Answer 3

@matt sanders I hope you are doing Well,

When there are multiple thread updating the same internal resource, the code take a lock to avoid saving conflict, please follow this steps:

Check for any locked resources
- Go to Resource Group > Locks.
- Remove any ReadOnly or Delete locks that might be blocking updates.
Activity Log & Notifications
- In the Azure portal, go to your VM > Activity log.
- Look for failed operations related to “Update Virtual Machine” or “Write Virtual Machine”.

Create a support ticket with Microsoft:

Go to Help + support > New support request in the Azure portal.

Choose category: Virtual Machines (IaaS) > Issue type: VM stuck in updating.

Please try to follow this procedure too https://techcommunity.microsoft.com/discussions/compute/azure-vms-stuck-at-status-unknown-or-updating-solution/3821385

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

Answer 4

Jean Van Iddekinge 0

Having the same issue with my Azure VM today.

SKU is Standard D4ds v6 (4 vcpus, 16 GiB memory)

HAs been suck in updating status for over 4 hours now, I have been using Azure VM's for years and updates take 30 minutes max so this is definitely something up with Azure.

Palmer Wilson 80 Reputation points

2025-06-12T16:41:08.4066667+00:00
Azure recognized the issue with Version 6 VMs yesterday. Their current suggestion is:

Workaround: Customers can mitigate the issue by disabling the vTPM and restarting the VM. Please follow the below steps to disable the vTPM:

Sign in to the Azure portal.

Navigate to the affected Virtual Machine Resource.

Expand the "Settings", navigate to "Configuration".

Under the "Security Type", uncheck the "Enable vTPM" checkbox. After you make the changes, select Save.

Share via

Azure VM stuck in updating status

4 answers

Your answer