Hi there

Just got hold of a brand new laptop from my new employer, and, it's an HP Victus, with 16Gb RAM and a 1TB SSD, but, while I had requested windows 10 pro 64 bit, they installed windows 11 home 64 bit on it.

In any case, my primary form of activity with this machine relates to python programming, so I am now trying to figure out what possible configuration changes, add-on installation, etc. I should try out to get the command line/console interaction to work in a similar fashion to how it operates on my other main machine, which is running windows 10 pro 64 bit, but, with effectively a mirror image of the NVDA version and add-ons combination.

Say that since literally exported a portable version of the NVDA installation on the windows 10 machine, and then fired it up on the new machine, and told it to install locally - telling it to maintain configuration in both parts of that process.

Anyway, while now on the new machine, I have tried playing around with UIA settings under NVDA settings|advanced, and, have tried out Tony Malik's console toolkit settings in different states - turning on and off read out changes in real-time, this newer machine, running under windows 11, seems to act inconsistently in the console/command prompt?

As in, every now and then it will read out on-screen changes as they happen/take place, but, then it will just stay silent until I review the screen in either object navigation mode, or screen review mode to see what's happening?

Now, I have various other add-ons installed, and suppose could go through the process of uninstalling them all and then try to figure out if installing any specific one makes a difference, but, this is not an issue on my windows 10 machine, so am guessing it has more to do with the operating system, or something?

Anyway, does anyone have any ideas/suggestions I could try out before I try out stepping through different combinations of add-ons, etc.?

Is there some or other choice in terms of screen resolutions, etc. that could make a difference?

Thanks

Jacob,

Are you talking in native Command Prompt (cmd.exe) or under Windows Terminal?  There has just been a lengthy discussion of an issue similar to the one you describe  on the NVDA  Development and Add-Ons development Groups, if you're talking about Windows Terminal.

See NVDA Development Group: Possible bug in NVDA with Windows Terminal.
and on the Add-Ons development group: Question to Windows Terminal in Windows 11
--

It used to be understood that if you published and profited from a mass media platform you should also be responsible for its content. That idea is nowadays considered quaintly archaic. There is no real accountability, and almost limitless ability to post any kind of ridiculous and scurrilous nonsense. God help us.

       ~ Ross Goldbaum, Letter to the New York Times,

          Regulating Media: It’s Now Seen as a Quaint Idea, November 13, 2022

Ok, that makes more sense - I think when I launch cmd.exe, it's still bringing up the new windows terminal of windows 11 - that machine has updated to 22H2, etc.

And, yes, scanning through those threads, it sounds exactly like what I am experiencing.

Found a workaround for that, for now from the following MS blog page:

Windows terminal is now the default in windows 11 - windows command line

Effectively, it tells you to go into settings, privacy and security, turn on developer mode, and then set windows terminal to use either windows console host, or windows terminal (the new one), or let windows decide for you - and, setting it to windows console host seemed to remove the issue, so, might bookmark this page, and, leave it on that setting for now.

Thanks

On Wed, Nov 23, 2022 at 02:41 PM, Jacob Kruger wrote:

I think when I launch cmd.exe, it's still bringing up the new windows terminal of windows 11

-
It shouldn't, as Command Prompt and PowerShell still exist as independent entities under Windows 11.  Under Windows 10, unless you specified otherwise some time back, PowerShell is the default, and under Windows 11 Terminal is now the default, but in neither situation should a direct invocation of Command Prompt or PowerShell be overridden.

I'll have to try this on my Windows 11 machine, but I would be utterly shocked if a direct invocation of cmd.exe or PowerShell would bring up Terminal.
--

It used to be understood that if you published and profited from a mass media platform you should also be responsible for its content. That idea is nowadays considered quaintly archaic. There is no real accountability, and almost limitless ability to post any kind of ridiculous and scurrilous nonsense. God help us.

       ~ Ross Goldbaum, Letter to the New York Times,

          Regulating Media: It’s Now Seen as a Quaint Idea, November 13, 2022

On Wed, Nov 23, 2022 at 02:41 PM, Jacob Kruger wrote:

Found a workaround for that, for now from the following MS blog page:

Windows terminal is now the default in windows 11 - windows command line

-
Thanks for this.  I've passed it along, crediting you, on both of the previously referenced topics.
--

It used to be understood that if you published and profited from a mass media platform you should also be responsible for its content. That idea is nowadays considered quaintly archaic. There is no real accountability, and almost limitless ability to post any kind of ridiculous and scurrilous nonsense. God help us.

       ~ Ross Goldbaum, Letter to the New York Times,

          Regulating Media: It’s Now Seen as a Quaint Idea, November 13, 2022

Jacob,

There has been an addition this evening in post  #46591 of one of the topics I previously referenced from the NVDA developer working on this.  It may be of particular interest to you and others with this issue.
--

It used to be understood that if you published and profited from a mass media platform you should also be responsible for its content. That idea is nowadays considered quaintly archaic. There is no real accountability, and almost limitless ability to post any kind of ridiculous and scurrilous nonsense. God help us.

       ~ Ross Goldbaum, Letter to the New York Times,

          Regulating Media: It’s Now Seen as a Quaint Idea, November 13, 2022

Thanks, Brian.

And, yes, I am actually subscribed to add-ons mailing list - haven't had chance to do much more than start tinkering around with creating add-ons, but, while don't follow that list properly, I am subscribed - saw your post.