ContributionsMost RecentMost LikesSolutionsRe: Command line settings import Thanks for the help. I've submitted a feature request here. Hopefully any other interested parties will find it. Command line import of TC/TE settings As someone who is automating the creation of my test environment, I would like to automate the configuration of TestComplete/TestExecute. TestComplete allows for a manual import of a settings file TestExecute does not. This is a problem when I'm attempting to spin up VMs from scratch and immediately start tests. For both products, I would like to be able to use a settings file that I have previously exported to set my desired product settings at the command line either during or after install to finish the product configuration. Command line settings import I'm generating VMs with a set of powershell scripts and installing TC/TE on them. Is there a way to import a TC/TE settings file from the command line or during install? I was unable to find anything other than the manual import/export documentation. SolvedRe: Overlapping window log error when window has been handled by event handler Gave that a shot and it worked great. Thanks! Overlapping window log error when window has been handled by event handler I'm currently handing an overlapping window using the project's event handler and after it exits I still get an error in the log. As far as I can tell the object still exists, but it is no longer visible. I was hoping for a way to not post the error to the log because it has been sufficiently handled for my test. For anyone interested in trying to reproduce this: Open an "older" version of VS 2019 (I'm currently using 16.0.3 with 16.0.4 available) and wait for the toast window in the bottom right hand corner to appear telling you that there's a newer version available. Create a C# winforms project. Add a textbox control to the form. Attempt to interact with any property of the control in the properties window behind the toast window. You'll generate the overlapping window event. Inside the overlapping window event handler run Sys.WaitProcess("devenv", 500).Find("Name", "*HwndSource: ToastWindowRoot*", 5).Find("WPFControlName", "IgnoreButton", 8).Click(); // To click the close button on the window Delay(5000); // To prove that it's not a timing issue The toast window object still exists, but doesn't appear on the Visual Studio window. You'll still get an error in the log saying there was an overlapping window. Solved