Troubleshooting

SmartScreen blocks the installer

Prefer the Microsoft Store. The direct GitHub installer is known to show an Unknown publisher warning. Download it only from the official TypeWhisper release and compare its SHA-256 hash with the published hash before running it.

Safe installation options

No microphone or wrong microphone

1. Open Windows Settings > Privacy & security > Microphone and allow desktop apps to access it.
2. Choose the input under TypeWhisper > Settings > Dictation, or select Default.
3. For changing headsets, order the microphone priority list; TypeWhisper uses the first available device.
4. Re-run onboarding from the dashboard and check the input level in step 2.

Hotkey does not respond

1. Open Settings > Shortcuts and record the combination again.
2. Choose a combination that Windows or another app has not registered globally.
3. Check workflow-specific hotkeys as well. TypeWhisper prevents conflicts inside the app, but not with other programs.
4. Quit the conflicting app or change one of the shortcuts, then restart TypeWhisper.

Text is not inserted

TypeWhisper first copies the final result to the clipboard and sends Ctrl+V for automatic insertion. Some elevated, protected, or unusual text fields block simulated input.

1. Press Ctrl+V yourself immediately after dictation. The text should still be on the clipboard.
2. Check Settings > Dictation > Auto paste after transcription.
3. Test a regular field such as Notepad. If it works there, the limitation is in the target app.
4. Do not run TypeWhisper with lower privileges than the target app; Windows blocks input across that privilege boundary.

Model or extension is not ready

1. Open Settings > Dictation and verify that the engine and model are installed and selected.
2. Open Integrations > Installed and review the add-on status, configuration, and available updates.
3. Restart TypeWhisper when App restart required appears or after changing local model acceleration.
4. If automatic acceleration fails, try CPU. Use CUDA, Vulkan, or ROCm only with matching hardware and runtime support.

API or CLI cannot reach TypeWhisper

1. Check Settings > Advanced > API Server: enabled, status running, and the expected port.
2. Test curl.exe http://localhost:8978/v1/status, or use the displayed port.
3. Do not delete discovery files while the app is running. Restart TypeWhisper if the port or token does not match the client.
4. With token protection enabled, /v1/status stays public; every other route needs Authorization: Bearer or X-TypeWhisper-API-Token.

API setup and discovery

Export diagnostics

Open Settings > About, review the error log first, and click Export Diagnostics. The JSON file contains app, Windows, and runtime versions, locale, and recorded errors. Review it before sharing and send it only through a trusted support channel.