Free diagnostic

Run the free layered diagnostic first

The script is read-only. It checks Runtime, Project, Electron, Native modules, Build Tools, and Voice stack, then prints OK, CHECK, BROKEN, and NEXT ACTION lines.

Open GitHub diagnostic repo Send error log for recovery path

Proof sample

If Electron is broken, this is the first split

A lot of Windows Electron failures look like a bad npm install. The useful split is simpler: does the Electron folder exist, and is the downloaded binary actually there?

Symptom 
Electron failed to install correctly, please delete node_modules/electron and try installing again
Free diagnostic check 
Test-Path .\node_modules\electron
Test-Path .\node_modules\electron\dist\electron.exe
What the result means

If the folder is present but electron.exe is missing, do not wipe the whole project first. Start with the targeted Electron reinstall path.

1

Run the PowerShell diagnostic

Download the script from GitHub, then point it at the broken project folder.

Invoke-WebRequest https://raw.githubusercontent.com/wiaikit/wiaikit-windows-ai-coding-setup-repair/main/wiaikit-windows-ai-coding-setup-check.ps1 -OutFile .\wiaikit-windows-ai-coding-setup-check.ps1
powershell -ExecutionPolicy Bypass -File .\wiaikit-windows-ai-coding-setup-check.ps1 -ProjectPath C:\openwhispr

Start with the first BROKEN or CHECK layer. The paid kit maps those layers to the recovery path.

2

Confirm Node.js and npm are visible

If npm is not recognized, the current terminal probably does not have Node.js on PATH.

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

Expected: Node.js 24+ and a real path for both node and npm. In PowerShell, use where.exe, not bare where. If Node works but npm does not, close PowerShell, open a new one, and test again.

3

Check the project install state

Run this from the project folder only. It should finish without reinstalling Node.js globally.

npm install
npm run dev

If Electron says it failed to install correctly, the full kit gives a clean reinstall path for the Electron package.

4

Identify native-module failures

Native dependencies often need prebuilt binaries. When prebuilds are unavailable, Windows may need Visual Studio Build Tools or MinGW-w64.

npm ls better-sqlite3
npm rebuild

Do not install build tools blindly. First check whether the failing package has a prebuilt binary for your Node and Electron version.

5

Understand Push-to-Talk fallback mode

windows-key-listener fallback mode means the app can still use a fallback approach, but a compiled native listener may be unavailable.

# If the app still runs, test the fallback first.
# If hotkeys fail, then check build tools or tap mode.

The paid kit includes the practical decision order: when to accept fallback, when to compile locally, and when to switch mode.

Stuck after the diagnostic?

Send the layer result plus the first error block. You will get the next recovery step, a clear upstream-bug verdict, or the option for paid manual log review if the setup is in scope.

Do not include tokens, API keys, private repo URLs, or personal data.

Send error log for recovery path Get the full recovery kit for 13 USD

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