Windows Standard E2ads v6 Update Loop Issue

Question

Windows Standard E2ads v6 Update Loop Issue

Jacob Eberhart 0

Experiencing an issue with a Windows Standard E2ads v6 (2 vCPUs, 16 GiB memory) VM that is stuck in an update loop, cycling through "starting > updating > failed."

Access was successful yesterday (6/10) via RDP, but today the machine cannot complete updates. Attempts to restore backups from previous days result in the same issue, making the system unresponsive.

Is there a known outage or systemic issue affecting this configuration?

Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2025-06-11T21:29:40.1533333+00:00

Hi Jacob Eberhart,

It doesn’t look like there’s a known or widespread outage affecting your Windows Standard E2ads v6 (2 vCPU, 16 GiB) VM configuration.

Instances frequently get stuck in update loops due to insufficient disk space. Azure VMs specifically tend to declare a failed update if the system or data disks are full, Resize the OS/data disk(s) to a larger size, then restart the VM.
You can use the Redeploy feature from the Azure portal. Redeploying moves the VM to a new Azure host, while preserving all the VM’s configurations and data. https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/vm-stuck-in-failed-state?tabs=portal
If your VM never boots correctly—even from restored backups—the underlying VHD may be damaged or missing corrupted update files. Create a new VM from the existing OS disk snapshot without attaching the old VM’s configuration or retain your data disks but build a fresh Windows VM and migrate only the data.

If you have any further queries, let me know. If the information is helpful, please click on Upvote.
Jacob Eberhart 0 Reputation points

2025-06-12T12:55:25.99+00:00
Thanks Anusree! I contacted Azure support and there is an issue with the v6 version of E2ads, we:

Did a full disk snapshot

Made a vm based on the snapshot

Changed the redundency zone

Checked for versions 5 and below of E2ads

Set up a similar VM size to E2ads, and it was a v3

Moved the public IP address to the new vm

It solved the issue.
Evan Schulte 0 Reputation points

2025-06-12T14:15:46.6966667+00:00

We are having this same exact issue, also in US East - but we are using D series VM's so this does not appear to be isolated to only E series. We were running a v6 VM for months, and suddenly on the morning of 6/11 it rebooted and did not come back up (stuck in boot loop). After creating a new v6 VM we were able to remote into it, however if it rebooted for any reason it would be stuck in a boot loop. In one instance it even seemingly rebooted itself.

This has been a huge headache for both us and our customers. Our team has spent the last 24 hours remediating the same server 3 times until we finally realized it was the VM generation causing it so we switched to v5.
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T09:54:32.87+00:00

Hello @Jacob Eberhart,

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.

1 answer

Your answer

Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2025-06-11T21:29:40.1533333+00:00

Hi Jacob Eberhart,

It doesn’t look like there’s a known or widespread outage affecting your Windows Standard E2ads v6 (2 vCPU, 16 GiB) VM configuration.

Instances frequently get stuck in update loops due to insufficient disk space. Azure VMs specifically tend to declare a failed update if the system or data disks are full, Resize the OS/data disk(s) to a larger size, then restart the VM.
You can use the Redeploy feature from the Azure portal. Redeploying moves the VM to a new Azure host, while preserving all the VM’s configurations and data. https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/vm-stuck-in-failed-state?tabs=portal
If your VM never boots correctly—even from restored backups—the underlying VHD may be damaged or missing corrupted update files. Create a new VM from the existing OS disk snapshot without attaching the old VM’s configuration or retain your data disks but build a fresh Windows VM and migrate only the data.

If you have any further queries, let me know. If the information is helpful, please click on Upvote.
Jacob Eberhart 0 Reputation points

2025-06-12T12:55:25.99+00:00

Thanks Anusree! I contacted Azure support and there is an issue with the v6 version of E2ads, we:

Did a full disk snapshot

Made a vm based on the snapshot

Changed the redundency zone

Checked for versions 5 and below of E2ads

Set up a similar VM size to E2ads, and it was a v3

Moved the public IP address to the new vm

It solved the issue.
Evan Schulte 0 Reputation points

2025-06-12T14:15:46.6966667+00:00

We are having this same exact issue, also in US East - but we are using D series VM's so this does not appear to be isolated to only E series. We were running a v6 VM for months, and suddenly on the morning of 6/11 it rebooted and did not come back up (stuck in boot loop). After creating a new v6 VM we were able to remote into it, however if it rebooted for any reason it would be stuck in a boot loop. In one instance it even seemingly rebooted itself.

This has been a huge headache for both us and our customers. Our team has spent the last 24 hours remediating the same server 3 times until we finally realized it was the VM generation causing it so we switched to v5.
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T09:54:32.87+00:00

Hello @Jacob Eberhart,

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 @Jacob Eberhart,

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.

Share via

Windows Standard E2ads v6 Update Loop Issue

1 answer

Your answer