Troubleshooting SQLCipher and DB Browser on Windows
Use this hub to quickly diagnose and fix issues when opening, encrypting or working with SQLCipher databases in DB Browser. Start with the checklist, then jump to the specific error you see.
Quick diagnostic checklist
- Passphrase: confirm correctness (caps, layout, clipboard spaces).
- Iterations & page size: ensure they match how the DB was created (SQLCipher basics).
- File origin: was it created by another app/version with different defaults?
- Permissions: can you read/write the file path? Try a local, user‑writable folder.
- Corruption: do plain copies open? Any unexpected shutdowns or disk issues?
- Reopen: after changing a setting, close and reopen to test.
“wrong key” when opening
Most often caused by an incorrect passphrase or mismatched KDF iterations/page size.
- Confirm passphrase (no trailing spaces).
- Match iteration count and page size used at creation.
“file is not a database”
Appears when a SQLCipher DB is opened as plain, or due to corruption.
- Ensure SQLCipher mode and correct parameters.
- Check backups; try another machine or version.
SmartScreen / antivirus prompts
Windows may warn for portable binaries. If you trust the source, proceed via “More info” → “Run anyway”.
See: Getting Started
“cannot open file” / permissions
Move the DB to a user‑writable folder (e.g., Documents) and try again. Avoid network or protected paths.
See: Getting Started
Slow operations
High iteration counts, large files or frequent re‑keying can slow work.
- Batch writes; avoid unnecessary re‑keys.
- Choose iterations appropriate for your hardware.
See: Performance tips
Corruption / integrity errors
Power loss or bad media may corrupt pages. Always keep backups.
- Test on another machine; restore from backup.
- Export what you can; rebuild indexes if needed.
See: Export CSV for salvage strategies.
When to re‑encrypt or migrate
If compatibility issues persist across environments, consider re‑creating the database with standardized parameters, or migrating via CSV/SQL export.
- Standardize KDF iterations and page size across your team.
- Migrate cleanly: Migrate to SQLCipher.
- Keep one authoritative set of parameters in your docs.