Starting 'gatsby develop' on a Windows PowerShell shows "UnauthorizedAccess" error

[ghost]

Description

Today I updated gatsby-cli from v2.7.32 to v2.7.34. Afterwards I could not run 'gatsby develop' anymore.

Steps to reproduce

In the morning, I started my project with the old version of gatsby. During the day, I had to restart and in the course of that, I updated gatsby-cli by running
npm install -g gatsby-cli

Expected result

I expected, that I can re-run gatsby develop.

Actual result

After starting gatsby develop on my PowerShell terminal, I got this error:

+ gatsby
+ ~~~~~~
    + CategoryInfo          : Sicherheitsfehler: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

Sorry, my system language is German, however, I hope you get the point. I was referred to the following page: https:/go.microsoft.com/fwlink/?LinkID=135170, title "About Execution Policies"

By setting the ExecutionPolicy to
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope LocalMachine
on the PowerShell, I was able to start gatsby again.

Environment

System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Binaries:
npm: 6.11.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.17763.1.0
npmPackages:
gatsby: ^2.13.73 => 2.13.73
gatsby-image: ^2.2.10 => 2.2.10
gatsby-plugin-manifest: ^2.2.6 => 2.2.6
gatsby-plugin-offline: ^2.2.7 => 2.2.7
gatsby-plugin-react-helmet: ^3.1.4 => 3.1.4
gatsby-plugin-sharp: ^2.2.13 => 2.2.13
gatsby-source-filesystem: ^2.1.11 => 2.1.11
gatsby-transformer-sharp: ^2.2.7 => 2.2.7

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!

[tim-basic]

@lukitroe you are a god amongst men. Thank you for your service.