Internet Explorer 11 causes WindowsError

[nvaccessAuto]

Reported by nishimotz on 2013-11-02 09:27 NVDA version master-9685,b2b398a with Windows 8.1 (x64) causes WindowsError on desktop version of Internet Explorer 11 (11.0.9600.16384).

After the error as shown below, Internet Explorer cannot be operated via Single Letter Navigation in web pages.

INFO - __main__ (18:17:12):
Starting NVDA
INFO - core.main (18:17:12):
Config dir: C:\nvda-portable\userConfig
INFO - core.main (18:17:12):
NVDA version master-9685,b2b398a
INFO - core.main (18:17:12):
Using Windows version sys.getwindowsversion(major=6, minor=2, build=9200, platform=2, service_pack='')
INFO - core.main (18:17:12):
Using Python version 2.7.5 (default, May 15 2013, 22:43:36) [v.1500 32 bit (Intel)](MSC)
INFO - core.main (18:17:12):
Using comtypes version 0.6.2
INFO - synthDriverHandler.setSynth (18:17:13):
Loaded synthDriver sapi5
INFO - core.main (18:17:13):
Using wx version 2.8.12.1 (msw-unicode)
INFO - braille.initialize (18:17:13):
Using liblouis version 2.5.3
INFO - braille.BrailleHandler.setDisplayByName (18:17:13):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:17:13):
Braille input initialized
INFO - core.main (18:17:13):
NVDA initialized
INFO - config.ConfigManager.save (18:17:15):
Base configuration saved
ERROR - virtualBuffers.MSHTML._loadBuffer (18:17:21):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyc", line 623, in _loadBuffer
WindowsError: [1702](Error) The binding handle is invalid

[nvaccessAuto]

Comment 1 by jteh on 2013-11-04 01:00 Did you perhaps use the reload plugins command (in NVDA menu -> Tools or NVDA+control+f3)? That will cause this problem; see #2892.

[nvaccessAuto]

Comment 2 by nishimotz on 2013-11-06 14:22 As the result of additional test with master-9686,3838313 snapshot (no plugins) and Windows 8.1 (32bit, almost clean environment) is as follows:

• Within launcher session of NVDA, IE11 raises "binding handle" error as mentioned previously.
• Within installed process of NVDA, IE11 works normally.

The version of Internet Explorer is 11.0.9600.16384 RTM (KB2841134).

[nvaccessAuto]

Comment 3 by jteh on 2013-11-07 04:13 Is this the desktop or immersive version of IE? The immersive version probably needs uiAccess like all other full screen Windows 8 apps. There's nothing we can do to make browse mode work here. However, we should definitely clean up the experience it a bit; e.g. don't try to load a buffer if there's no nvdaHelperRemote binding handle.

[nvaccessAuto]

Comment 4 by nishimotz on 2013-11-08 00:10 Since Windows 8.1 and IE11, Enhanced Protected Mode of Internet Explorer for the desktop is enabled by default.

Is it related to the issue?

http://msdn.microsoft.com/en-us/library/ie/dn265025%28v=vs.85%29.aspx

It seems that IE11 for desktop on Windows 8.1, with EPM disabled, works with NVDA running from the latest source code.

[nvaccessAuto]

Comment 5 by jteh on 2013-11-08 00:32 Ah. Yes, this does explain things. uiAccess is needed to access this. So, as I noted, we can't provide browse mode without uiAccess, but we should still clean up the exceptions.

[Adriani90]

@nishimotz are you still able to reproduce it? I am working in IE11 with protected settings on Windows 8.1 on 64bit system and was never able to reproduce it during last two years.

[nishimotz]

@Adriani90 I don't have Windows 8.1 (x64) machine anymore.

So far, I cannot reproduce this issue with Windows 8.1 (x86) and NVDA 2018.4rc2.

[Adriani90]

@ehollig then I think we can close this issue and reopen it if someone reports it again.

[nishimotz]

I agree we should close the issue, but I can't.

[LeonarddeR]

I can :)