Windows repair note

Fix: node-gyp cannot find Visual Studio on Windows

Native Node and Electron modules may need C++ build tools, but Build Tools should not be the first guess. Confirm npm, the project folder, the native package, and then Visual Studio C++ detection.

node-gyp error Could not find any Visual Studio installation to use

Run the free diagnostic Get the full recovery kit

Confirm Node and npm first

If npm is not visible in PowerShell, fix PATH before touching Visual Studio. A broken runtime layer can make node-gyp logs misleading.

node -v
npm -v
where.exe node
where.exe npm

Identify the package that is compiling

Do not install Build Tools blindly. First find which dependency falls back to native compilation.

npm install
npm rebuild
npm ls node-gyp
npm ls better-sqlite3

Check Visual Studio C++ detection

If vswhere returns no path with the C++ requirement, the C++ workload is not visible to the toolchain.

& "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath

Check npm toolchain settings

A stale npm Visual Studio setting can point node-gyp at an older toolchain even after Build Tools are installed.

node -v
npm -v
npm config get msvs_version

Install Build Tools only after the log requires it

For Electron and better-sqlite3, the version combination may matter as much as the compiler. Check prebuilt support before rebuilding repeatedly.

# Look for MSBuild, cl.exe, Windows SDK, VCBuild, or node-gyp in the first real error log.

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.

Visual Studio Build ToolsWindows SDKnode-gypElectron native modulesbetter-sqlite3

Get the recovery kit for 13 USD

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