Closed christopherpross closed 2 years ago
seanbudd
commented
2 years ago There seems that there is a lot going wrong here.
In the first log, the Windows version is reported as Windows 10 21H1 (10.0.19043)
Do you have any idea why NVDA is reporting the Windows version as Windows 11 21H1 (12.2.20043) in the normal launcher log?
This Windows Version is unreleased and doesn't make sense.
Can you run the normal launcher again to confirm what Windows version is reported, and upload the log?
christopherpross
commented
2 years ago @seanbudd Ok, here are some log-files from starting the normal nvda-launcher. Multible starts because the traceback is diffenrent sometimes. Also I attach a export of the reg values of the path I found in Source/winversion.py. I hope this helps. I have also executed sys.getwindowsversion() it displays: `Microsoft Windows [Version 10.0.19043.1503] (c) Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cpross>python Python 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information.
import sys sys.getwindowsversion() sys.getwindowsversion(major=10, minor=0, build=19043, platform=2, service_pack='') `
nvda-logs
tobyfitch
commented
2 years ago I have the same issue, except I tried all of the launching options. It runs, I see it in the system tray / task manager, but I'm unable to launch the GUI to turn on speech viewer. Would it be possible that its only launching the win11 builds on a win10 machine?
@christopherpross @seanbudd
christopherpross
commented
2 years ago Hey, any suggestions how we can we investigate this further? In this moment I can not work with nvda on this machine. Maybe I can provide more infos or debugging stuff?
seanbudd
commented
2 years ago There's a reported problem with Dell machines causing a memory leak https://support.freedomscientific.com/Support/TechnicalSupport/Bulletin/1786
Do both @tobyfitch and @christopherpross use a Dell machine? Is this a potential cause?
christopherpross
commented
2 years ago Yeah, I use a dell Maschine. Is this book fixable?
seanbudd
commented
2 years ago Try following the steps in the above article to disable "Waves MaxxAudio Service Application" to see if this fixes the issue
christopherpross
commented
2 years ago @seanbudd nope, the issue persits and the MaxxAudioServices was already disabled. Sorry, but that was not the issue. I am frustated because on my private computer, is nvda working fine. Narator and Jaws working too on this system with the issue.
christopherpross
commented
2 years ago @seanbudd nvda-debugdata.zip I have here now a current package for you with 2 minidumps from nvda (installed and portable) both with the crash. In the package is also the logs to the crashes and one log with the working nvda, which I can only start over nvda_uiaccess.exe The MaxxAudioService is completly disabled and when I start normal nvda, don't matter portable or installed, I hear serial error sounds on multible Soundoutputs. Yeah, also tried it that nvda should only find one Audiooutput, this changed nothing. When I can try something or provide some other data, please say it, I am ready to do all, that we find the issue.
tobyfitch
commented
2 years ago @seanbudd - I run a custom built Win10 machine and no, it's not a Dell. This machine isn't eligible for an upgrade to Win11 due to the specs.
NVDA works fine on my work machine that runs the latest Win11.
lukaszgo1
commented
2 years ago @tobyfitch Could you please upload your NVDA log? It can be found in %temp% folder as nvda.log and nvda-old.log. It seems to me that your issue is different to what @christopherpross is experiencing.
tobyfitch
commented
2 years ago @tobyfitch Could you please upload your NVDA log? It can be found in
%temp%folder as nvda.log and nvda-old.log. It seems to me that your issue is different to what @christopherpross is experiencing.
I'll have to circle back. Do you have a tutorial / instructions where I can navigate to the temp folder?
lukaszgo1
commented
2 years ago You can just paste %temp% to the run dialog invoked with Windows+r
christopherpross
commented
2 years ago Hey, are there any updates? Any ideas how this could crash? The disabling of the Wave MaxxAudio Service doesn't have a effect. Sometimes I can see in the log that the nvwave module can not find or access a device but this log message is not good reproducable. In 99% of the cases I get a memoryError in the log or nothing, after braille initialization, that means nvda is very extremly crashed.
In the time, where we try to fix that, should I use uiaccess or nouiaccess? Because I have to work with this computer and without nvda that is not possible.
tobyfitch
commented
2 years ago @christopherpross Sorry, been MIA --- I hope this is what you're looking for. I updated to the new version but still same issues. I can't right click on the icon in the task bar to bring up a contextual menu, nor am I able to launch the GUI for me to check my settings.
feerrenrut
commented
2 years ago @tobyfitch This log is at info level. Please use logging at debug level when reporting issues.
seanbudd
commented
2 years ago While we investigate this further, can you try:
tobyfitch
commented
2 years ago @tobyfitch This log is at info level. Please use logging at debug level when reporting issues.
@seanbudd @feerrenrut - The problem is I can't even access any menu / GUI of NVDA, and I am deaf -- so navigating NVDA without a GUI is impossible for me. I use the Speech Viewer to find my way around NVDA. If you can give me step by step of what to do since I can't access the menu to change the log level.
seanbudd
commented
2 years ago For debug level logging, you can start NVDA from a Windows terminal with the CLI parameter --debug--logging.
christopherpross
commented
2 years ago @seanbudd I have disabled anti-virus software completly and in the following logs, in the first line you can see what I have done. The Wave Maxx-Audio service is deactivated and only nvda_uiaccess.exe is working. In fact no improvement, but see youself in the log. If I can try some other things, just say that. nvda-changed-audiodevice.log nvda-changed-audiodevice-2.log nvda-changed-audiodevice-3.log nvda-changed-audiodriver-to-microsoft.log nvda-changed-audiodriver-to-microsoft-2.log
seanbudd
commented
2 years ago Have you spoken with your system administrator / organisational IT support?
It seems like NVDA is being sandboxed somehow.
nvda.exe is a copy of nvda_uiaccess.exe for an installed copy of NVDA.
Your system is preventing it from reading files (in AppData) and accessing synthesizer dlls.
There is something going on with your system that is changing the access privileges of NVDA.
I'd encourage completely uninstalling and reinstalling and checking to make sure compatibility mode isn't set.
Could you provide screenshots of each tab for the file properties of nvda.exe?
christopherpross
commented
2 years ago @seanbudd interesting, so far I know no sandboxing is done on my system. I will speak with my systemadministrator, maybe we should try to completly reinstall the os and make sure no sandboxing is enabled. I have checked the security tab of the file properties, no strange values I have seen. I will report back what the admin says and will provide screenshots of the file properties, but its german I hope that is ok. Thank you for your support.
seanbudd
commented
2 years ago Thanks @christopherpross That should be fine, I can use OCR and google translate to translate.
christopherpross
commented
2 years ago @seanbudd
here the screenshots that have you requested.
I had searched on my system for a sandbox or similar, but I haven't found such a mechinism. If my Systemadmin says me, that we have a sandbox or something I will that note it here, but I thing not.
christopherpross
commented
2 years ago @seanbudd yeah, my systemadmin confirms that we not have a sandbox solution or something. I am the local admin on my system too.
seanbudd
commented
2 years ago Does renaming nvda.exe to nvda_back.exe fix the problem?
christopherpross
commented
2 years ago @seanbudd
ähm, yeah, that fix the problem. Strange. But I would have to rename this on every update and nvda_slave doesn't know about the changed name...
It is a workaround, but no solution, great idea.
seanbudd
commented
2 years ago I think given this information, there is a problem with your system not with NVDA. Something is causing nvda.exe specifically to be blocked by Windows. I'm not sure what we are able to do about this.
seanbudd
commented
2 years ago As a guess, there is a problem with your registry. I would suggest a last ditch solution of running the COM registration tool with NVDA 2022.1 / the latest alpha and then restarting.
seanbudd
commented
2 years ago Hi @christopherpross - given the nature of the issue, there is nothing we can do to fix this. If you find a solution (e.g. reinstalling Windows), please let us know in case others run into the same problem with their system.
seanbudd
commented
2 years ago Some thing that might point towards the issue is searching the registry for "nvda.exe".
Steps to reproduce:
On my system, I can reproduce this as follows (I know that works perfectly on other systems):
Actual behavior:
Expected behavior:
NVDA should start normally over nvda.exe
System configuration
NVDA installed/portable/running from source:
I have tried all of them, at this moment I write the issue with the nvda-alpha with uiaccess
NVDA version:
I had reproduced this issue with the stable version, latest alpha (NVDA version alpha-24843,3040444a) and from source.
Windows version:
Windows 10 21h1 64Bit on Dell Laditute 5520
Name and version of other software in use when reproducing the issue:
I thing it is something with the audio-component, I use the realtek-driver from dell.
Other information about your system:
I have reinstalled the audio-driver, narrator is working fine.
Other questions
Does the issue still occur after restarting your computer?
Yes, tried serial times
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes:
All versions have this issue
If NVDA add-ons are disabled, is your problem still occurring?
I have no add-ons installed, because I have tried to reinstall nvda.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes, no effect
NVDA-logs
nvda succesful start with "nvda_uiaccess.exe"
nvda start failure over normal launcher