Note: the below only occurs if the advanced "Use
UI Automation to access the windows console when available" option is turned off. In
other words: the current default condition.
Steps to reproduce:
Run a recent NVDA alpha or beta.
Perform Windows+r, "cmd", enter.
Actual behavior:
A windows error sound occurs on launch.
The console appears to act normally after that, although when doing a "cls" NVDA is silent (does not read the prompt), until enter is pressed a second time, though this may be unrelated and happens in older versions.
Various warnings, and a "could not attach console: windows error (6, 'the handle is invalid')" are logged.
Expected behavior:
No windows error sound, no logged warnings or errors.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
beta-17929
Windows version:
Windows 10 Home 1903, 64 bit
Name and version of other software in use when reproducing the issue:
Windows command shell (cmd.exe)
Other information about your system:
AMD
Other questions
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
A few recent betas have done this.
Edit: also occurs on an installed version of alpha-17928,9dfbd2ee (7/3/2019).
Doesn't happen with 2019.1.1, although the (likely unrelated) cls problem does.
nvda-cmd-errors.txt
Note: the below only occurs if the advanced "Use
UI Automation to access the windows console when available" option is turned off. In
other words: the current default condition.
Steps to reproduce:
Run a recent NVDA alpha or beta.
Perform Windows+r, "cmd", enter.
Actual behavior:
A windows error sound occurs on launch.
The console appears to act normally after that, although when doing a "cls" NVDA is silent (does not read the prompt), until enter is pressed a second time, though this may be unrelated and happens in older versions.
Various warnings, and a "could not attach console: windows error (6, 'the handle is invalid')" are logged.
Expected behavior:
No windows error sound, no logged warnings or errors.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
beta-17929
Windows version:
Windows 10 Home 1903, 64 bit
Name and version of other software in use when reproducing the issue:
Windows command shell (cmd.exe)
Other information about your system:
AMD
Other questions
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
A few recent betas have done this.
Edit: also occurs on an installed version of alpha-17928,9dfbd2ee (7/3/2019).
Doesn't happen with 2019.1.1, although the (likely unrelated) cls problem does.
nvda-cmd-errors.txt