How to start my Windows VM after Failed to start, failed to reapply, and failed to redeploy

Question

When trying to start the VM it remains a long time and finish with "... did not start in the allotted time. The VM may still start successfully. Please check the power state later.". Try troubleshooting with redeploy and reapply, but nothing worked.

Answer 1

Hello @sebastianfelix,

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

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!

Answer 3

Finally, something was released. Just in case people are still having issues with the v6 VM's.

Service: Virtual Machines

Region: East US, West US 2, West US 3, Canada Central, UK South, Central US, Central India, East US 2 EUAP, East Asia, West Europe, Central US EUAP, West Central US, North Europe, Australia East

Event tags: --

Impact Statement: Starting at 04:00 UTC on 07 June 2025, you have been identified as a customer using v6 Virtual Machines (VMs), who may experience failures when attempting to start or reboot v6 Virtual Machines with the trusted launch feature.

 

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.

 Alternatively, customers can mitigate this issue by deleting the VM and recreating the VM.

Current Status: A software issue has been identified affecting a subset of v6 Virtual Machines with trusted launch. A hotfix has been deployed, which has resolved the issue for newly created v6 VMs. However, some existing v6 Virtual Machines may still be affected. We are currently exploring additional mitigation strategies and coordinating efforts to ensure resolution. We continue to closely monitor the situation and will provide additional information within the next 8 hours, or as events warrant.

0 commentsNo commentsReport a concern