npm error code 1

[golden cipher]

Im trying to install but keep getting this error

Windows PowerShell
Copyright (C) Microsoft Corporation. Todos los derechos reservados.

Instale la versión más reciente de PowerShell para obtener nuevas características y mejoras. https://aka.ms/PSWindows

PS C:\WINDOWS\system32> iwr -useb https://openclaw.ai/install.ps1 | iex

OpenClaw Installer

[OK] Windows detected
[] Existing OpenClaw installation detected
[OK] Node.js v24.13.1 found
[] Installing OpenClaw (openclaw@latest)...
node.exe : npm error code 1
En línea: 1 Carácter: 1

• & "C:\Program Files\nodejs/node.exe" "C:\Program Files\nodejs/node_mo ...

•   + CategoryInfo          : NotSpecified: (npm error code 1:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
  
  
  

I have tried installing through power shell and cmd without success

[fathom furnace]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[devout quail]

Try to reinstalling node js. https://nodejs.org/en/download

[golden cipher]

thanks, i just typed openclaw onboard and it worked

[idle thunder]

The npm error code 1 you’re seeing when running the Windows install script usually happens because PowerShell is using a stale PATH or can’t actually call npm/git even though the script says it found them. On Windows the installer checks for Node/npm, but the actual install step can fail if Git isn’t installed or if your shell hasn’t picked up the updated PATH after installing Node. A reliable way to fix this is to close all open PowerShell/terminal windows, install Git for Windows (so npm can fetch dependencies), then open a fresh elevated PowerShell and rerun the installer. If rebuilding the environment still fails, install Node.js from its official installer, verify that npm and git work in the same shell (where npm and git --version), and then run:

iwr -useb https://openclaw.ai/install.ps1 | iex

This refreshes the PATH so npm can actually be invoked and avoids the “npm error code 1” problem most people hit on Windows.

[golden cipher]

I did it but I'm still getting the same issue however if I type openclaw onboard it works but I cannot connect it to a cli

[idle thunder]

Since openclaw onboard works, OpenClaw is installed correctly. The issue is likely that the global npm bin path isn’t properly linked to your CLI environment.

Please check where OpenClaw is installed:

where openclaw
npm config get prefix

If where openclaw returns nothing, reinstall it globally:

npm install -g openclaw

Then confirm the global npm path (usually something like C:\Users\YourName\AppData\Roaming\npm) is included in your System PATH. If it’s missing, add it manually via:

System Properties → Environment Variables → Path → Edit → Add the npm global folder

After that, completely close all terminals and reopen PowerShell, then test:

openclaw --version

If it still doesn’t connect to CLI, try running it directly via:

npx openclaw

That bypasses PATH issues and confirms whether it’s strictly an environment variable problem.

Let me know what where openclaw returns — that will tell us exactly where it’s breaking.

[golden cipher]

Really appreciate your help. this is what happens when running the where

C:\Windows\System32>where openclaw
INFORMACIÓN: no se pudo encontrar ningún archivo para los patrones dados.

C:\Windows\System32>npm config get prefix
C:\Users\Lou\AppData\Roaming\npm