My VM's OS disk crashed and it restarted unexpectedly on its own, and now it is NOT turning on

Question

My VM's OS disk crashed and it restarted unexpectedly on its own, and now it is NOT turning on

Bhavesh Ved 0

Today morning around 9.30 am IST, My Azure Virtual machine's OS crashed unexpectedly and it restarted on its own. After that it is not booting up, in the notifications it just shows VM is starting but it never starts, I have been facing this issue and trying to troubleshoot it fro the past 2 hour or so. I am also seeing an issue with my VM which is also a question I am trying to find out the answer for. Posting the supported images for reference. User's image

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-12T18:31:43.4933333+00:00

Hello @Bhavesh Ved,

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!
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T10:11:52.0733333+00:00

Hello @Bhavesh Ved,

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.

3 answers

Your answer

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-12T18:31:43.4933333+00:00

Hello @Bhavesh Ved,

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!
Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T10:11:52.0733333+00:00

Hello @Bhavesh Ved,

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 @Bhavesh Ved,

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

Bhavesh Ved 0

@Nikhil Duserla : Yes. Issue got resolved after we changed the VM configuration from 2 cpu to 4 cpu. Thank you.

Nikhil Duserla 7,935 Reputation points Microsoft External Staff Moderator

2025-06-19T10:25:12.77+00:00

Hello @Bhavesh Ved,

Thank you for letting us know that the issue has been resolved. If the answer helped you resolve the issue, please consider accepting it.

Answer 3

Bhavesh Ved 0

Yes. Issue got resolved when we changed the VM configuration. We got to know about Microsoft issue related to firmware misconfiguration much later. It would have been good if such information was made available to us in time. We lost half a day of productivity of my team.

Share via

My VM's OS disk crashed and it restarted unexpectedly on its own, and now it is NOT turning on

3 answers

Your answer