Before you continue
- Do not delete or overwrite original wallet data.
- Make at least two copies before attempting any repair.
- Preserve the original folder structure where possible.
- Do not install random tools found through search advertisements.
- Do not enter wallet words into a website.
- Do not send private keys, wallet files or passwords through ordinary email.
- Verify software signatures and hashes where possible.
- Verify at least one historical Bitcoin address before assuming a wallet is correct.
- After recovery, transfer funds to a newly generated, maintained wallet.
The short answer
spvchain/checkpoints files (never the wallet file) — or skip the app and restore your seed / extract Classic keys directly. Verify your known receiving addresses on an independent block explorer before drawing conclusions.Why MultiBit stops opening
MultiBit was discontinued in 2017 and depends on an old Java runtime. On modern Windows and macOS it commonly fails to start because the system Java is too new, missing, or 32-bit while the app expects 64-bit. The other classic culprits are a corrupted sync file (stuck at "syncing"), leftover lock files from a crash, or a corrupted .wallet file.
Step 1 — back up the wallet file first
Before changing anything, copy your wallet data somewhere safe: .wallet/.key files for Classic, and mbhd.wallet.aes plus your seed phrase for HD. Your private keys live in these files — the app is disposable, the keys are not.
Step 2 — fix Java errors
MultiBit Classic was built against Java 8-era runtimes. If it crashes instantly or shows a Java error, install a 64-bit Java 8 runtime and make sure it's the active JVM before launching MultiBit — ideally inside an isolated offline virtual machine configured for the matching historical OS and runtime, rather than downgrading your normal system-wide Java. On macOS, Gatekeeper may also block the unsigned app — right-click → Open once to allow it.
Step 3 — clear the stuck sync
If MultiBit opens but hangs at "syncing" or shows an empty balance, the cached blockchain headers (spvchain, checkpoints) are likely stale or corrupted. Close the app, rename only those files (add .disabled), and relaunch so it rebuilds them. Don't permanently delete anything until recovery is complete. Never delete the .wallet file while doing this.
Step 4 — remove leftover lock files
A crashed session can leave a .lock file that stops a new instance from opening. Close everything, confirm no MultiBit process is still running, then rename any .lock file in the MultiBit data folder and try again. Deleting a lock while the wallet is still running can cause concurrent access or corruption.
Step 5 — recover without the app at all
You don't actually need MultiBit to run to reach your bitcoin:
- HD: restore your 12-, 18- or 24-word seed in Electrum (BIP39, path
m/0') — see the seed restore guide. - Classic: import unencrypted
.keyexports, or read the.walletfile with a carefully vetted open-source tool (verify its source and hashes, run it offline) to extract the keys — see exporting private keys.