Wispr Flow keeps prompting for an admin password after updates (macOS, MDM-managed Macs)
Last updated: September 7, 2026
Available on: Mac (MDM-managed devices). Requires an IT admin with access to your MDM and the Wispr Flow admin portal.
If Wispr Flow asks for an admin password on every update, gets flagged by your security software mid-update, or breaks until you reinstall it, the cause is file ownership on the installed app — not the app or the installer. IT applies a one-time fix.
Quick checks
Was Flow installed by your MDM? Copies installed from wisprflow.ai are owned by you and do not prompt.
Do the prompts return after a reinstall? Reinstalling fixes it only until the next MDM install or update.
Who owns the app? Run stat -f%Su "/Applications/Wispr Flow.app" in Terminal. If the owner is root, continue below. If it is your username, contact support.
Why this keeps coming back
MDM installs leave /Applications/Wispr Flow.app owned by root. The updater runs as the signed-in user, so macOS asks for admin credentials before it can write to the app. Standard users cannot authenticate, so the update fails or half-applies and can leave the app broken until it is reinstalled.
Reinstalling from our website gives you a copy you own, so the prompts stop until the next MDM install or update returns ownership to root.
How to fix this
IT deploys the Restore App Ownership post-install script (step 4 of the macOS MDM setup). It returns ownership of /Applications/Wispr Flow.app to the logged-in user after every MDM install, so updates apply silently.
Sign in to admin.wisprflow.ai and open Settings → Organization → MDM.
Download the Restore App Ownership script from step 4, then unzip it.
Deploy it as a post-install action alongside the Wispr Flow installer so it runs after each install or update. In Kandji, use an Auto App postinstall script. Step-by-step instructions exist for Jamf Pro, Kandji, Microsoft Intune, Rippling, Mosyle, Munki, and Fleet.
Verify with stat -f%Su "/Applications/Wispr Flow.app". The owner should be the username, not root.
Note: The script produces no output. It does nothing if the app isn't installed, if no one is logged in (login window or Setup Assistant), or if ownership is already correct. Confirm the result by checking ownership on the device, not by looking for output.
If the app is already broken, reinstall Wispr Flow first, then run the ownership script.
In Kandji, you can also deploy the script as a Custom Script → Audit & Enforce rule for self-healing on every check-in. It skips work when ownership is already correct and never reports failure, so a run cannot trigger a Kandji reinstall.
FAQs
The script fails with "bad substitution"
Unzip the script before running it, and download the file rather than copying its text from a browser, which adds Windows line endings and breaks it. Otherwise you are running an old copy — re-download the zip from the MDM page.
Is this a bad release or a corrupted installer?
No. The .pkg installer and the app are fine, and there is no need to roll back your deployment. This is a file ownership side effect of MDM installs on macOS.
I am an end user without admin rights. What can I do now?
Uninstall and reinstall Wispr Flow from wisprflow.ai/downloads. That copy is owned by you, so updates apply normally until the next MDM install. Send this article to your IT team for the permanent fix; we are happy to work with them directly.
What else does a full macOS MDM deployment need?
Three artifacts: the installer, the Accessibility configuration profile, and this ownership restore script. Catalog entries in some MDM tools ship only the installer, so the other two often need to be added separately. See our guide to deploying Wispr Flow via MDM.
macOS does not permit pre-granting Microphone access via MDM for third-party apps; only Accessibility can be pre-granted, so users still see one microphone prompt on first use.
An optional managed config profile locks update cadence (auto, weekly, bi-weekly, or monthly) so users can't override it.
Still stuck?
Contact support if:
The app owner is your username but prompts continue.
Prompts return after the post-install script is deployed and verified.
Include your macOS version, MDM tool, and the output of stat -f%Su "/Applications/Wispr Flow.app".