Forum Discussion

BrandonFowler's avatar
BrandonFowler
Occasional Contributor
2 months ago
Solved

Azure Pipeline InstallTestCompleteAdapter Not Working Properly with Windows Server 2025

This step in my yml file is failing after update to 'windows-latest' tag:  task: InstallTestCompleteAdapter@1         inputs:           installExecutor: true           updateExecutor: true      ...
  • Hassan_Ballan's avatar
    Hassan_Ballan
    2 months ago

    Your pipeline error (spawn wmic ENOENT) suggests that the TestComplete adapter is attempting to use the deprecated wmic utility for detection or version checks.

    This fails on Windows Server 2025 (windows-latest) because wmic is no longer available by default—it has been deprecated by Microsoft and removed from default system images.

    I recommend opening a support ticket with SmartBear to confirm whether the adapter relies on wmic, and if there's an updated version or workaround planned.

    In the meantime, you can:

    • Stick with the windows-2022 image, which still includes wmic, or
    • Use a self-hosted agent where you control the environment, or
    • Manually install TestExecute prior to running your tests, bypassing the adapter’s auto-install logic.

    🤖 AI-assisted response.
    💬 Found this helpful? Click Like to show appreciation.
    ✅ Issue resolved? Mark as Solution to help others.

Hassan_Ballan's avatar
Hassan_Ballan
Icon for Champion Level 3 rankChampion Level 3
2 months ago

Your pipeline error (spawn wmic ENOENT) suggests that the TestComplete adapter is attempting to use the deprecated wmic utility for detection or version checks.

This fails on Windows Server 2025 (windows-latest) because wmic is no longer available by default—it has been deprecated by Microsoft and removed from default system images.

I recommend opening a support ticket with SmartBear to confirm whether the adapter relies on wmic, and if there's an updated version or workaround planned.

In the meantime, you can:

  • Stick with the windows-2022 image, which still includes wmic, or
  • Use a self-hosted agent where you control the environment, or
  • Manually install TestExecute prior to running your tests, bypassing the adapter’s auto-install logic.

🤖 AI-assisted response.
💬 Found this helpful? Click Like to show appreciation.
✅ Issue resolved? Mark as Solution to help others.

BrandonFowler's avatar
BrandonFowler
Occasional Contributor
2 months ago

Downgrading my pipelines to windows-2022 image did fix this issue. I do not have access to a self-hosted agent and therefore I can't manually install TestExecute. I have marked this as a solution because it did allow me to continue running my tests in the pipeline, however I have also opened a ticket with SmartBear regarding the issue.