Update issues

Solid Accounting checks for updates on launch and once per day after that. Updates download in the background; the app applies them on next restart.

"Update available" notification keeps reappearing

The download finished but install didn't complete. Quit the app and relaunch — most installs that interrupt mid-write retry on launch.

If that doesn't help:

  1. macOS: ~/Library/Application Support/com.solidaccounting.app/updater/ contains the staged update. Delete the folder, restart, and the updater will re-download.
  2. Windows: %APPDATA%\com.solidaccounting.app\updater\ — same thing.
  3. Linux: ~/.local/share/com.solidaccounting.app/updater/. The AppImage updater works in-place — make sure the AppImage is in a writable location (not /opt).

"Signature verification failed"

The downloaded update doesn't match the embedded public key. Causes:

  • A corporate proxy is rewriting the download. Whitelist releases.solidaccounting.com and *.b2.amazonaws.com (our CDN).
  • Disk corruption mid-download — delete the staged update and retry.
  • (Rare) Active man-in-the-middle attack. If you see this consistently on a network you trust, contact support before retrying.

We will never ask you to disable signature verification. If you see instructions telling you to, those instructions are not from us.

Update keeps failing on Windows SmartScreen

Windows is over-cautious about new installers. Our cert is EV-signed so this should be rare, but if SmartScreen still blocks:

  1. Right-click the installer → Properties → check Unblock
  2. Run the installer

Or use the Help → Check for updates path which uses the in-app updater that bypasses SmartScreen.

Downgrading to a previous version

Officially unsupported, but possible:

  1. Download the previous version from the GitHub releases page.
  2. Quit the running app.
  3. Install the older version.
  4. Open your file. You may see a "newer schema" warning. If so, restore from a backup taken before the upgrade — the schema may have changed in ways the older version can't read.

If you're downgrading because of a real bug, please file a report first. We'd rather fix it than have you on stale software.

Beta channel

Settings → General → Update channel:

  • Stable (default): production builds, tested
  • Beta: pre-release builds for power users
  • Alpha: nightly builds for internal testing — likely to break

Switching channels takes effect at the next update check.

Updated May 2, 2026
Edit this page on GitHub →
Was this helpful?

We use this to prioritize which docs to improve. No tracking, no email follow-up.