You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NVDA introduced support for Windows 8.x start screen workarounds in 2012, including focus movement and search suggestions announcement. Windows 8.x start screen is part of File Explorer, and Windows 10 uses a dedicated app (searchui/searchapp/searchhost/startmenuexperiencehost) to present start menu interface.
Why are the other templates not appropriate in this case?
This issue affects users and developers:
Users: NVDA 2026.1 will require Windows 10 (see Support Windows 10 or later #18684), so it makes sense to remove workaroudns used in now unsupported Windows releaes.
Developers: in some ways, search suggestions and other content form File Explorer app module became the basis for Windows 10 support in 2015 and beyond. However, with the end of support for Windows 8.x, it makes sense to standardize around Windows 10 work.
Have you asked for advice on how to report this issue via a community discussion? If so, please link to the discussion
Steps to reproduce or illustrate the issue (if applicable)
None
Expected outcome or behaviour (if applicable)
N/A
Screenshots, logs, and other attachments (if applicable)
N/A
System configuration or software environment (if applicable)
N/A
Additional information (if applicable)
While separate issue/PR pair would also work, doin this as part of Windows 10 requirement makes more sense as it gives us an opportunity to remove support code for operating system releases the NVDA project no longer supports (making the code base cleaner).
Implementation:
This will be implemented as part of the PR that will close #18684 unless NV Access advises creating a new PR.
Hi,
Part of #18684 project:
Detailed description of the issue
NVDA introduced support for Windows 8.x start screen workarounds in 2012, including focus movement and search suggestions announcement. Windows 8.x start screen is part of File Explorer, and Windows 10 uses a dedicated app (searchui/searchapp/searchhost/startmenuexperiencehost) to present start menu interface.
Why are the other templates not appropriate in this case?
This issue affects users and developers:
Have you asked for advice on how to report this issue via a community discussion? If so, please link to the discussion
No - this is part of #18684 work.
Steps to reproduce or illustrate the issue (if applicable)
None
Expected outcome or behaviour (if applicable)
N/A
Screenshots, logs, and other attachments (if applicable)
N/A
System configuration or software environment (if applicable)
N/A
Additional information (if applicable)
While separate issue/PR pair would also work, doin this as part of Windows 10 requirement makes more sense as it gives us an opportunity to remove support code for operating system releases the NVDA project no longer supports (making the code base cleaner).
Implementation:
This will be implemented as part of the PR that will close #18684 unless NV Access advises creating a new PR.
Thanks.