error in nvda when a message gains focus in outlook

[fernando-jose-silva]

Steps to reproduce:

On a machine where I have Outlook installed, when I open a message box in Outlook, and there is a message receiving focus, an nvda error appears.

Errors in 'nvda_slave.exe'

x

The logfile 'D:\Users\fernando.silva.LARAMARA\AppData\Roaming\nvda_slave.log' could not be opened: [Errno 13] Permission denied: 'D:\Users\fernando.silva.LARAMARA\/ pp .* ata\Roaming\nvda_slave.log'

OK
Sorry for the way I copied the error, but at this point NVDA becomes completely inactive. I couldn't copy the error with the narrator. I had to use Seeing a i to take a picture of the computer screen and copy the identified text.
The file referenced in the error does not exist.

Actual behavior:

nvda is completely frozen, does not read anything, does not execute a single command.

Expected behavior:

The error does not occur.
If the error occurs, nvda should not be completely frozen.
I have not noticed this error on any other screen.
After closing the error, it is displayed again.
After that, everything works correctly until Outlook is closed and reopened.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

instaled

NVDA version:

nvda.exe, NVDA alpha-34198,67f6cb99

Windows version:

10.0.19045.4957

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

outlook 16.0.5461.1001

Other information about your system:

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.

no

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
log
outlook.txt

[Adriani90]

cc: @michaelDCurran, @seanbudd, @gerald-hartig for triaging. I saw this error also from time to time, it might be something related to NVDA running without admin privileges on a Windows user account that is not an admin which most usual in corporate environments.

[Adriani90]

Or there might be partition restrictions and NVDA cannot write its log to the partition...