NVDA+control+r three times does not reset to factory configuration

[Qchristensen]

Brief summary

In the current alpha, when pressing NVDA+control+r three times quickly, the configuration is re-loaded from the saved configuration, not reset to factory defaults.

Steps to reproduce

Run the latest alpha
Press NVDA+control+r three times quickly

Actual behavior

NVDA loads the saved configuration and reports "Configuration applied"

Expected behavior

NVDA should reset to factory configuration and report that

NVDA logs, crash dumps and other attachments

Here are relevant excerpts from my log (set to debug level, first line number of each section noted just to give an idea of the amount in between). Note the time difference between the first and last keypress is less than 400ms:

Line 280: IO - inputCore.InputManager.executeGesture (11:38:56.676) - winInputHook (20968):
Input: kb(desktop):control+NVDA+r
DEBUG - core.resetConfiguration (11:38:56.676) - MainThread (22772):
Terminating vision
...
Line 390: initializing addonStore data manager
IO - inputCore.InputManager.executeGesture (11:38:56.993) - winInputHook (20968):
Input: kb(desktop):control+NVDA+r
IO - inputCore.InputManager.executeGesture (11:38:57.030) - winInputHook (20968):
Input: kb(desktop):control+NVDA+r
DEBUG - addonStore.dataManager._DataManager._getCacheHash (11:38:57.071) - initialiseAvailableAddons (19736):
Fetching add-on data from https://addonStore.nvaccess.org/cacheHash.json
...

Line 475: IO - speech.speech.speak (11:38:57.713) - MainThread (22772):
Speaking [LangChangeCommand ('en_GB'), 'Configuration applied']

NVDA type

installed copy

NVDA version

alpha-55275,8d4e1994 (2026.2.0.55275)

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

NVDA 2025.3.3 portable & temporary: Same behaviour
NVDA 2025.2 temporary "Configuration restored to factory defaults" when pressed three times.

Windows version

Windows 11 (64-bit) Version: 25H2, Build: 26200.8039

Name and version of other software in use when reproducing the issue

No response

Other information about your system

No response

Does the issue still occur after restarting your computer?

I have restarted my computer and the issue still occurs

If NVDA add-ons are disabled, is your problem still occurring?

I have restarted NVDA with add-ons disabled and the issue still occurs

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

I have run the COM Registration Fixing Tool and the issue still occurs

[SaschaCowley]

@Qchristensen I think the commit that introduced this is only on 26.2, but can you check with 26.1b8?

[Qchristensen]

2026.1 beta 8 works as expected - pressing NVDA+control+r three times gives "Configuration restored to factory defaults". Interestingly, I did try 2025.3.3 again when you said that - and it seems to be doing the same as the latest alpha?

It's not a feature I use all the time, so I'm not sure if it was working and we broke it and fixed it and broke it again, or if that is just a quirk of my system - take it as you will.

[CyrilleB79]

There is an intermittent issue with control+alt+R triple press command and it is not new to 2026.x dev cycle. Pressing 3 times does not always reset to factory default; sometimes, it only reset to disk config. And it seems more difficult to reset to get correct triple press result when NVDA is running with add-ons.
I have never investigated, but I imagine that when NVDA is reset to disk config (first press), there is processing time which would delay the next key press processing; then at the time the seconde/third press are processed, the delay would be such that they are no longer identified as multiple presses but as subsequent single presses. Playing with "Multiple key press timeout" option in keyboard parameter may help confirming this hypothesis or not.

[Qchristensen]

Thanks Cyrille. Looking at my log from this, as soon as I pressed NVDA+control+r the first time, it immediately (that millisecond from the log?) started terminating things to load the saved config. It was some 300ms later that it recorded the second keypress, and 37 milliseconds later that it timestamped the third keypress. I would have thought they were more evenly spaced out, but the explanation that when you press the keystroke once it immediately starts resetting without waiting for further keystrokes makes sense.

So I was wondering, if it resets to the saved profile when you press it once, but then accepts the second and third keystrokes before doing anything further, I tried:

1. Reset to factory defaults, NVDA uses Microsoft OneCore
2. Change synth to eSpeak and save config
3. Press NVDA+control+r three times. It loads the saved config as per this issue.
4. press NVDA+control+r FOUR times. It didn't speak anything, but it DID reset to factory default configuration

So the issue does seem to be that as soon as the keystroke is pressed once, it loads the saved configuration, but also drops whatever it normally uses to count how many times a keystroke has been pressed, so the second press of the keystroke is remembered as the first press (I'm not sure - does it not try to reload the saved config again at that point because it can see it is already in the middle of doing that?)