Brief summary

I updated portable alpha version of NVDA to alpha-52937,f535af1f (2026.1.0.52937). When I started it, my Braillex EL 80c display didn't start. The display works normally with all the previous versions of NVDA and also with the JAWS screen reader.

Steps to reproduce

Download the latest alpha and start it.

Actual behavior

The driver for Papenmeier newer models is not loaded and the display (Braillex EL 80c) doesn't start.

Expected behavior

The Braille driver for Papenmeier newer models should be loaded and the Braille display should start normally.

NVDA logs, crash dumps and other attachments

Here is a part of the log file:

Initializing braille
INFO - braille.initialize (17:10:54.983) - MainThread (13804):
Using liblouis version 3.35.0
INFO - braille.initialize (17:10:54.983) - MainThread (13804):
Using pySerial version 3.5
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (17:10:54.983) - MainThread (13804):
registering pre_configSave action: <class 'brailleDisplayDrivers.papenmeier.BrailleDisplayDriver'>
DEBUGWARNING - brailleDisplayDrivers.papenmeier.BrailleDisplayDriver.connectUSB (17:10:55.047) - MainThread (13804):
connectUSB failed
DEBUGWARNING - brailleDisplayDrivers.papenmeier.BrailleDisplayDriver.init (17:10:55.047) - MainThread (13804):
BROKEN PIPE - THIS SHOULD NEVER HAPPEN
ERROR - braille.BrailleHandler.setDisplayByName (17:10:55.048) - MainThread (13804):
Error initializing display driver 'papenmeier'
Traceback (most recent call last):
File "braille.pyc", line 2737, in setDisplayByName
File "braille.pyc", line 2807, in _setDisplay
File "braille.pyc", line 2777, in _switchDisplay
File "extensionPoints\util.pyc", line 230, in callWithSupportedKwargs
File "brailleDisplayDrivers\papenmeier.pyc", line 312, in init
Exception: no device found

NVDA type

portable copy

NVDA version

alpha-52937,f535af1f (2026.1.0.52937)

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

All the previous alpha and stable versions work correctly.

Windows version

Windows 11 Professional Version 24H2 (OS Build 26100.6584), System Type x64

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