Wispr Flow keeps prompting for an admin password after updates (macOS, MDM-managed Macs)

Last updated: September 19, 2026

Available on: Mac (MDM-managed devices). An IT administrator needs access to your MDM and the Wispr Flow Admin Portal.

If Wispr Flow repeatedly asks for an administrator password after MDM installs or updates, check who owns the installed app. An MDM installation can leave the app owned by root, while Flow's updater runs as the signed-in user.

Check the app's owner

Run this command in Terminal:

stat -f%Su "/Applications/Wispr Flow.app"

  • The result is root: Follow the ownership fix below.

  • The result is the signed-in user's username: Ownership may not be the cause. Contact support with the command's output, macOS version, and MDM provider.

Deploy the permanent fix

  1. Sign in to admin.wisprflow.ai and open the MDM section.

  2. Download and unzip Restore App Ownership. Use the downloaded file rather than copying its contents from a browser.

  3. Attach the script as a post-install action so it runs after each Wispr Flow install or update. In Kandji, use the Wispr Flow Auto App postinstall action.

  4. Run the ownership check again. The result should be the signed-in user's username, rather than root.

When Wispr publishes an updated ownership script, download, unzip, and redeploy the new copy through your MDM.

The script produces no output. It does nothing if Flow is not installed, no user is logged in, or ownership is already correct. Verify the result on the device; a silent script run alone does not prove ownership changed.

For installer, permission-profile, and MDM-provider setup, use Deploy Wispr Flow via MDM. For update scheduling, use Configure auto-update policy via MDM.

If the fix does not work

The app is damaged, empty, or missing

Reinstall Wispr Flow from a fresh download, then deploy the ownership script. Reinstalling without the post-install fix can leave the same problem after the next MDM installation.

The script reports “bad substitution”

Download a fresh script archive from the MDM section and unzip it before deployment. Avoid copying script text from the browser, which can introduce line-ending errors.

Prompts return after another MDM install

Check that the ownership script is attached to every install or update action and runs after the installer. If no user was logged in when it ran, check ownership again after a user signs in. If prompts continue despite verified ownership, contact support.

I do not have administrator rights

Send this article to your IT team for the permanent fix. Reinstalling a fresh copy from wisprflow.ai/downloads can restore a user-owned copy, but another MDM installation can return ownership to root.

When contacting support@wisprflow.ai, include your macOS version, MDM provider, and the ownership-check output.