I just submitted a feature request to #NVDA regarding creation of a more useful mechanism for editing the configuration on secure screens, to replace or augment the current clunky and all-or-nothing settings copy feature. Please give it some love! I don't think @NVAccess actually partakes in the whole vote with thumbs-ups to increase priority, but doing so might serve as a useful metric for how widely desired this is anyway, which could theoretically help with triage. If anyone who sees this is skilled and willing enough to actually turn this into a pull request, I would be very greatful! Otherwise, hopefully someone at NVAccess will take it up! It's about time we got a more useful means of customizing that other layer of NVDA.
github.com/nvaccess/nvda/issue…
#NVDASR #blind
in reply to Sean | Ginsenshi The blindwolf

@ginsenshi Which feature is failing for you? Do you mean the "Use currently saved settings during sign-in and on secure screens" option? As it notes, it "requires administrator privileges", so you do need to acknowledge the user account control (UAC) dialog, and then it will copy the settings to the profile used on secure screens.
in reply to Sean | Ginsenshi The blindwolf

@ginsenshi Can you send us a copy of your nvda.log and nvda-old.log after trying please? If you press NVDA+control+g to open NVDA's general settings, set the log level to "Debug" then NVDA+q and "Restart with add-ons disabled". Recreate, then press windws+e to open file explorer, then F2 to go to the address bar, type in %temp%
Note the percent signs either side of the word. Please attach the files to an email to us at info@nvaccess.org & we'll see if we can figure it out.
in reply to Sean | Ginsenshi The blindwolf

@ginsenshi Thanks Sean! I got your email ok. It looks like you have a number of add-ons which are not compatible with 2025.1 which you've overridden compatibility on. Please note that does NOT make the add-ons work, it simply stops NVDA from telling you they are not marked compatible. In this case, they are causing errors, and this may be leading to random issues. Please restart NVDA with add-ons disabled and see if the issue still occurs.