On the new machine, was getting inconsistent feedback from cmd.exe while
doing various things, and, mentioned it on the NVDA-users list, and, was
notified that, with 22H2 update of windows 11, they've more or less
replaced cmd.exe and other terminal windows with new windows terminal
interface, which is apparently providing usability issues to
screenreader users.
Either way, found the following form of a blog post from MS relating to
how to reset it to original one if you want to - have done so for now,
and, with a very quick test, it seemed to be cooperating with NVDA again:
Windows Terminal is now the Default in Windows 11
<https://devblogs.microsoft.com/commandline/windows-terminal-is-now-the-default-in-windows-11/>
They mention that you can go into settings, privacy and security,
developer options - turn that one on - and, then set the terminal to
windows console host, as opposed to letting windows choose, or setting
it to windows terminal.
This did seem to immediately get the cmd.exe command line to start
cooperating with NVDA again, so, thought would bring it up here, just in
case the 22H2 update has caused hassles for others.
Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."
