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

"Access denied" when running a command (Win10) #3392

Closed
saugstauberr opened this issue Jun 1, 2021 · 10 comments
Closed

"Access denied" when running a command (Win10) #3392

saugstauberr opened this issue Jun 1, 2021 · 10 comments
Labels

Comments

@saugstauberr
Copy link

saugstauberr commented Jun 1, 2021

  • Node.js Version: 14.17.0
  • OS: Windows 10
  • Scope (install, code, runtime, meta, other?): Execution
  • Module (and version) (if relevant):

Hello,
I have an issue while running Node.js. After I've installed it without any problems and then tried to run it, I'll always get an "Access denied" error. Also running "npm i" throws me the same error.
I tried to reinstall Node in many different folders, disabled the UAC dialog, gave Admin permissions everywhere but nothing worked. Also I didn't find any solution for my problem.

Please let me know if you have an idea or solution for my problem.

With best regards,
Martin
grafik

@shashank9aug
Copy link

you should look into the system environment variable and check there should be the present Nodejs file path.
e.g: in my case

C:\Program Files\nodejs

@bl-ue
Copy link

bl-ue commented Jun 8, 2021

This is a bit odd because it's just printing a message, no stack trace or even additional error code or anything like that 🤔

@shashank9aug
Copy link

As @ItsMartin030 mentioned his error

 I've installed it without any problems and then tried to run it, I'll always get an "Access denied" error.
 Also running "npm i" throws me the same error.

I think the .exe file path is not accessible so it shows the error "Access denied" while he using npm or node commands.

@saugstauberr
Copy link
Author

saugstauberr commented Jun 8, 2021

I found the solution, it was because a process accessed it. After I stopped it, everything worked fine.

Gonna create another issue on their GitHub, thank you for your help anyways. :)

@shashank9aug
Copy link

I found the solution, it was because a process accessed it. After I stopped it, everything worked fine.

Gonna create another issue on their GitHub, thank you for your help anyways. :)

that's good.

@bl-ue
Copy link

bl-ue commented Jun 8, 2021

What process was it, @ItsMartin030?

@bl-ue
Copy link

bl-ue commented Jun 8, 2021

Linking for reference: snowie2000/mactype#758

@saugstauberr
Copy link
Author

What process was it, @ItsMartin030?

It was MacType.

Copy link

github-actions bot commented May 9, 2024

It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.

@github-actions github-actions bot added the stale label May 9, 2024
Copy link

github-actions bot commented Jun 9, 2024

It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants