Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update KB3032359 breaking IE driver #368

Closed
florentbr opened this issue Mar 25, 2015 · 2 comments
Closed

Update KB3032359 breaking IE driver #368

florentbr opened this issue Mar 25, 2015 · 2 comments

Comments

@florentbr
Copy link

The KB3032359 update from march 10 breaks the Internet Explorer driver.

Environment:
Windows 8.1 64bit, IE11, IEDriver 32bit 2.45

To reproduce:

var driver = new InternetExplorerDriver();
driver.Navigate().GoToUrl(@"http://www.google.com");
driver.FindElementByName("q").SendKeys("ok");

The last line throws ElementNotFoundException and the log indicates an "Access denied" error on IHTMLWindow2::execScript.
It seems to be related to execScript being deprecated:
https://connect.microsoft.com/IE/feedback/details/1062093/installation-of-kb3025390-breaks-out-of-process-javascript-execution-in-ie11

I have the registry key "FEATURE_DISABLE_INTERNAL_SECURITY_MANAGER" set to 1,
but this workaround for the kb3025390 doesn't work with this new update.

@jimevans
Copy link
Member

This isn't globally broken. I can confirm that I have the referenced update installed, as shown here:
windowsupdates

Running the same code in my environment works perfectly fine. I'm closing this issue as unreproducible.

@florentbr
Copy link
Author

I tried again on a new fresh installation with the same config and updates and it didn't fail.
I found that it is the "FEATURE_DISABLE_INTERNAL_SECURITY_MANAGER" registry key that is causing the failure.

So for the record, the IE driver doesn't work with this registy tweek since KB3032359:

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_DISABLE_INTERNAL_SECURITY_MANAGER]
"iexplore.exe"=dword:00000001

Thanks for your time.

@lock lock bot locked and limited conversation to collaborators Aug 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants