If Windows console support for UIA is enabled, console output cannot be reviewed using the review cursor and the navigator is locked in a list item with the class name "MultiaskingViewFrame".

[cary-rowen]

Notes

This is a replacement for #14377 and makes the description clearer.

Under advanced settings, Windows console support is set to "UIA". This bug cannot be reproduced if set to "Legacy".

Steps to reproduce:

testconsole.py.txt

1. Use python to execute the above script in cmd
2. Alt+Tab to switch to other windows, and then back to the cmd window
3. Try to review the output in CMD
4. Press alt+Space, X to maximize the CMD window.
5. Alt+Tab to switch to other windows, and then back to the cmd window

   Actual behavior:

   Perform step 3: You cannot use the review command to review the cmd window. At this time, the navigator’s window class name is 'MultiaskingViewFrame'. Perform step 4: You will be able to review the CMD window again Perform step 5: You cannot use the review command to review the cmd window. At this time, the navigator’s window class name is 'MultiaskingViewFrame'.

   Expected behavior:

   The cmd output can be reviewed as expected.

   NVDA logs, crash dumps and other attachments:

   log.txt

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

NVDA2023.3Beta3

Windows version:

Windows 10 22H2 (AMD64) build 19045.3448

Name and version of other software in use when reproducing the issue:

Windows CMD

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

I can reproduce this using NVDA-2022.4

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes

[codeofdusk]

Windows 10 now allows the default terminal application to be changed. I'd suggest installing Windows Terminal and, in wt settings (Control+,), set your default terminal app to wt.

CC @carlos-zamora.

[XLTechie]

Windows 10 now allows the default terminal application to be changed. I'd suggest installing Windows Terminal and, in wt settings (Control+,), set your default terminal app to wt.

Would every Windows 10 user using the default terminal have to do this? If so, while I would consider that not a fix, perhaps something needs to be in the UG.

[cary-rowen]

@codeofdusk Hello, after my test, according to what you said, using Windows Terminal cannot solve this problem. Is there anything else I need to do?

[CyrilleB79]

@cary-rowen can you clarify if you make the tests with the options set to "Automatic (prefer UIA)" or "UIA when available"? Unfortunately, this combobox is not a feature flag (was probably implemented before it), so things are less clear.

[cary-rowen]

@CyrilleB79 Yes, I tested both options and the issue can be reproduced using Windows Terminal.

[seanbudd]

This issue is only caused by enabling an advanced preference in NVDA settings. It can be worked around by using a modern Windows Terminal. Closing as won't fix.

[codeofdusk]

Looking at this again, I think it's a duplicate of #12648. Unfortunately, I'm afraid UIA clients are just going to have to work around this one.

The "windows console support" option, as indicated in the user guide, does not affect terminal (which is always UIA).

[cary-rowen]

Hi @seanbudd As mentioned in my comment above, switching to a more modern terminal will not solve this problem.

[cary-rowen]

@codeofdusk Do you have any new discoveries about this?