Windows repair note

Fix: npm is not recognized in PowerShell

This usually means Node.js is not installed correctly, npm is not on PATH, or the current terminal was opened before PATH changed.

npm : The term 'npm' is not recognized as the name of a cmdlet
Run the free diagnostic Get the full recovery kit
1

Check node and npm separately

It is common for node to work while npm fails in PowerShell. Check both commands and their paths.

node -v
npm -v
where node
where npm
2

Open a fresh terminal

After installing Node.js, old PowerShell windows may not load the updated PATH. Close PowerShell and open it again.

powershell
node -v
npm -v
3

Check npm.cmd if npm fails

If npm.cmd works but npm does not, the issue is likely command resolution or PATH ordering.

npm.cmd -v
Get-Command npm -ErrorAction SilentlyContinue

When to use the paid kit

If the quick checks do not get the app running, the full WiaiKit recovery kit gives the ordered Windows path for npm, Electron, native modules, Visual Studio Build Tools, and Push-to-Talk setup.

Node.js PATHPowerShell command resolutionVS Code terminal

Get the recovery kit for 13 USD

Independent practical material. Not an official OpenAI, Codex, Electron, Node.js, or OpenWhispr product.