spawn node ENOENT

[budarin]

Describe the bug

Every start VS Code I get the error:

[INFO 11:27:36 PM] [v1.16.0] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 11:27:37 PM] [API] Resolving configs: web-toir/vite.sw.config.mts, web-toir/vite.config.mts
[INFO 11:27:37 PM] [API] Running Vitest v3.0.8 (web-toir/vite.sw.config.mts) with "node C:/Users/Vadim/.vscode/extensions/vitest.explorer-1.16.0/dist/worker.js"
[Error 11:27:37 PM] [Error Error] spawn node ENOENT
Error: spawn node ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)

Reproduction

just start VS Code

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (6) x64 AMD FX(tm)-6300 Six-Core Processor
    Memory: 14.88 GB / 23.90 GB
  Binaries:
    Node: 23.8.0 - ~\.nvm\versions\node\v23.8.0\bin\node.EXE    
    npm: 11.1.0 - ~\.nvm\versions\node\v23.8.0\bin\npm.CMD      
    pnpm: 9.12.0 - ~\.nvm\versions\node\v23.8.0\bin\pnpm.CMD    
  Browsers:
    Edge: Chromium (133.0.3065.92)
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    @vitejs/plugin-react: ^4.3.4 => 4.3.4
    vite: ^6.2.1 => 6.2.1
    vitest: ^3.0.8 => 3.0.8

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[lesjul]

Also have this issue.