# Unable to update the Node-RED on win10

**URL:** <https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487>\
**Category:** General\
**Created:** [12 April 2023 10:14 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487 "2023-04-12T10:14:27Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nerevar](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@nerevar](https://discourse.nodered.org/u/nerevar)\
**Post date:** [12 April 2023 10:14 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/1 "2023-04-12T10:14:27Z")

</div>

Hi,

I'm having some problems with one of installed library so I decided to update Node-RED first.

Upon opening an elevated CMD I asked for a node version:

```auto
C:\Windows\system32>node --version && npm --version
v14.16.1
6.14.12

```

Then I tried to update Node-RED by typing: `npm install -g –unsafe-perm node-red`.  
The result came OK:

```auto
C:\Users\Administrator\AppData\Roaming\npm\node-red-pi -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\node-red\bin\node-red-pi
C:\Users\Administrator\AppData\Roaming\npm\node-red -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\node-red\red.js
+ node-red@3.0.2
updated 1 package in 16.747s

```

Then I exited the evelated CMD and run my .bat script and end up with that:

```auto
12 Apr 12:13:36 - [info] Node-RED version: v2.1.6
12 Apr 12:13:36 - [info] Node.js version: v14.16.1
12 Apr 12:13:36 - [info] Windows_NT 10.0.19045 x64 LE
12 Apr 12:13:37 - [info] Loading palette nodes
12 Apr 12:13:39 - [info] mDashboard version 2.19.4-beta started at /mui
12 Apr 12:13:42 - [info] Dashboard version 2.30.0 started at /ui

```

Why it's still at 2.1.6?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 April 2023 10:27 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/2 "2023-04-12T10:27:17Z")

</div>

> [@nerevar](#):
>
> Why it's still at 2.1.6?

First note: On windows, npm global is global to the user (not the computer).

So, it looks like you used the account "Administrator" which means you have updated node-red for that account.

How did you open the elevated CMD?

* * *

Personally, on windows, I always adjust NPM to set the global install path to something commonly accessible (e.g. `c:\ProgramData`) to avoid these types of issue. Better still, run Node-RED on a linux box (or inside WSL2 on your windows box 🙂 )

---

<div class="post-metadata">

**Author:** ![nerevar](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@nerevar](https://discourse.nodered.org/u/nerevar)\
**Post date:** [12 April 2023 10:41 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/3 "2023-04-12T10:41:09Z")

</div>

> [@Steve-Mcl](#):
>
> > [@nerevar](#):
> >
> > Why it's still at 2.1.6?
> 
> So, it looks like you used the account "Administrator" which means you have updated node-red for that account.
> 
> How did you open the elevated CMD?

I got the admin pass from the IT dept 🙂

I used the elevated version because I thought I wouldn't be able to install it without an admin pass as I can't the regular win programs.

Thank you

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 April 2023 11:10 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/4 "2023-04-12T11:10:47Z")

</div>

> [@Steve-Mcl](#):
>
> Personally, on windows, I always adjust NPM to set the global install path to something commonly accessible (e.g. `c:\ProgramData`) to avoid these types of issue. Better still, run Node-RED on a linux box (or inside WSL2 on your windows box 🙂 )

Or do what I do and install Node-RED locally rather than globally and avoid all that hassle.

> [@nerevar](#):
>
> I got the admin pass from the IT dept

😦

If they did that in our organisation they would be out of a job immediately!

---

<div class="post-metadata">

**Author:** ![nerevar](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@nerevar](https://discourse.nodered.org/u/nerevar)\
**Post date:** [12 April 2023 11:16 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/5 "2023-04-12T11:16:29Z")

</div>

Its and admin pass only for my PC and its used only to make changes on my PC (to install programs). It lasts 7 days until it resets

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 April 2023 11:54 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/6 "2023-04-12T11:54:07Z")

</div>

Yes, we don't allow end users to have that at all 🙂

I recently had to put in a complaint against a desktop support engineer who was onsite and installed some software that a user asked them directly for. We have a catalogue of allowed software and no manual installs are allowed (though we do allow users to install/run software that does not require admin rights).

---

<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:** [26 April 2023 11:54 UTC](https://discourse.nodered.org/t/unable-to-update-the-node-red-on-win10/77487/7 "2023-04-26T11:54:31Z")

</div>

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