Steps to reproduce:
I have two separate situations, based on what @lukaszgo1 advised me to do. When I attempt a clean start of NVDA using the following command line:
nvda_2023.1.exe -c "C:\Users\brite\OneDrive\Desktop\TEMP NVDA\nowhere" --debug-logging --log-file="C:\Users\brite\OneDrive\Desktop\TEMP NVDA\nvda2023.1_debug.log"
everything behaves as expected. The installer starts and allows me to go through the usual choices when not actually installing, including running as portable from the installer.
However, whether I invoke nvda_2023.1.exe by activating that file in File Explorer or via the following command line:
nvda_2023.1.exe --debug-logging --log-file="C:\Users\brite\OneDrive\Desktop\TEMP NVDA\nvda2023.1_debug_normal-start.log"
what happens, in order, is this:
The usual setup starting tune and dialog box.
Then I get the rising xylophone tones indicating NVDA is starting, a very brief pause, and then a second set of xylophone tones indicating NVDA is starting. From all appearances, the installer starts, exits, and somehow tells 2023.3beta3 to start.
Using the NVDA + N, H, A command to get the NVDA version information, I am shown I am running NVDA 2023.3beta3
Note: the above does not occur, at all, if I am actually kicking off NVDA 2023.1 from a true portable copy by activating nvda.exe
Actual behavior:
Documented in Steps to Reproduce
Expected behavior:
NVDA 2023.1 firing up as it normally should from an installer, rather than triggering NVDA 2023.3.beta3
NVDA logs, crash dumps and other attachments:
nvda2023.1_debug_cleanstart.log
nvda2023.1_debug_normal-start.log
System configuration
NVDA installed/portable/running from source:
Running nvda_2023.1.exe, whether directly by activating that file in file explorer, double clicking, or triggering via the command line as noted in Steps to Reproduce.
NVDA version:
NVDA 2023.1
Windows version:
Windows 11, Version 22H2, Build 22621.2283
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
LG Gram 16, 16GB RAM, i5 12th gen CPU, 1TB NVMe SSD
Other questions
Not applicable in this instance.
Steps to reproduce:
I have two separate situations, based on what @lukaszgo1 advised me to do. When I attempt a clean start of NVDA using the following command line:
everything behaves as expected. The installer starts and allows me to go through the usual choices when not actually installing, including running as portable from the installer.
However, whether I invoke nvda_2023.1.exe by activating that file in File Explorer or via the following command line:
nvda_2023.1.exe --debug-logging --log-file="C:\Users\brite\OneDrive\Desktop\TEMP NVDA\nvda2023.1_debug_normal-start.log"what happens, in order, is this:
The usual setup starting tune and dialog box.
Then I get the rising xylophone tones indicating NVDA is starting, a very brief pause, and then a second set of xylophone tones indicating NVDA is starting. From all appearances, the installer starts, exits, and somehow tells 2023.3beta3 to start.
Using the NVDA + N, H, A command to get the NVDA version information, I am shown I am running NVDA 2023.3beta3
Note: the above does not occur, at all, if I am actually kicking off NVDA 2023.1 from a true portable copy by activating nvda.exe
Actual behavior:
Documented in Steps to Reproduce
Expected behavior:
NVDA 2023.1 firing up as it normally should from an installer, rather than triggering NVDA 2023.3.beta3
NVDA logs, crash dumps and other attachments:
nvda2023.1_debug_cleanstart.log
nvda2023.1_debug_normal-start.log
System configuration
NVDA installed/portable/running from source:
Running nvda_2023.1.exe, whether directly by activating that file in file explorer, double clicking, or triggering via the command line as noted in Steps to Reproduce.
NVDA version:
NVDA 2023.1
Windows version:
Windows 11, Version 22H2, Build 22621.2283
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
LG Gram 16, 16GB RAM, i5 12th gen CPU, 1TB NVMe SSD
Other questions
Not applicable in this instance.