Re: Bug in beta with command line window in administrator mode

Brian's Mail list account

In windows 10, there are an increasing number of things portable screenreaders cannot do. Not sure that this is progress!

Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Tony Malykh" <anton.malykh@...>
To: <>
Sent: Wednesday, November 21, 2018 6:39 PM
Subject: Re: [nvda] Bug in beta with command line window in administrator mode

Good catch, I was running it directly from the installer. I'll try to
properly install it tonight and see if I can still reproduce this. It
would be great to have some kind of meaningful error message if this
is expected behavior.

On 11/21/18, Tyler Spivey <tspivey@...> wrote:
Are you running an installed copy? If not, then it won't work.
On 11/21/2018 10:30 AM, Tony Malykh wrote:
All add-ons disabled, the bug is still there.
I couldn't find that bug in recently filed issues on github.

On 11/21/18, Joseph Lee <joseph.lee22590@...> wrote:
Does restarting with add-ons disabled help? If not, it would be best to
search GitHub for issues (it was noted a few months ago).

-----Original Message-----
From: <> On Behalf Of Tony Malykh
Sent: Wednesday, November 21, 2018 10:16 AM
Subject: [nvda] Bug in beta with command line window in administrator

I just tried NVDA 2018.4.beta1 and it cannot read the contents of
line window in Administrator mode. Here is the exception I'm
ERROR - NVDAObjects.behaviors.LiveText._monitor (10:09:54.604):
Error getting initial lines
Traceback (most recent call last):
File "NVDAObjects\behaviors.pyo", line 260, in _monitor
File "NVDAObjects\window\winConsole.pyo", line 49, in _getTextLines
File "winConsoleHandler.pyo", line 121, in getConsoleVisibleLines
File "wincon.pyo", line 70, in GetConsoleScreenBufferInfo
WindowsError: [Error 6] The handle is invalid.

Command line with normal privileges works fine. I'm running the latest
Windows 10.
Also, what's the preferred way to report bugs like this? Should I send
email here or directly create an issue on github?


Join to automatically receive all group messages.