Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA rarely fails to open at the Windows login screen #17452

Closed
haruncetinkaya306 opened this issue Nov 29, 2024 · 1 comment
Closed

NVDA rarely fails to open at the Windows login screen #17452

haruncetinkaya306 opened this issue Nov 29, 2024 · 1 comment
Milestone

Comments

@haruncetinkaya306
Copy link

haruncetinkaya306 commented Nov 29, 2024

Steps to reproduce:

Press the power button, wait for Windows to start. In rare cases, NVDA will not start even though it is set to start at the Windows login screen.

Actual behavior:

Windows starts, NVDA is set to start here, Windows starts properly but NVDA does not start.

Expected behavior:

NVDA should start at the Windows login screen, which it does most of the time.

NVDA logs, crash dumps, and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

2024.4.1

Windows version:

Windows 11, 24 H2.

Name and version of other software used to reproduce the problem:

None.

Other information about your system:

None.

Other questions

Does the problem persist after restarting your computer?

When the problem occurs varies, but restarting certainly does not fix the problem, which is rare.

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

I have experienced this error with previous versions as well.

If the NVDA plugins are disabled, does your problem persist?

I am not using any plugins.

Does the problem persist after running the COM Registry Fix Tool from NVDA's tools menu?

It doesn't work

@github-actions github-actions bot added this to the 2025.1 milestone Nov 29, 2024
@haruncetinkaya306
Copy link
Author

I reproduced this issue with issue #17453, there I was able to attach the logs correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant