When I try to start a portable copy of NVDA (I have used many Alpha and Beta versions since December 2023) it may start the first time, but when I exit the program and start it again, NVDA tries to start but this happens very slowly, and finally I have to boot the computer, if I don't manage to kill the NVDA process. Sometimes I can't kill the NVDA process and reboot seems to be the only solution. NVDA doesn't react on key presses and my Braille display (Braillex EL 80c) is empty.

I have never used installed versions of NVDA, and everything has gone correctly until last December when I moved from 32 bit Windows 7 to 64 bit Windows 11 Pro. I am using the same setting files which I used in Windows 7. I put the portable copy to C:nvda (beta version) and C:\nvda2 (Alpha version) and copied the one userconfig folder to these NVDA folders. Is it possible that my problems have something to do with userconfig folder's content, normal text-based files?

Steps to reproduce:

Put the portable NVDA to a folder, i.e. C:\nvda, and start and quit it a few times.

Actual behavior:

NVDA starts very slowly, the speech synthesizer says "Starting NVDA. Please wait..." and nothing happens after this.

Expected behavior:

NVDA starts normally and it can be used normally.

NVDA logs, crash dumps and other attachments:

Here are some lines from the nvda.log file? Should I post the whole file? I'm not sure

Initializing MathPlayer
WARNING - mathPres.initialize (08:06:34.408) - MainThread (12452):
MathPlayer 4 not available
DEBUGWARNING - core.main (08:06:34.408) - MainThread (12452):
Slow starting core (10.44 sec)
IO - speech.speech.speak (08:06:34.408) - MainThread (12452):
Speaking ['Loading NVDA. Please wait...']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (08:06:34.408) - MainThread (12452):
No CLDR data for locale fi_FI
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (08:06:34.408) - MainThread (12452):
No symbol data for locale fi_FI
INFO - core.main (08:06:34.497) - MainThread (12452):
Using wx version 4.2.1 msw (phoenix) wxWidgets 3.2.2.1 with six version 1.16.0
DEBUG - core.main (08:06:34.497) - MainThread (12452):
Initializing braille input
INFO - brailleInput.initialize (08:06:34.497) - MainThread (12452):
Braille input initialized
DEBUG - core.main (08:06:34.497) - MainThread (12452):
Initializing braille
INFO - braille.initialize (08:06:34.497) - MainThread (12452):
Using liblouis version 3.28.0
INFO - braille.initialize (08:06:34.497) - MainThread (12452):
Using pySerial version 3.5
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (08:06:34.497) - MainThread (12452):
registering pre_configSave action: <class 'brailleDisplayDrivers.papenmeier.BrailleDisplayDriver'>
INFO - brailleDisplayDrivers.papenmeier.BrailleDisplayDriver.connectUSB (08:06:34.559) - MainThread (12452):
connectUSB success
INFO - brailleDisplayDrivers.papenmeier.BrailleDisplayDriver.init (08:06:34.617) - MainThread (12452):
Found EL80c
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (08:06:34.617) - MainThread (12452):
loading braille papenmeier
INFO - braille.BrailleHandler._setDisplay (08:06:34.617) - MainThread (12452):
Loaded braille display driver 'papenmeier', current display has 80 cells.
DEBUG - core.main (08:06:34.617) - MainThread (12452):
Initializing vision
DEBUG - core.main (08:06:34.617) - MainThread (12452):
Initializing displayModel
DEBUG - core.main (08:06:34.617) - MainThread (12452):
Initializing GUI
DEBUG - config.isInstalledCopy (08:06:34.627) - MainThread (12452):
Unable to find isInstalledCopy registry key RegistryKey.INSTALLED_COPY- this is not an installed copy.

System configuration

NVDA installed/portable/running from source:

Portable

NVDA version:

2024.1beta4

Windows version:

Microsoft Windows 11 Professional Version 23H2 (OS Build 22631.3007), System Type x64

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

No other software

Other information about your system:

Lenovo ThinkStation P3 Tower with 16 GB RAM

Other questions

Does the issue still occur after restarting your computer?

Yes

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

Alphas and Betas since December 2023 with same results

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

Yes

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

Yes