# Can't start NR on a new Windows 10 PC

**URL:** <https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819>\
**Category:** General\
**Created:** [27 October 2021 10:02 UTC](https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819 "2021-10-27T10:02:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnd](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@johnd](https://discourse.nodered.org/u/johnd)\
**Post date:** [27 October 2021 10:02 UTC](https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819/1 "2021-10-27T10:02:05Z")

</div>

Running Powershell **as Administrator** under Win10:Home entering node-red at the prompt gives 'node-red.ps1 cannot be loaded because running scripts is disabled on  
this system. For more information, see about\_Execution\_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.'

This is a personal PC with a default install. I could spend an hour or two fiddling with Execution Policies without really knowing exactly what I'm doing. Is there a simple fix please that doesn't also open me up to potentially running some malware scripts?

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [27 October 2021 10:06 UTC](https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819/2 "2021-10-27T10:06:40Z")

</div>

Why are you trying to run Node-RED as Administrator? it shouldn't need it.

---

<div class="post-metadata">

**Author:** ![johnd](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@johnd](https://discourse.nodered.org/u/johnd)\
**Post date:** [27 October 2021 10:39 UTC](https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819/3 "2021-10-27T10:39:57Z")

</div>

Doesn't make any difference whether I run Powershell as Admin or not.

But I've just tried reverting to Command Prompt and - hooray - that works OK. Obviously Powershell under fully updated Win10 must be invoking some extra security checks that Command Prompt doesn't do.

Not sure whether I'll run into other issues under Windows - I could potentially run on a Pi instead, but Windows is my default desktop machine and it's just quicker and easier to use that PC. Anyway, problem solved for the time being. Sorry, I probably reached for support too quickly, but it looked like a bigger/more obscure issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [10 November 2021 10:40 UTC](https://discourse.nodered.org/t/cant-start-nr-on-a-new-windows-10-pc/52819/4 "2021-11-10T10:40:11Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.