BTCRecover found no match: a diagnostic workflow

First establish what actually finished

An exhausted search means BTCRecover did not find a match among the configured candidates and checks. An interrupted process, dependency error or unreadable file is a different outcome. Preserve the final message and command locally, then identify which occurred. The upstream password tutorial and limitations guide are the technical references for run behavior.

Check candidate coverage before speed

Use an invented equivalent to reproduce your rules. Our candidate lab shows how a required suffix removes no-suffix guesses, and how anchors remove alternative orders. If the intended guess is excluded by construction, a faster GPU cannot fix it.

For your actual search, privately check representative candidates: an expected spelling, a no-suffix variant, a capitalization possibility and any intentional spaces. Do not redirect a large real preview into cloud-synced storage or paste it into a public issue. Separate candidate-generation defects from wallet-verification defects.

Check the object being tested

Confirm the original application and backup type. A filename is not a reliable wallet identification method. Verify that you supplied the intended copy, not an unrelated export or another wallet’s backup. If the upstream workflow requires an extraction script, keep track of which source file produced its extracted data. See the extraction reference.

A password recovered for one encrypted file does not prove it belongs to a different file. Conversely, seed recovery and file-password recovery need different verification inputs. Revisit the recovery-path guide when these have become mixed together.

For seeds, check the verification assumptions

Recheck the wallet scheme, known address, additional passphrase, account, path and address limit. A valid mnemonic checksum alone is insufficient. Our checksum and address guide explains the layers. Change one assumption per experiment and label the results.

Build the next search from evidence

Write a brief conclusion: “This run tested these year choices in this order, with at most one case change, against this wallet copy.” Then state the next specific uncertainty. A new candidate file or rule set should have a new search record and save filename; do not silently modify the inputs of a search you intend to restore.

For help planning the next step, email mail@keychainx.io with the wallet application, general backup type and a sanitized error. Do not include the seed, private key or actual password candidates in the initial email.