Why won't this Electrum wallet open?

What an Electrum wallet file actually is

Electrum keeps its wallets in %APPDATA%\Electrum\wallets on Windows and ~/.electrum/wallets on macOS and Linux. The default one is named default_wallet and has no file extension at all, which is the single most common reason people scroll straight past the thing they are looking for. Copy it somewhere safe before you do anything else, and work only on the copy.

Two separate layers of encryption, and it matters which one you have hit

Electrum can encrypt the wallet file itself, and it separately encrypts the secrets inside it. They are different mechanisms with different consequences, and the whole diagnosis turns on telling them apart.

File encryption has been the default since version 2.8. When it is on, the entire file is one unbroken line of base64 that begins QklFMQ, which is the four bytes BIE1 encoded. You cannot read a single field. Key encryption is what you get when the file itself is readable JSON but the seed and xprv fields inside it hold ciphertext instead of words. And a wallet made with no password at all keeps its seed phrase sitting in the file in plain English, which the tool above will warn you about without printing any of it.

So: if you can open the file in a text editor and see field names, the file is not encrypted and whatever is failing is either the inner keys or structural damage. If you see nothing but a wall of base64, you are hitting file encryption first and cannot learn anything about the contents until it opens.

What is inside an encrypted Electrum wallet, and why that is still useful

An encrypted wallet file is not a featureless blob. Electrum writes a four-byte marker, then a 33-byte one-time public key, then AES-CBC ciphertext, then a 32-byte signature, and base64s the lot. Two facts fall straight out of that layout with no password involved.

First, a complete file is always 69 bytes plus a whole number of 16-byte blocks. If the decoded length does not fit that, characters have been lost, and no password will ever open it. Second, that 33-byte one-time key is a real point on Bitcoin's curve, and whether a given 33 bytes is a real curve point is arithmetic anyone can check. Damage fails that test about half the time. Between them, those two checks tell you whether you have a password problem or a file problem, which are not the same problem and do not have the same fix.

The marker itself is worth reading too. BIE1 means the file is locked with the password you chose. BIE2 means it is locked with a key derived from the wallet's own master public key, which Electrum only does for hardware wallets: there is no forgotten password in that case, there is a missing device or a missing seed.

"It is not possible to recover your password"

That is Electrum's own documentation, and it is accurate: there is no reset, no support channel, and no back door, by design. What it does not mean is that the money is gone. Electrum also says a wallet "can be entirely recovered from its seed", so the question that actually matters is not whether the password can be reset but whether you also have the seed. If you do, restore it into a fresh wallet, set a new password, and the file you cannot open stops being relevant. A surprising number of people never try this, because they assume the file is the wallet. In Electrum, the seed is.

If the seed is gone too, an offline attack on the file is the remaining route, and what decides whether it is worth attempting is how much of the password you remember, not what hardware gets pointed at it. The service side of that is forgotten wallet password recovery.

Electrum seeds are not BIP-39 seeds

This is the most misread thing about Electrum, and it is where the tool above earns its keep. Electrum generates its own seed format and its documentation says plainly that it "does not generate BIP39 seeds". A phrase from Trust Wallet, Ledger, Trezor, MetaMask, or almost anything else is BIP-39, and Electrum will not restore one unless you tell it to.

You can read which standard built a wallet straight out of a readable wallet file, from the derivation path. Electrum's own seeds derive at m for the old pre-SegWit format and m/0' for the SegWit format. A path shaped like m/44'/0'/0', m/49'/0'/0', or m/84'/0'/0' is the BIP-43 account shape used by BIP-39 wallets and hardware devices, which means the wallet was not built from Electrum words. The tool prints the path and says which of those two you have.

There is a second consequence people find out the hard way: when a wallet is restored from a BIP-39 phrase, Electrum stores only the derived master key and never the mnemonic. So no tool can print your recovery words back to you from that wallet file. They have to come from wherever you originally wrote them down.

"Electrum cannot restore wallets from Trust Wallet"

It can, and the failure is two settings deep. First, enter the phrase, click Options, and tick BIP39 seed; without that, Electrum reads a Trust Wallet phrase as an Electrum-native seed and rejects it. Second, set the derivation path to match the coin: Trust Wallet's Bitcoin is native SegWit at m/84'/0'/0', so choose script type native segwit (p2wpkh) and that path, and try m/44'/0'/0' if your addresses start with a 1.

The caveat that catches everyone: Electrum is Bitcoin only. If your Trust Wallet holds Ethereum, BNB, or tokens, the seed is the same but Electrum cannot show any of it. That, and not a lost wallet, is why so many Trust Wallet restores into Electrum look empty. The full walkthrough is in the Electrum won't open guide.

"Your wallet has an unsupported seed version"

Every Electrum wallet file carries a seed_version, which is the storage format number rather than anything to do with your seed phrase. Its practical meaning is the oldest Electrum that can open this file: version 11 needs 2.0, version 18 needs 3.3, version 40 needs 4.1, version 54 needs 4.5. Newer Electrum opens older files by upgrading them, and older Electrum refuses newer ones with "This version of Electrum is too old to open this wallet."

A handful of numbers are refused outright with the message above. Versions 5 through 10 came out of development builds around Electrum 1.9 and were never carried forward; Electrum's own suggestion is to check out the matching build to open them. That is fiddly, but it is a version problem, not a damaged file, and the coins are still there. The tool reads the number off the file and tells you which case you are in.

Standard, imported, multisig, and 2FA are four different recovery problems

A readable wallet file says which one you have in its wallet_type field, and the answers diverge sharply from there.

Standard is one seed, one keystore, and the seed is the whole wallet. Imported means individual keys or addresses were pasted in and there is no seed at all, so whatever is in the file is all there is, and no amount of searching for words will help.

2FA is the one people give up on wrongly. An Electrum two-factor wallet is a 2-of-3 multisig with TrustedCoin as the third cosigner, and Electrum's documentation is explicit that "your seed contains two master private keys in a 2-of-3 security scheme" and that "even if TrustedCoin is compromised or taken offline, your coins are secure as long as you still have the seed". A dead or unpaid co-signing service is an inconvenience, not a loss. The restore has to be done as the two-factor variety, though; restoring a 2FA seed as an ordinary wallet is the standard way to conclude, incorrectly, that the money has vanished.

General multisig is the genuinely harder case, because each cosigner's master public key is part of the wallet's definition and your seed alone does not describe the wallet. The good news is that a readable wallet file contains that definition. The tool counts how many of the cosigner slots hold a private key and compares it against the quorum, which answers "can this file actually spend" directly.

A file full of zeros, and other kinds of damage

Not every unopenable file is encrypted. A wallet that is the right size and contains nothing but zero bytes is the signature of an interrupted write: the filesystem recorded the length and the contents never reached the disk before a crash or a power cut. A file whose JSON starts correctly and then stops mid-value is a truncated copy, which Electrum reports as "Cannot read wallet file. (parsing failed)". Neither is a password problem and neither can be talked out of it.

In both cases the effort belongs somewhere other than the damaged file: another copy in a backup, a sync folder, an old machine, or an email attachment. And if the drive itself is throwing errors while you copy, stop and image it before doing anything else. The longer version is corrupt and deleted wallet file recovery.

The wrong file: config, and everything else in the folder

Electrum's data directory holds a file called config that sits one level above wallets and, like the wallet, has no extension. It holds settings and has never contained a key. It gets sent to recovery services often enough to be worth naming, and the tool identifies it, reads the "last wallet opened" path out of it, and tells you what your wallet file was actually called. On an old machine that filename is sometimes the entire lead you needed.

What this inspector can and can't tell you

It can tell you: which of Electrum's encryption schemes is in the way, whether an encrypted file is structurally complete or has been truncated, the storage version and therefore which Electrum releases can open it, the wallet type, the seed type, whether a seed phrase is even stored in the file, the derivation path and what standard it implies, whether the wallet can sign or is watch-only, how many cosigners a multisig has and how many of them this file can sign with, and the public receiving addresses.

It cannot tell you the password. It never tries, and never will: there is no password field on this page. It cannot decrypt an encrypted file, so for a BIE1 wallet everything above the encryption layer is unreadable and it says so rather than guessing. It cannot recover a file that has been genuinely overwritten at the disk level. And a wallet with addresses in it is not the same thing as a wallet with a balance, which is why the addresses are listed for you to check in a block explorer yourself.

Two pages carry the rest of this. Electrum won't open your wallet is the free written diagnostic, covering all four failure modes in detail. Electrum wallet recovery is the service, for the cases where a wrong move is permanent.