Windows VMs won't start because the GuestAgent extension can't be found

Sergey Borovoy 541 Reputation points
2021-10-13T07:13:46.46+00:00

Hi, I have a bunch of Windows Server 2019 VMs and they were working fine just yesterday, but this morning none of them can be started. Provisioning state becomes "failed" and the error message is "No version found in the artifact repository that satisfies the requested version '' for VM extension with publisher 'Microsoft.WindowsAzure.GuestAgent' and type 'CRPProd'"

So I called a colleague who also has a bunch of similar Windows Server VMs in a different subscription (created independently, those are not copies of my VMs) and he has the same problem.

Looks like some kind of Azure outage, GuestAgent extension became inaccessible? On the other had, I'm worried about the fact that the requested version is shown as an empty string. If this is what my VM requests for some reason, no wonder it can't find it.

The region is Western Europe, in case it matters.

Tried googling the error message, nothing really useful.

I'll appreciate your help.

Azure Virtual Machines
Azure Virtual Machines

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

Windows for business | Windows Server | User experience | Other

130 answers

Sort by: Most helpful
  1. Gytautas Buivydas 1 Reputation point
    2021-10-13T08:11:35.377+00:00

    Same issue in US East

    Was this answer helpful?

    0 comments No comments

  2. Massimo Pascucci 1 Reputation point
    2021-10-13T08:02:02.387+00:00

    Confirmed on multiple customer subscriptions (I work for an IT consulting company and several of our customers are impacted); happens across multiple regions, too.

    Was this answer helpful?

    0 comments No comments

  3. tjoachimi 1 Reputation point
    2021-10-13T07:58:15.663+00:00

    Having the same issue in Eastern US. I've checked the Azure Status page and Microsoft is saying that everything is working normally.

    Was this answer helpful?

    0 comments No comments

  4. Craig Pattison 1 Reputation point
    2021-10-13T07:43:49.217+00:00

    Same for me. 3 x Windows Server 2016 machines in UK West and UK South.

    Was this answer helpful?

    0 comments No comments

  5. YOGESH YADAV 1 Reputation point
    2021-10-13T07:42:03.6+00:00

    We are also facing the same error message while starting the virtual machine. Tried to start the VMs belong to multiple regions (Central India, Southeast Asia, West US 2) , different tenants, but no luck.

    Please let us know if someone has update on this.

    Was this answer helpful?

    0 comments No comments

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.