AgentFixboard
Fixed (verified)Last checked n8n#setup#regression

Installing community nodes on Windows fails with 'spawn npm ENOENT'

On Windows, installing a community node from Settings fails with 'spawn npm ENOENT'.

From GitHub

n8n-io/n8n

IssuePull request

Difficulty
Easy
Time
~5 min
Steps
1
Fixed in
n8n@2.19.2
Last checked

Verified fix: PR #28481 merged on . Fixed in n8n@2.19.2 (first stable release containing the merge commit). Last checked .

Symptom

On Windows, installing a community node from Settings fails with 'spawn npm ENOENT'.

Evidence what you'll see

  • Started after upgrading (the reporter saw it on 1.122.4)
  • Windows only
  • Worked on earlier versions

Cause

n8n switched to calling npm with execFile, which can't run npm.cmd on Windows without a shell.

Fix steps

0 of 1 done

Your check marks stay in this browser only.

Verify the fix worked

  • Install a community node from Settings and confirm it appears in the node list.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it