Suggestion: NVDA troubleshoot the startup process to avoid extreme situations that may cause users to be unable to use it

[wmhn1872265132]

Is your feature request related to a problem? Please describe.

Currently known:
#15690 (Fixed)
#16362

Describe the solution you'd like

I am not sure if there will be other file damage or formatting errors that may cause similar problems to occur. It is recommended to thoroughly investigate the startup process to resolve similar issues.
For ordinary users, once this situation occurs, it is almost catastrophic:

1. Repeated restarts without obvious error prompts may cause users to not know where to solve the problem;

2. Because NVDA simulates pressing the Windows+U shortcut key during startup, even if users want to use other screen readers for troubleshooting, it is very difficult

3. Most users encounter this situation and their first consideration is to uninstall and reinstall, but if the problem occurs in the user profile, doing so is of no use

Therefore, it is recommended to conduct a thorough investigation of the startup process of NVDA, which has been implemented

1. Prevent NVDA from restarting repeatedly when it cannot start normally;
2. Check every file that needs to be read and written when NVDA starts (including dependent files in the program folder), and ensure that there is an error message or automatic recovery solution when NVDA cannot read and write these files normally.

Describe alternatives you've considered

Additional context

[gerald-hartig]

This issue needs more detail on what is the desired solution.

[wmhn1872265132]

Original description updated

[wmhn1872265132]

Here’s what’s updated:
Therefore, it is recommended to conduct a thorough investigation of the startup process of NVDA, which has been implemented

1. Prevent NVDA from restarting repeatedly when it cannot start normally;
2. Check every file that needs to be read and written when NVDA starts (including dependent files in the program folder), and ensure that there is an error message or automatic recovery solution when NVDA cannot read and write these files normally.

[seanbudd]

Hi, converting this issue to a discussion.
As is, this is not something that describes a solvable issue in NVDA.
This is a suggestion to audit the start up code for NVDA and we have already done this recently when dealing with start up issues in previous releases. If known issues are found they can be reported and handled.