VM will not start/stop/reapply/redeploy

MM 0 Reputation points
2026-09-17T14:10:57.8566667+00:00

I'm unable to start a VM. In my attempt to start it, I've tried to manually start/stop/reapply/redeploy via the website and also via CLI. The errors generally include some sort of generic internal message, but also include something that I haven't seen before regarding a "Madari delete context selector". Anyone have any ideas how I can get this VM back up and running? It's possible this is just an Azure issue and there is nothing I can do, but they don't say there is a service outage or issue anywhere. I can't even communicate with Microsoft unless I pay for a support plan (which is wild that I have no recourse to submit a ticket for their failures without paying them more money and if past support tickets are similar they probably won't do anything).

Here is the error when attempting to reapply (with some information removed where brackets are):

az vm reapply --resource-group [ResourceGroup] --name [VM_Name]

(InternalExecutionError) Madari delete context selector /vms/[GUID] operation failed.

Code: InternalExecutionError

Message: Madari delete context selector /vms/[GUID] operation failed.

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 9,575 Reputation points
    2026-09-17T14:26:22.6933333+00:00

    Hi @MM

    The "Madari delete context selector" message isn't a publicly documented Azure VM error that I can find, so don't try to troubleshoot that component directly.

    More importantly, you're seeing failures across Start/Stop/Reapply/Redeploy, and even az vm reapply is returning:

    InternalExecutionError

    Madari delete context selector /vms/[GUID] operation failed.

    Use Reapply when a VM is stuck in a failed provisioning state, followed by Redeploy if Reapply doesn't resolve it. Since both operations are failing in your case, this points more toward an Azure Compute control-plane/backend issue than something you can repair from inside the guest OS.

    Before escalating, capture the failed operation from VM → Activity log and save the timestamp, correlation ID, operation ID, error code, and full error details. Also check VM → Resource health for any platform event.

    You can also get the current instance/provisioning state with:

    az vm get-instance-view \
  --resource-group <ResourceGroup> \
  --name <VMName> \
  --query "instanceView.statuses"

    If possible, post that output here with identifying information removed.

    At this point, don't delete the VM, detach disks, or start rebuilding it until you understand the control-plane failure, especially if the VM contains data you need.

    Regarding support: because this appears to involve an Azure platform operation failing internally, try Help + support → Create a support request and select the affected VM/subscription. Include the exact InternalExecutionError plus the correlation/operation IDs, and explain that Reapply and Redeploy themselves fail, so the documented recovery paths cannot complete.

    References:

    VM stuck in a failed state

    Redeploy a VM to a new Azure node

    Troubleshoot VM restart and redeployment errors

    If you can share the Activity Log failure details for one of the failed operations, particularly the correlation ID and inner error with sensitive information removed, we may be able to narrow it down further.

    Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.