I've reproduced the issue on my side.
Try use "Start-Process TestComplete.exe". Also if you need to use some parameters read help info for PowerShell "Start-Process" command.
Looks like you use path to testcomplete.exe as a parameter for testcomplete.exe. Could you show us your code to run TC.
When TC started and displayed such message, please look into his command line. For example, you can open ObjectBrowser in TC and find Sys.Process("TestComplete") object. What is the value for "CommandLine" property?
Also, TestComplete 14.10 now have a command line tool to use with CI systems to run tests. You can try this.
See help https://support.smartbear.com/testcomplete/docs/working-with/automating/session-creator/index.html
All I type in to the terminal if that is what your asking is:
TestComplete.exe
No parameter at all. I have tried it in the actual bin directory and exported as an enviroment variable. I do agree it is taking the exe as the project for some reason. I tried repair and complete reinstall but nothing changed.
What if you run TestComplete.exe at a standard Windows command prompt and not in Powershell? Does that make a difference?
Strange. That did work. Any idea why?
Honestly... I don't know. It just seemed like something to try, in case there's something specifically in the PowerShell environment that triggers opening anything as a project.
