Share via

Remote machine provider reported: The configuration 'windows-2019-vs2019-uk-default' is not supported

Steve Hodgkiss 20 Reputation points
2026-02-10T11:58:25.2633333+00:00

When attampting to deploy a code change (Builds ok with no errors) the deployment is stopped and the error message below is presented in the logs - how do I identify where the 2019 configurastion is being defined and what is the simplest way to correct the issue.

Remote machine provider reported: The configuration 'windows-2019-vs2019-uk-default' is not supported
Azure DevOps
Answer accepted by question author
  1. Pravallika KV 11,030 Reputation points Microsoft External Staff Moderator
    2026-02-10T12:49:51.7533333+00:00

    Hi @Steve Hodgkiss ,

    Thanks for the confirmation over Private chat. Glad the issue is resolved.

    Solution:

    As mentioned, checked the Release pipeline, Classic Release Pipeline and found the reference to windows 2019 and corrected to Windows latest.

    The error is because your pipeline is trying to use a deprecated VM image windows-2019-vs2019-uk-default

    1. Search your YAML or pipeline variables for that image.
    2. Replace it with a supported one, e.g.:
    pool:
  vmImage: 'windows-2022'

    or use windows-latest and then redeploy.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex Burlachenko 19,465 Reputation points Volunteer Moderator
    2026-02-10T12:40:21.26+00:00

    Steve Hodgkiss hi,

    error means exactly what it says :)))). In Azure DevOps, the image windows-2019-vs2019-uk-default is no longer supported. This is not a build or deployment problem. It is an outdated hosted agent configuration.In most cases it is specified directly in the YAML. Look for entries such as pool: vmImage: windows-2019-vs2019-uk-default, or image or queue references with a similar name. check any shared YAML templates included via extends or template, as the value may be coming from there rather than the main pipeline file.

    Msft is gradually retiring older hosted images. This particular image was region specific and has been legacy for some time. It is now fully unsupported, so the agent never starts.

    Switch to a supported image, for example windows-latest or explicitly windows-2022.

    In YAML this would look like

    pool:
  vmImage: windows-2022

    If your project genuinely requires Windows Server 2019, the only option is to use a self hosted agent running on your own VM with the required Visual Studio version. Microsoft hosted agents with this image are no longer available.

    The failure is caused by an obsolete vmImage. Find it in your YAML or templates. Replace it with windows-2022 or windows-latest, or move to a self hosted agent.

    rgds,

    Alex

    1 person found 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.