Hi,

Yes, this again confirms my hypothesis. See a message I sent earlier for the full explanation.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Felix G.

Sent: Thursday, February 8, 2018 11:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Potentially important observation with Windows 10 Preview

 

Hi Joseph,

Win+X says unknown for me and indeed does not read. The other menus that didn't read, however, didn't say unknown, just in case it matters.

Kind regards,

Felix

 

Joseph Lee <joseph.lee22590@...> schrieb am Do., 8. Feb. 2018 um 20:46 Uhr:

Hi,

What about Windows+X menu? If NVDA does not read that menu, then don’t worry – fixed in newer builds.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Felix G.
Sent: Thursday, February 8, 2018 11:41 AM
To: nvda@nvda.groups.io
Subject: [nvda] Potentially important observation with Windows 10 Preview

 

Hi!

I'm running Windows Insider build 17074.1002 64 bit. With this build, the current NVDA Master won't read menus in Notepad. Perhaps more importantly, context menus for files and folders in Windows Explorer are also not read. For me, that is. It would be great if other Windows Insiders could try to reproduce, to prevent this from suddenly affecting users post 2018.1.

Here's one piece of evidence it's NVDA-related and not just my system: JAWS does not have those problems. Reinstall of NVDA does not fix them, neither does restoring factory defaults.
Kind regards,

Felix