Fix Flow startup and No Model Available errors

Last updated: October 16, 2026

Available on: Mac, Windows, iOS, and Android

If Flow won't start dictation, shows an audio-system error, or fails to transcribe what you said, start with the message on screen. Each one has a different fix.

Quick checks

  1. Check your connection: open any website; if it won't load, reconnect before testing Flow.

  2. Quit and reopen Flow — choose Restart Flow if the error offers it, or follow Quit and relaunch Wispr Flow — then dictate one short phrase.

  3. Update Flow before repeating a failing recording.

  4. Confirm the selected microphone: if you connected a new mic but declined Flow's Switch prompt, the old input is still selected. Test that mic in another recording app — if it's silent there too, the problem is system-level, not Flow.

Follow the action for your error

Message

Next action

Flow is having trouble loading or starting

Choose Restart Flow; if it repeats, use Contact us.

Audio system failed to load

Restart Flow, then contact support if audio still won't start.

Something's not right

Transcription failed; let recovery finish, then use Retry or Open History when offered.

Is your internet connected?

Check the network, then retry the retained audio after reconnecting.

Microphone Permission Required or Microphone access is disabled

Use Grant Permission or Open Settings, then enable microphone access.

Accessibility Permission Required

Choose Open Settings and grant the requested access.

Microphone disconnected

Use Insert to recover text captured before the disconnect, then reconnect or select another input.

Note: On desktop, "Is your internet connected?" can be advisory while recording continues. A session-limit or organization-policy notice is not a microphone failure: follow that notice or contact your administrator. For muted, missing, unavailable, or silent microphones, follow Troubleshooting mic issues.

Check setup for your platform

Mac

  1. Enable Wispr Flow in System Settings → Privacy & Security → Microphone and in Accessibility.

  2. Select a working microphone in Flow. With the MacBook lid closed, use an external mic; if Bluetooth is unreliable, compare a built-in or wired mic.

  3. Restart your Mac and test again if restarting Flow didn't help.

Windows

  1. Open Settings → Privacy & security → Microphone — or Flow's settings link if offered — and enable both microphone access and desktop-app access.

  2. Select another working input in Flow and test it.

  3. Restart the computer if the error persists after restarting Flow.

  4. Update Flow if it opens with no window or a blank window and the microphone never becomes ready. Flow sets the permissions it needs on its install folder during install and update, and repairs them and relaunches once if they change later.

Note: This self-repair applies to standard installer-based installs. If you run Flow from a copied or manually extracted folder, reinstall with the installer from dl.wisprflow.ai.

iPhone

  1. Enable Settings → General → Keyboard → Keyboards → Flow → Allow Full Access and grant Flow microphone access. Flow rechecks both when you return from Settings.

  2. For "Couldn't start audio capture," dismiss the error, close any other app or call using the mic, then tap the microphone to start a fresh recording. Quit and reopen Flow if it repeats.

  3. Wait a moment after opening Flow before switching apps — it may still be getting ready after a cold launch.

Android

  1. Complete the home-screen cards for microphone, overlay, Accessibility, and background operation — see Android setup.

  2. Use Settings → Apps → Wispr Flow → Force stop, reopen Flow, and test again; restart the phone if the problem continues.

Recover saved work

Open History on the device where you dictated. On desktop, a failed dictation appears in Recent Activity with its Retry row as soon as it fails; dictations that finished while the hub was hidden appear when you open it again.

On Mac and Windows, if a long dictation loses its connection near the end, Flow transcribes the leftover audio instead of discarding it. It stays in Processing while it catches up — up to five minutes on a very long recording — then pastes what came back, and refuses new dictations until it finishes. If nothing could be transcribed, you get the usual error with Retry.

Use Retry for eligible saved audio, or Recover on a dismissed transcript when offered. A dictation started while the previous one is still finishing waits its turn, then pastes and saves to History as normal.

Warning: Dismissing a recovery cancels it and can prevent the previous result from pasting. Recovery also requires retained audio: a capture error, deleted recording, or storage policy can leave nothing to retry. See Retry failed transcriptions for the available actions.

Still stuck?

Warning: Reset & restart deletes local data, including transcription history. Use it only when Wispr Flow support directs you to.

Contact support before resetting app data: use Help → Talk to support on desktop, Menu → Talk to Support on iPhone, or Report an issue in the Android drawer. Include the exact error, your device and OS, your microphone, and the checks you tried; a screenshot helps. If a desktop submission fails, your message is copied to the clipboard so you can send it again.