-
-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVDA 2022.3.2 install fails on Windows 10 21H2 19044 Server #14379
Comments
Hi, Looks like this user is trying to install NVDA in a Windows 10 Enterprise multi-session environment. I don't know if we officially support this. Thanks. |
I also started to have issues installing from command line from batch file setupcomplete.cmd after imaging. This had worked previously. I am installing on Windows 10 Enterprise LTSC 21H2. Install if ran from command line when logged in. INFO - main (11:04:36.589) - MainThread (3540): INFO - NVDAHelperLocal (11:04:38.870) - MainThread (3540): INFO - NVDAHelperLocal (11:04:43.792) - MainThread (3540): INFO - synthDriverHandler.setSynth (11:04:43.808) - MainThread (3540): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
It looks like the last working version was 2022.2.4 |
Hi @PhillipBrickner , @ThwinAg We believe we have a fix ready for this issue, prepared in #14416. |
@PhillipBrickner @ThwinAg this should now be fixed on alpha as of alpha-27325,304ea7a3. We will release this into 2022.3.3 and 2022.4beta4 |
Yep it installed correctly. Thanks! |
Steps to reproduce:
Reported by email from user
Running NVDA 2022.3.2 launcher with following switches:
--minimal --install-silent --enable-start-on-logon=True
Actual behavior:
Install fails
From log:
Expected behavior:
Install should complete normally.
NVDA logs, crash dumps and other attachments:
Install_NVDA.log
System configuration
NVDA installed/portable/running from source:
NVDA version:
2022.3.2
Windows version:
Windows version: Windows 10 21H2 (10.0.19044) server
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
The text was updated successfully, but these errors were encountered: