I am trying to follow a simple example to get IE11 automation working on a windows 7 box. I get a browser window open with about:blank in the URL and System.TimeoutException after a while.
The code works on my local developer machine but does not work on a remote desktop with a basic windows 7 64-bit install.
I have configured the browser, uninstalled and reinstalled Test Framework (Testing_Framework_2017_2_0530_1_Free.msi). Tried building x86, x64, Any CPU in both debug and release.
Again, this works on my local machine but not the remote machine. Are there pre-requisites I am unaware of? The only thing I install is the Test Framework.
Any help would be very much appreciated.
6 Answers, 1 is accepted
// Initialize the settings
Settings mySettings =
// Set the default browser
mySettings.Web.DefaultBrowser = BrowserType.InternetExplorer;
// Create the manager object
Manager myManager =
// Start the manager
// Launch a new browser instance. [This will launch an IE instance given the setting above]
// Navigate to a certain web page
// Perform your automation actions.
Element mybtn = myManager.ActiveBrowser.Find.ByTagIndex(
// Shut-down the manager and do all clean-up
Thank you for sharing details about the issue you have faced.
It seems that the remote machine does not have Visual Studio installed and your developers machine does. Therefore IE is not working on that machine.
To resolve this misbehavior you could install Team Explorer 2013 from the MSDN site. Please note that this download is only available for signed in users with a Microsoft account.
This is an issue we have investigated in depth and quite soon - within our next planned release - a fix will be introduced and additional installations will not be required.
I hope the above information would be helpful for you. Thank you for your understanding!
Test Studio Trainings
Thanks for getting back to me Elena.
I've managed to work around the IE problem by installing microsoft.mshtml.dll to the GAC by using gacutil.exe. So far it seems to work and allows us to automate the process for our CI builds.
Thanks for getting back to me.
This is the other workaround which is a bit more complex for part of our users which are not familiar with coding at all. Though I am glad to know you resolved the issue on your end.
As I have mentioned in one of my replies to your posts recently - this behavior will be fixed with our next release and none of the above will be required.
Thank you once again for your cooperation!
Test Studio Trainings