Manual Test Runs in Azure Devops - Server errors when saving screenshots.

Kevin Koekemoer 5 Reputation points
2026-04-24T12:32:25.91+00:00

Good day,

For the past week or so, the web based test runner has been giving some issues with saving screenshots - it says that it can't connect to the server (DevOps via Azure) and screen shots can't be saved.

I even tried to use the old Test manager 2017 and it did not work, the only one that works is the Run the Desktop Client - and now you want to retire it - could we not get a proper local desktop app like the Test manager again - it worked great why do you want to go to all the browser based apps - if the old ones worked?

Developer technologies | Visual Studio | Testing
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-04-24T12:32:54.78+00:00

    The web-based test runner is the primary and recommended experience for running manual tests in Azure Test Plans. When screenshots or other diagnostic data fail to save with a “can’t connect to the server” error, the supported guidance is to move to the newer, fully supported tooling rather than rely on legacy clients.

    Key points based on current platform direction:

    1. Desktop Test Runner client retirement
    • The Test Runner client for Windows (the “Run the Desktop Client” option) is scheduled for retirement and will no longer be available or supported after its retirement date.
    • The platform direction is to use the web-based test runner instead of a new local desktop application.
    • This retirement is explicitly called out: “The Test Runner Client for Windows is scheduled for retirement… Transition to the web-based test runner, which provides the same functionality with improved performance and ongoing development.”
    1. Recommended replacement tools
    • Use the web browser-based runner from the Execute tab to run manual tests.
    • For rich desktop and web app testing, including screenshots and recordings, use the Test & Feedback extension, which is actively maintained and has been updated to Manifest V3 for security and performance.
    • Diagnostic data supported in the modern experience includes:
      • Screen captures (annotated screenshots)
      • Image action log (step-by-step visual log)
      • Screen recordings (auto-stop after 10 minutes)
    1. Impact of legacy dependencies
    • The legacy desktop Azure Test Runner client relies on Problem Steps Recorder (PSR), which is being deprecated in newer Windows versions. As PSR is removed, action logging and related features in the desktop runner may stop working.
    • Because of this dependency, the recommendation is to switch to screen recording and other diagnostic capture in the web runner and Test & Feedback extension.
    1. Current guidance for issues like screenshot save failures
    • For ongoing issues with screenshot saving in the web runner, the supported path is to:
      • Use the web runner plus Test & Feedback extension for capturing screenshots and recordings.
      • Transition away from the desktop Test Runner client and Microsoft Test Manager, which are no longer the primary focus and are being retired or deprecated.
    • If assistance is needed transitioning to the Test & Feedback extension or web runner, the official guidance is to contact support channels for help with migration and troubleshooting.

    There is no indication in the current guidance that a new local desktop app similar to Microsoft Test Manager will be introduced; instead, all investment is in the web-based runner and the Test & Feedback extension.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Varsha Dundigalla(INFOSYS LIMITED) 5,185 Reputation points Microsoft External Staff
    2026-04-27T11:36:02.82+00:00

    Thank you for reaching out.

    The behavior you’re experiencing (screenshots not being saved and showing a server connection error) indicates that this scenario likely requires deeper investigation specific to your environment and service connection.

    Since resolving this may involve analyzing account configuration, network conditions, or service-level diagnostics, it would be best handled through the official support channel where the team can securely review detailed logs and provide targeted assistance.

    We recommend reaching out to the Azure DevOps support team using the following link:

    Get support and provide feedback

    https://developercommunity.visualstudio.com/AzureDevOps

    They can help investigate the issue further and guide you with appropriate next steps.

    Was this answer helpful?

    0 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.