1. Topics
  2. nvda not reading powershell output.

nvda not reading powershell output.

Austin Pinto <austinpinto.xaviers@...>
 

hi all.
tried this on windows 10 2004 and latest windows insider build.
if i type any commands in powershell the typing is being read but the
output is not being read.
is it some problem or do i need to reinstall nvda.
Ralf Kefferpuetz
 

Maybe you should turn on report dynamic content changes. Try to toggle it with NVDA-5

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Austin Pinto
Sent: Freitag, 10. Juli 2020 16:02
To: nvda <nvda@nvda.groups.io>
Subject: [nvda] nvda not reading powershell output.

hi all.
tried this on windows 10 2004 and latest windows insider build.
if i type any commands in powershell the typing is being read but the output is not being read.
is it some problem or do i need to reinstall nvda.
g melconian <gmelconian619@...>
 

Austin, I don’t know as I don’t have 2004. But its working on 1909 with power shell.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Austin Pinto
Sent: Friday, July 10, 2020 7:02 AM
To: nvda <nvda@nvda.groups.io>
Subject: [nvda] nvda not reading powershell output.

hi all.
tried this on windows 10 2004 and latest windows insider build.
if i type any commands in powershell the typing is being read but the output is not being read.
is it some problem or do i need to reinstall nvda.
Luke Davis
 

First let me say that I do not now have this problem on NVDA alpha and Win 10 2004, but have had it in the past.

Under NVDA advanced settings, how do you have things configured? My settings are as follows:

Use UI Automation to access the windows console when available: not checked.
Use the new typed character support in Windows console when available: checked.

Luke

On Fri, 10 Jul 2020, Austin Pinto wrote:

tried this on windows 10 2004 and latest windows insider build.
if i type any commands in powershell the typing is being read but the
output is not being read.
is it some problem or do i need to reinstall nvda.
Luke Davis
 

I spoke too soon. These options no longer appear to have an effect on power shell.

Another question: are you running as:

(1) A normal user;
(2) an administrative user; or
(3) an elevated power shell?

Luke

On Fri, 10 Jul 2020, Luke Davis wrote some irrelevant nonsense:

First let me say that I do not now have this problem on NVDA alpha and Win 10 2004, but have had it in the past.

Under NVDA advanced settings, how do you have things configured? My settings are as follows:
Use UI Automation to access the windows console when available: not checked.
Use the new typed character support in Windows console when available:
1 - 5 of 5