# Start Error after Windows Patchday?
**URL:** https://discourse.nodered.org/t/start-error-after-windows-patchday/87993
**Category:** General
**Tags:** windows
**Created:** [15 May 2024 18:53 UTC](https://discourse.nodered.org/t/start-error-after-windows-patchday/87993 "2024-05-15T18:53:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@RTWE](https://discourse.nodered.org/u/RTWE)
#### Post date: [15 May 2024 18:53 UTC](https://discourse.nodered.org/t/start-error-after-windows-patchday/87993/1 "2024-05-15T18:53:44Z")
My Node-RED instance wont start anymore after installing the patches _KB5037763_ and _KB890830_ to my Windows Server 2016.
error message:
```auto
Welcome to Node-RED
===================
15 May 20:18:15 - [info] Node-RED version: v2.1.3
15 May 20:18:15 - [info] Node.js version: v22.1.0
15 May 20:18:15 - [info] Windows_NT 10.0.14393 x64 LE
15 May 20:18:15 - [error] Failed to start server:
15 May 20:18:15 - [error] Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:760:9)
at Object.execFile (node:child_process:350:17)
at C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\installer.js:581:27
at new Promise ()
at Object.checkPrereq (C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\installer.js:580:16)
at Object.load (C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\index.js:59:22)
at C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\index.js:146:29
(node:3356) [DEP0059] DeprecationWarning: The `util.log API is deprecated. Please use console.log() with a custom formatter or a third-party logger instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
```
Any suggestions?
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [15 May 2024 20:28 UTC](https://discourse.nodered.org/t/start-error-after-windows-patchday/87993/2 "2024-05-15T20:28:13Z")
That version of Node-JS is too new for Node-RED 2.1.3 due to a security patch they did recently
Searching that error "Error: spawn EINVAL" would have lead you to:
- [Not starting on window 11 "Error: spawn EINVAL" - #2 by knolleary](https://discourse.nodered.org/t/not-starting-on-window-11-error-spawn-einval/87153/2)
- [Error: spawn EINVAL - #2 by GogoVega](https://discourse.nodered.org/t/error-spawn-einval/87181/2)
- [Estou tendo problemas para rodar o node red - #2 by jbudd](https://discourse.nodered.org/t/estou-tendo-problemas-para-rodar-o-node-red/87226/2)
- and so on....
In short, update node-red to 3.1.9 or 4.0.0-beta.3
---
### Author:  [@RTWE](https://discourse.nodered.org/u/RTWE)
#### Post date: [16 May 2024 19:26 UTC](https://discourse.nodered.org/t/start-error-after-windows-patchday/87993/3 "2024-05-16T19:26:54Z")
Thank You!
after updating node-red to 3.1.19 via
`npm install -g -unsafe-perm node-red`
everything works fine.
```auto
node-red start
16 May 21:15:35 - [info]
Welcome to Node-RED
===================
16 May 21:15:35 - [info] Node-RED version: v3.1.9
16 May 21:15:35 - [info] Node.js version: v22.1.0
16 May 21:15:35 - [info] Windows_NT 10.0.14393 x64 LE
(node:12684) [DEP0059] DeprecationWarning: The `util.log API is deprecated. Please use console.log() with a custom formatter or a third-party logger instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
16 May 21:15:35 - [info] Loading palette nodes
16 May 21:15:36 - [info] Dashboard version 2.19.4 started at /ui
(node:12684) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
16 May 21:15:36 - [warn] ------------------------------------------------------
16 May 21:15:36 - [warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red
16 May 21:15:36 - [warn] ------------------------------------------------------
16 May 21:15:36 - [info] Settings file : \Users\RTAdm\.node-red\settings.js
16 May 21:15:36 - [info] HTTP Static : C:\Users\RTAdm\.node-red\static > /
16 May 21:15:36 - [info] Context store : 'default' [module=memory]
16 May 21:15:36 - [info] User directory : \Users\RTAdm\.node-red
16 May 21:15:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 May 21:15:36 - [info] Flows file : \Users\RTAdm\.node-red\start
16 May 21:15:36 - [info] Creating new flow file
```
_but_
if I start it via
`C:\Users\RTAdm\AppData\Roaming\npm\node-red.cmd`
then node-red version 2.1.3 starts (I use this for starting node-red via task scheduler)
```auto
PS C:\Users\RTAdm\AppData\Roaming\npm> .\node-red.cmd
16 May 21:19:49 - [info]
Welcome to Node-RED
===================
16 May 21:19:49 - [info] Node-RED version: v2.1.3
16 May 21:19:49 - [info] Node.js version: v22.1.0
16 May 21:19:49 - [info] Windows_NT 10.0.14393 x64 LE
16 May 21:19:49 - [error] Failed to start server:
16 May 21:19:49 - [error] Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:760:9)
at Object.execFile (node:child_process:350:17)
at C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\installer.js:581:27
at new Promise ()
at Object.checkPrereq (C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\installer.js:580:16)
at Object.load (C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\index.js:59:22)
at C:\Users\RTAdm\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\index.js:146:29
(node:7584) [DEP0059] DeprecationWarning: The `util.log API is deprecated. Please use console.log() with a custom formatter or a third-party logger instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
```
Why? Is this the wrong .cmd file? Do I have to uninstall v2.1.3?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [14 August 2024 19:27 UTC](https://discourse.nodered.org/t/start-error-after-windows-patchday/87993/4 "2024-08-14T19:27:28Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.