NV Access

NVDA 2026.1 Beta 4 is available for testing for anyone interested in trying out the next version of NVDA before it is released!

Changes:

- Fixed a rate issue in eSpeak NG
- Fixed changing MathCAT settings
- “Use NVDA during sign-in” is no-longer checked by default in a fresh install
- Warning is given when creating a portable copy if it will downgrade an existing portable copy.
- Updates to translations.

Full details & download: https://www.nvaccess.org/post/nvda-2026-1beta4/

#NVDA #NVDAsr #Update #PreRelease #FOSS

NV Access | NVDA 2026.1beta4 available for testing

Feb 23 at 6:51amWeb
Show threadBrandon TysonFeb 23
@NVAccess Thanks for posting this. I was just curious why start NVDA at the sign in screen is unchecked by default now? I have actually started doing this myself, but I just thought it was interesting that this happened so soon after I started experimenting with this.
Show threadmaysoncaboFeb 23
@BTyson @NVAccess Yes I just upgraded my nvda to the 4th beta
Show threadmaysoncaboFeb 23
@BTyson @NVAccess not that I am complaining but I'd like to know this as well. I started not using NVDA at sign in as well.
Show threadNV AccessFeb 24
@maysoncabo @BTyson Did you see the reply to the same question I posted before I saw your query? Basically we're being overly-cautious and ensuring that people ARE opting in for having NVDA run at startup etc. It won't change your existing install, and even on a new install, the option is presented as you are installing so you can ensure you have it setup how you want.
Show threadmaysoncaboFeb 24
@NVAccess @BTyson Hello when will the natural voices be worked on for us to try?
Show threadNV AccessFeb 24
@maysoncabo @BTyson We are waiting on Microsoft to make them avaialble to third party developers :)
Show threadmaysoncaboFeb 24
@NVAccess @BTyson ok that's good.
Show threadmaysoncaboFeb 24
@NVAccess @BTyson any timeline as to when or how long?
Show threadNV AccessFeb 24
@maysoncabo @BTyson No, it's dependant on Microsoft- feel free to reach out to their disability answer desk or feedback hub to encourage them that users are waiting on it maybe?
Show threadAmirFeb 24
@NVAccess People ask this because supporting MS natural voices is in the NVDA roadmap. When something is in the roadmap, it means NVAccess can support it without depending on, say, Microsoft to prepare the infrastructure first.
@maysoncabo @BTyson
Show threadNV AccessFeb 24
@amir @maysoncabo @BTyson It's in the roadmap because it's something we know many people are keen for, and we are happy to support the implementation of, but in this case, that feature is not simply waiting for us to implement it, but we do need Microsoft to make it available
Show threadAmirFeb 24
@NVAccess @maysoncabo @BTyson So clarify it in the roadmap. When I myself saw that, I thought the technical barrier has been removed.
Show threadNV AccessFeb 24
@amir @maysoncabo @BTyson Apologies for the confusion Amir. It is listed in "Medium" so not something we are immediately free to work on - which I expect is because in this particular case, we are waiting on Microsoft. And indeed, looking at some of the other items, they aren't all unblocked and ready for work by us - MathCAT for instance is there now in 2026.1 but it was a collaboration with Neil, the original Mathcat developer, Chinese Word Segmentation is working with a group from China
Show threadNV AccessFeb 23

@BTyson You are a trned setter!

The rationale was to ensure that users DO want this and opt IN to it. The option is presented as you install NVDA so it is there to check if you want it, but it stops it from being inadvertently set if people don't want it. It's probably one of those things you could make a very logical argument about either way, but we elected to err on the side of ensuring users can opt IN to this rather than needing to opt OUT.

Show threadBrandon TysonFeb 23
@NVAccess I can get behind that, and I am all for opting in to something rather than opting out. Too much stuff is assume opt in, opt out later these days, so I'm super glad to see this going the other way.
Show threadCleversonFeb 23
@NVAccess I downloaded beta 4 for testing. when I ran it, it simply restarted the stable 2025.3, and the following was registered in nvda-old.log:
INFO - __main__ (10:05:55.426) - MainThread (14160):
Starting NVDA version 2026.1beta4 AMD64
INFO - core.main (10:05:55.481) - MainThread (14160):
Config dir: C:\Users\CLEVER~1\AppData\Local\Temp\nsx71CD.tmp\app\userConfig
INFO - config.ConfigManager._loadConfig (10:05:55.484) - MainThread (14160):
Loading config: C:\Users\CLEVER~1\AppData\Local\Temp
Show threadNV AccessFeb 24
@clv1 How did you go with the new Beta? Did you get it working? I would have suggested a restart as the default first action to try
Show threadCleversonFeb 24
@NVAccess Thanks; restarting did the trick.
Show threadCleversonFeb 23
@NVAccess
\nsx71CD.tmp\app\userConfig\nvda.ini
CRITICAL - __main__ (10:05:55.744) - MainThread (14160):
core failure
Traceback (most recent call last):
File "nvda.pyw", line 309, in <module>
File "core.pyc", line 717, in main
File "NVDAHelper\__init__.pyc", line 49, in <module>
File "eventHandler.pyc", line 13, in <module>
File "api.pyc", line 15, in <module>
File "review.pyc", line 15, in <module>
File "NVDAObjects\__init__.pyc", line 25, in <module>
Show threadCleversonFeb 23
@NVAccess
File "displayModel.pyc", line 16, in <module>
File "mouseHandler.pyc", line 9, in <module>
File "gui\__init__.pyc", line 17, in <module>
File "ui.pyc", line 30, in <module>
File "braille.pyc", line 37, in <module>
File "louisHelper.pyc", line 23, in <module>
File "louis\__init__.pyc", line 271, in <module>
File "ctypes\__init__.pyc", line 412, in __getattr__
File "ctypes\__init__.pyc", line 417, in __getitem__
AttributeError: function 'lou_freeTableFile' not found