Skip to content
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 install fails when Windows 10's Controlled Folder Access is enabled #7696

michaelDCurran opened this issue Oct 25, 2017 · 2 comments


Copy link

@michaelDCurran michaelDCurran commented Oct 25, 2017

Steps to reproduce:

In windows 10 Fall Creaters update:

  • Enable Controlled Folder Access in windows Defender (Virus and Threat Protection -> Virus and Threat Protection Settings -> Controlled Folder Access).
  • Install NVDA either by downloading and running the launcher, or via NVDA's update feature.
  • If installing from the launcher, ensure that the "create desktop shortcut" checkbox is checked. It may be called "keep existing desktop shortcut" if it detects a previous install. Either way, make sure it is checked.
  • Notice that the install fails near the end.

Expected behavior:

The install should succeed with no errors.

Actual behavior:

The install fails, as it cannot create the desktop shortcut in the allUsersDesktop directory, due to Controlled folder Access.

System configuration:

NVDA version: 2017.3
NVDA Installed or portable: installed

Windows version: 10.0.17017

Copy link

@ghost ghost commented Nov 5, 2017

Add the install .exe to allowed apps. Open Windows Defender Security Center, go to Virus and Threat Protection -> Virus and Threat Protection Settings -> Controlled Folder Access and click on Allow an app through Controlled folder access. Navigate to your Downloads folder and select the installer. Be very careful with this and ensure that the app is from a reliable source and only seeking access to needed folders. Controlled folder access is probably an important addition to Windows security and if I was still an IT manager, I would have it enabled on all my users' computers, even though it would mean I would have to do something like this whenever a new app was deployed. It will mean some additional work for you but it is well worth it, unless you have easy access to cryptocurrency that you don't really need. If so, can I have some?


Copy link

@Brian1Gaff Brian1Gaff commented Nov 6, 2017


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants