My VM is down due to host server issue

Question

Today my Windows VM is down and inaccessible due to the following error:

Unavailable (Unplanned) : Redeploying due to host failure (Unplanned)

---

At Wednesday, June 11, 2025 at 3:15:23 AM EDT, the Azure monitoring system received the following information regarding your Virtual machine: We're sorry, your virtual machine isn't available and it is being redeployed due to an unexpected failure on the host server. Azure has begun the auto-recovery process and is currently starting the virtual machine on a different host. No additional action is required from you at this time. Recommended Steps

• Check back here for status updates

Since this error, it is in a repeated loop of the OS crashing and restarting with the following errors:

Machine crashed (Customer Initiated)

---

At Wednesday, June 11, 2025 at 10:55:22 AM EDT, the Azure monitoring system received the following information regarding your Virtual machine: The Virtual Machine is undergoing a reboot due to a guest OS crash. The local data remains unaffected during this process. No other action is required at this time.

Reboot initiated from inside the machine (Customer Initiated)

---

At Wednesday, June 11, 2025 at 10:55:22 AM EDT, the Azure monitoring system received the following information regarding your Virtual machine: The Virtual Machine is undergoing a reboot as requested by a restart action triggered by an authorized user or process from within the Virtual Machine. No other action is required at this time.

How can I get this resolved?

Answer 1

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

Answer 2

Hello @Tracy Gough,

I’m currently checking with our team regarding this issue. In the meantime, please try the following steps:

If your VM is stuck in the Updating state, unable to restart or not able to access, try restarting it through the Azure Portal or use PowerShell to refresh its state.

If the VM is still not running after a restart, consider redeploying it from the Azure Portal.

If you're currently using a v6-series VM, try resizing it to a v4 or v5 series and then verify whether the VM is running.

Additionally, make sure that TPM (Trusted Platform Module) is disabled, as this could impact the VM's functionality and check the VM status.

Note-

If you have resized the VM size or disk configuration, try reverting to the previous size after a few hours to see if that resolves the issue.

Thank you!