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
accessKey: 'XXXXXXXXXXXXXXXXXXXXXXXXXX'
logsLevel: '0'
preferredExecutor: TE
cmdLineParams: '/PrjVar:alternateEnvironment=$(alternateEnvironment) /PrjVar:startingEnvironment=$(startingEnvironment) /PrjVar:logEventMessages=$(logEventMessages)'
it works just fine if I switch back to 'windows-2022' however, I would like to use some functionality added to the new version.
This is what the logs look like when I try to run this on the new version:
Test Case search mode: "In Execution Plan"/
Installing the test adapter...
The test adapter installation completed.
Neither TestExecute nor TestComplete was found on the agent machine.
Predefined executor [TestExecute] Version major: 15
Predefined executor [TestExecute] version minor: 77
##[error] spawn wmic ENOENT
##[error] Can not specify installer version to download
It was saying that the version was not defined and after I defined the version it still would not work.
This is on a windows hosted agent so I do not expect it to already have the adapter/TestExecute. Again, it works just fine if I change nothing and set the version back to windows-2022. Anyone know what's happening here?
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.
