Windows VM won't start

Question

I have a Windows Server 20222 VM that overnight crashed and now is unable to start again.

From what I can tell, it is related to the agent which is reporting "not ready".

I am getting the following error when attempting to redeploy

    "submissionTimestamp": "2025-06-11T09:28:31Z",
    "subscriptionId": "ec487679-8cea-4206-a50c-ea9218fe2651",
    "tenantId": "98a61d6d-690e-4fad-8954-8d7915c69662",
    "properties": {
        "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"VMStartTimedOut\",\"message\":\"VM 'Airbus' did not start in the allotted time. The VM may still start successfully. Please check the power state later.\"}]}}",
        "eventCategory": "Administrative",
        "entity": "/subscriptions/ec487679-8cea-4206-a50c-ea9218fe2651/resourceGroups/concorde/providers/Microsoft.Compute/virtualMachines/Airbus",
        "message": "Microsoft.Compute/virtualMachines/start/action",
        "hierarchy": "98a61d6d-690e-4fad-8954-8d7915c69662/dev-mg/ec487679-8cea-4206-a50c-ea9218fe2651"

and a similar error when attempting to reapply. I'm not really sure where to go from here.

    "submissionTimestamp": "2025-06-11T10:10:37Z",
    "subscriptionId": "ec487679-8cea-4206-a50c-ea9218fe2651",
    "tenantId": "98a61d6d-690e-4fad-8954-8d7915c69662",
    "properties": {
        "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"VMStartTimedOut\",\"message\":\"VM 'Airbus' did not start in the allotted time. The VM may still start successfully. Please check the power state later.\"}]}}",
        "eventCategory": "Administrative",
        "entity": "/subscriptions/ec487679-8cea-4206-a50c-ea9218fe2651/resourceGroups/concorde/providers/Microsoft.Compute/virtualMachines/Airbus",
        "message": "Microsoft.Compute/virtualMachines/Reapply/action",
        "hierarchy": "98a61d6d-690e-4fad-8954-8d7915c69662/dev-mg/ec487679-8cea-4206-a50c-ea9218fe2651"

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

Move from the v6 Machines to the v4 or v5 machines.

d4sb should do the trick if you get a disk controller error.