Configure auto-update policy via MDM (UpdateFrequency)

Available on: Mac and Windows on MDM-managed devices.

Set UpdateFrequency to control how often Wispr Flow checks for updates across your managed devices. This is currently the only MDM-managed app setting Flow reads.

Choose an update schedule

Value	Update-check schedule
auto	Default: automatic checks every 30 minutes to 5 hours.
weekly	Every 7 days.
bi-weekly	Every 14 days.
monthly	Every 30 days.

Automatic updates are on by default. Missing or invalid values fall back to auto. Capitalization and surrounding whitespace do not matter.

For the three scheduled options, each successful check starts a new interval — not policy deployment or a fixed calendar date. Checks run normally until the first successful check. If a clock change leaves the last successful check dated in the future, Flow allows checks again instead of waiting for that date.

Configure the policy

Download the policy files from the Admin Portal under Settings → MDM Rollout (Optional) → Start MDM Setup → Set the update policy (optional). On Windows, use either the registry policy or the PowerShell script.

Mac: configuration profile

The template starts with auto.

Important: The supplied Mac profile disallows user removal.

Download Update policy (Mac, .mobileconfig).
Unzip wispr-flow-managed-config.mobileconfig.
Set the string UpdateFrequency to your chosen schedule.
Deploy the profile through your MDM.

Windows: registry policy

Deploy this machine-wide value through your MDM's registry or policy template:

Setting	Value
Key	`HKLM\SOFTWARE\Policies\WisprAI\Flow`
Name	`UpdateFrequency`
Type	`REG_SZ`
Data	A value from the schedule table.

Windows: PowerShell script

The script starts with weekly. It creates the key if missing, writes a string value, verifies the write, and reports mismatches as errors.

Download Update policy (Windows, .ps1).
Unzip wispr-flow-set-update-frequency.ps1.
Edit $value to your chosen schedule.
Run the script as a post-install action under SYSTEM.

Rippling: upload the Windows script

Prepare and run the script as described above, then:

Zip the edited .ps1 as wispr-flow-set-update-frequency.zip.
Upload the ZIP as a post-install script on the Wispr Flow app.
Set a GPO name.
Verify execution in Rippling's script logs.

Verify or change the policy

Restart Wispr Flow after deploying or changing the policy; editing the policy alone does not refresh Flow.
Confirm UpdateFrequency matches your choice — on Mac, the delivered value in /Library/Managed Preferences/com.electron.wispr-flow.plist; on Windows, the registry entry or your MDM's script execution logs, which also show write failures.

To restore default behavior, set UpdateFrequency to auto before restarting Flow; the managed schedule and next-check display disappear.

If Windows cannot read the policy

Flow uses its last successfully read value, even across restarts, or auto if none exists. Later checks can retry the read; repeated failures keep that fallback for the rest of the session.

What users can expect

The policy schedules checks, not installation times. Scheduled checks and automatic installations require an unlocked, active or idle user session and an internet connection.

No user override: When no update is downloaded and the next check is still in the future, the update button in Settings is disabled and shows “Updates managed by your organization.” with the next check date (no time).
Downloaded updates: Users can restart to apply an already-downloaded update at any time; replacing it with a newer release waits for the next scheduled check.
Automatic installation: Flow waits at least 20 minutes after the last dictation and never installs during dictation or a Notetaker recording. On weekly, bi-weekly or monthly, a focused Flow window or recent typing does not postpone installation, and Flow installs without a restart prompt. The first attempt waits 20 minutes plus up to 60 more; later attempts wait 40, then 80 minutes.
After the restart: Scheduled installations relaunch quietly, bringing back only the Flow Bar. When a user applies an update themselves, the main hub window reopens; if an update does not relaunch, the hub appears once on the next launch.
Failures: Flow retries automatically. After three failed installations, automatic attempts pause for 24 hours, and the “There was an error updating Flow” notification offers “Restart Flow” and “Contact us”.

Warning: Restarting during a dictation or meeting can lose unsaved audio. The “Restart to update?” dialog names the recording in progress and offers “Cancel” (default) or “Restart anyway”.

Still stuck?

A Mac asks for an administrator password during updates — deploy Restore app ownership (Mac, .zsh) (wispr-flow-restore-app-ownership.zsh.zip) from step 4 in the Admin Portal, or follow the admin-password troubleshooting guide. Cancelling that prompt leaves Flow unchanged and shows no update error.
Update failures keep recurring, or the policy still does not take effect after a restart — email support@wisprflow.ai with your MDM provider, the configured value, deployment logs, the device, and the steps you tried.