Comment 1 by jteh on 2015-03-12 05:31
I've seen this, but it's rare as you say and I haven't been able to reproduce it on demand either. I suspect UI Automation core is breaking/crashing somehow, but I haven't been able to work out any more than that.

Comment 2 by bhavyashah on 2015-03-12 08:48
Hi,
I reproduced this once right now on Windows 7 Ultimate 32 bit as well.
Just adding...

Comment 3 by nvdakor on 2015-05-28 23:48
Hi,
Confirmed in Windows 8.1 with a possible way to reproduce this.
STR:

1. Open Start screen and type a search term that isn't readily available. Windows will open search results window.
2. Once search results window opens, press Alt+F4 to close it.
   Expected: The next time you press Windows key, NVDA should announce start screen contents.
   Actual: NVDA does not say start screen is opened.

Setup:

• OS: Windows 8.1.
• NVDA version: next.12021.
• Reproducible: Yes on my system.

Thanks.

Comment 4 by nvdakor on 2015-05-29 00:10
Hi,
Possible workaround found: In Windows 8/8.1, when you don't hear start screen content when you press Windows key, press Windows+C to open charms, press escape and press Windows key.
Thanks.

Comment 5 by Brendon22 on 2015-05-29 03:06
Hello, Good Afternoon,

I have this same issue with the same setup!!

Something is going on?

Thank you.

Comment 6 by jteh on 2015-07-01 12:47
Thanks for the repro steps in comment:3. I can confirm this. it also seems to happen with Narrator, so this is not NVDA specific. I've yet to test this in Windows 10.

I am not able to reproduce this using the steps provided in #4967 (comment) and Windows 10. It would be interesting to know if this can still be reproduced in Windows 7 or 8.1, in hopes this has been fixed. If not, should an appropriate issue be created with Microsoft?

I cannot reproduce issue reported in #4967 (comment) using NVDA 2017.3 on Windows 8.1, although this might well be because I have a Start menu modified by Classic Shell.

@tspivey
I actually believe this was either fixed by ms in win10, or is not relevant no more.

I just tried this on my Windows 8.1 virtual machine and NVDA 2017.3 and did not get the behavior described above. Either this has been fixed by Microsoft, or this will not be fixed by Microsoft, as a lot of development is with Windows 10. Closing as this sounds not to be an NVDA issue, as Narrator experienced this issue as stated in #4967 (comment)