MultiBit.online

    MultiBit Crashed: Recovery and Troubleshooting Guide

    What to do when MultiBit wallet crashes. Learn how to recover your wallet data, locate backup files, and restore access to your Bitcoin.

    Important Warning
    If MultiBit crashed unexpectedly, don't panic. Your Bitcoin is stored in wallet files on your computer, not in the application itself. This guide will help you recover your funds.

    Understanding MultiBit Crashes

    MultiBit, being discontinued software from 2017, is increasingly prone to crashes on modern systems. Crashes can occur for various reasons, but the important thing to understand is that a crash doesn't mean your Bitcoin is lost. Your private keys and wallet data are stored separately from the application.

    Common Crash Causes

    • Memory Exhaustion: MultiBit may run out of memory during blockchain sync or when processing large wallets
    • Corrupted Blockchain Data: The local SPV chain file became corrupted during sync or shutdown
    • Java Errors: Incompatible Java versions or missing libraries cause runtime exceptions
    • Network Issues: Failed connections to Bitcoin peers can cause hangs that lead to crashes
    • Disk Space: Insufficient disk space for blockchain data or temp files
    • Corrupted Wallet File: The .wallet file itself may have become damaged

    Immediate Steps After a Crash

    Step 1: Don't Try to Force It

    After a crash, don't immediately try to reopen MultiBit repeatedly. Each failed launch attempt could potentially corrupt your wallet data further. Take a moment to assess the situation.

    Step 2: Locate Your Wallet Files

    Before doing anything else, locate and backup your wallet files:

    # Windows:

    %APPDATA%\MultiBit\ (Classic)

    %APPDATA%\MultiBitHD\ (HD)

    # macOS:

    ~/Library/Application Support/MultiBit/ (Classic)

    ~/Library/Application Support/MultiBitHD/ (HD)

    # Linux:

    ~/.multibit/ (Classic)

    ~/.MultiBitHD/ (HD)

    Copy the entire folder to a safe location (USB drive, cloud storage, or another folder) before attempting any recovery steps.

    Step 3: Check for Crash Logs

    MultiBit may have created a crash log that explains what went wrong. Look for:

    # In the MultiBit data folder, look for:

    multibit.log

    multibit-hd.log

    hs_err_pid*.log (Java crash dump)

    Attempting to Reopen MultiBit

    Method 1: Delete the SPV Chain File

    The most common fix for crashes is deleting the blockchain sync file. This forces MultiBit to resync from scratch. While syncing is likely to fail (since MultiBit servers are offline), this often allows the wallet to open.

    # Delete these files:

    multibit.spvchain (Classic)

    spvchain/ (HD - delete the folder)

    multibit.checkpoints (if present)

    After deleting, try opening MultiBit again. It may show a sync error or zero balance, but if it opens, you can export your private keys.

    Method 2: Restore from Backup

    MultiBit creates automatic backups of your wallet. Look for backup files in:

    # Classic backup files:

    *.wallet.backup

    rolling-backup/

    # HD backup files:

    zip-backup/

    rolling-backup/

    To restore: rename the current .wallet file to .wallet.corrupted, then rename the backup file to the original name.

    Method 3: Try Safe Mode / Clean Start

    You can try launching MultiBit with a fresh configuration:

    1. Backup your entire MultiBit data folder
    2. Rename the folder (e.g., MultiBit to MultiBit-backup)
    3. Launch MultiBit - it will create a fresh installation
    4. Close MultiBit
    5. Copy only your .wallet and .key files from the backup to the new folder
    6. Reopen MultiBit

    Method 4: Reinstall MultiBit

    If the application itself is corrupted, try a fresh installation:

    1. Backup your wallet files first
    2. Uninstall MultiBit
    3. Download a fresh copy from our download page
    4. Install MultiBit
    5. Copy your wallet files back to the data folder

    Recovering Wallet Data Without MultiBit

    If MultiBit won't open no matter what you try, you can still recover your Bitcoin by extracting private keys directly from the wallet files.

    MultiBit Classic Recovery

    MultiBit Classic stores private keys in .key files (exported keys) or encrypted in .wallet files.

    • .key files: Can be imported directly into Electrum
    • .wallet files: Require decryption with your password
    • .wallet.aes files: Double-encrypted, more complex recovery

    MultiBit HD Recovery

    MultiBit HD uses BIP39 seed phrases. If you wrote down your 12 or 24 word recovery phrase when creating the wallet, you can recover your Bitcoin easily.

    • With seed phrase: Enter it into Electrum with the correct derivation path
    • Without seed phrase: More complex - you'll need the mbhd.yaml or mbhd.wallet.aes files

    Preventing Future Data Loss

    Once you recover access to your Bitcoin, take these steps to prevent future problems:

    1. Migrate to a Modern Wallet

    MultiBit is no longer maintained and will only become less reliable over time. Transfer your Bitcoin to Electrum, Sparrow, or a hardware wallet as soon as you recover access.

    2. Export Private Keys

    If MultiBit is working now, export all private keys and store them securely. Don't just rely on the application.

    3. Write Down Seed Phrases

    When creating a new wallet, write down the seed phrase on paper and store it safely. Never store it digitally.

    4. Test Your Backups

    After migrating, test that your backup actually works by restoring it on a different device before relying on it.

    Remember: Your Bitcoin Is Recoverable

    A MultiBit crash is frustrating, but it doesn't mean your Bitcoin is gone. The private keys that control your Bitcoin are stored in files on your computer. As long as you have those files and remember your password, recovery is possible.

    If you're struggling with recovery, take your time. Don't delete any files until you're certain they're not needed. Consider seeking professional help if you have a significant amount of Bitcoin at stake.

    Version-Specific Guides