HyperVs: w/ TestComplete/TestExecute: Lose their connection to the On-Prem SLM

I have HyperVs used for automation with ADO pipelines along with an On-Prem SLM.

There are instances after a new release comes out or maybe a network issue as well where when an ADO pipeline is run, the run is over very quickly.

I do not see anything happen on the HyperV when watching.

The soultion I have to do to correct this is open up TestComplete or TestExecute, depending on what the ADO pipeline is using and let it find again my On-Prem SLM.  I close TC\TE, try the ADO pipeline again and all is well.

I am thinking of implementing a .bat file (run as admin) that would run each morning to open, wait, and close TestComplete and TestExecute just to refresh the connection to the SLM so I do not have these hiccups with my ADO pipelines to my HyperVs.

I should not have to do this ?

Anyone else see this scenario happen to them?