,

BTCRecover Install + GPU Acceleration on Windows 11 – Seed Recovery Tool

If you have a broken or incomplete crypto wallet backup, the first feeling is usually panic. Maybe your seed phrase has one wrong word. Maybe two words are missing. Maybe the wallet says the recovery phrase is invalid and now you are not sure whether the funds are gone forever.

In self-custody, that kind of problem can feel like nightmare fuel. But if the mistake is small — a transcription error, a swapped word, a few wrong characters in your backup — there may still be a way to recover access.

BTCRecover is one tool I use for this kind of work. In this guide, I will walk through setting it up on a fresh Windows 11 machine, running the basic tests, enabling GPU acceleration with an NVIDIA card, and installing the extended wallet support modules. I will also cover the important safety step: if you run recovery software on your normal desktop, disconnect networking before entering any seed words.

Watch the video.

If this feels too complicated for you right now, or you would rather have help with a sensitive recovery situation, I offer private sessions and trusted recoveries on my website: recovery services and consultations. That said, most people can do the self-hosted setup themselves with patience.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

1. Check Windows S Mode First

The first thing to check is whether your Windows machine is running in S Mode.

On a fresh Windows 11 install, this may be enabled by default. If it is, you will run into problems trying to use command-line tools like cmd, PowerShell scripts, or software installed outside the Microsoft Store.

A quick way to tell is to open Start and try running Command Prompt. If Windows blocks it with a security warning saying that only Microsoft-verified apps can be installed or run, you are likely in S Mode.

Windows 11 S Mode blocking cmd.exe
S Mode blocks command-line tools like cmd.exe

For BTCRecover, we need to install Python packages and run commands from the terminal. That means S Mode is not workable for this setup.

How to switch out of Windows S Mode

The process is usually straightforward:

  1. Try to open Command Prompt or another blocked app.
  2. When Windows shows the warning, choose the option that explains how to leave S Mode.
  3. You will be taken to the Microsoft Store page for switching out of S Mode.
  4. Sign in with your Microsoft account if prompted.
  5. Confirm the switch.

Once it is done, Windows should let you install and run apps from outside the Microsoft Store.

Windows says you have switched out of S mode
Confirmation that S Mode has been disabled

After this step, opening Command Prompt or PowerShell should work normally.

If your machine already opens command-line tools without an S Mode warning, you can skip ahead to the next section.

2. Download BTCRecover and Open the Docs

Next, get the BTCRecover files.

For this walkthrough, I do not use Git. Instead, I download the repository archive from GitHub, save it to my Downloads folder, and extract it there. The exact folder does not matter much as long as you know where it is. For simplicity, keep it in Downloads or another easy-to-find location.

After extracting, you should have a folder containing the BTCRecover files. That is the folder we will use for running commands later.

The documentation is also important because it contains the installation steps and example recovery commands. I follow the basic install and testing process from the docs rather than guessing at commands.

Extracting BTCRecover into the Downloads folder
Extract the downloaded BTCRecover archive

3. Install Python

BTCRecover needs Python. On Windows, there are two main ways to install it:

  1. From python.org using the official installer.
  2. From the Microsoft Store, which can be convenient on newer Windows systems.

If you use the python.org installer, make sure you check the option to add Python to your PATH. If Python is not available in the command line, nothing else will work properly.

Python installer with Add python.exe to PATH visible
When installing from python.org, make sure Python is added to PATH

The Microsoft Store route can be even simpler. On some Windows setups, if you open Command Prompt and type python, Windows may automatically offer the recommended Python version from the Store. You can install it directly from that prompt.

After installation, verify that both of these work in a new terminal:

python
pip

If they show version information or help text instead of an error, you are ready to continue.

Python installed from Microsoft Store and verified in Command Prompt
Typing python after installation should show the Python version

4. Install the Basic Requirements

Now we install the core BTCRecover requirements using pip.

The exact command is shown in the BTCRecover documentation under the installation section. You copy that command, open a terminal inside your extracted BTCRecover folder, and run it.

A convenient way to get into the right folder on Windows is to right-click the BTCRecover folder and choose Open in Terminal. This opens PowerShell at the correct location. PowerShell and Command Prompt are similar enough for most of these commands.

Then paste or type the pip install command from the docs and press Enter.

Installing basic BTCRecover requirements with pip
pip installs the core packages needed for basic recovery

Once that finishes, you can run the built-in tests described in the documentation. If everything passes, your basic installation is working.

At this point, if all you need is a basic Bitcoin or Ethereum wallet recovery, you may already have enough installed to proceed. You do not necessarily need every extended module unless your specific recovery requires one.

5. Run a Basic BIP39 Test

To double-check that the tool works, I run one of the basic seed recovery examples from the documentation. In the video, this is a simple test for a wallet with one missing word in a native SegWit setup.

You should see BTCRecover start running and find the matching seed quickly if the example inputs are correct. This confirms that:

  • Python is working.
  • The core BTCRecover packages are installed.
  • The command syntax is being accepted.
  • Basic recovery logic is functioning.
BTCRecover documentation showing basic seed recovery examples
Use the documented example to verify basic recovery works

Do not paste your real seed words into a connected computer unless you fully understand the risks. For testing, use only the example commands from the docs or harmless placeholder inputs that do not represent your actual wallet.

6. Enable GPU Acceleration with NVIDIA and PyOpenCL

GPU acceleration can make a big difference for some recovery types, especially when searching large keyspaces. In this setup, the machine has an NVIDIA GeForce RTX 5090.

Even if Windows Device Manager already lists the GPU correctly, you may still need to install or update the NVIDIA driver before OpenCL works properly with BTCRecover.

Device Manager showing the NVIDIA RTX 5090
The GPU is visible in Device Manager, but the driver and PyOpenCL are still needed

Install the NVIDIA driver

For a normal desktop PC, the Game Ready Driver from NVIDIA is usually the right choice. Download it for your operating system, run the installer, and accept the defaults unless you have a specific reason not to.

After the driver installs, restart if prompted.

Install PyOpenCL

Back in PowerShell or Command Prompt, install the Python package needed for OpenCL:

pip3 install pyopencl

This may pull in additional dependencies required for GPU support.

Once installed, you can add the --enable-opencl flag to your BTCRecover command. When it works, BTCRecover should detect the NVIDIA OpenCL platform and adjust worker threads based on available GPU memory.

You may see some warnings while compiling the kernel. That can be normal. The important part is that the recovery runs and uses the GPU as expected.

A practical note about CPU versus GPU

The performance benefit from a graphics card varies a lot depending on:

  • Your CPU.
  • Your GPU.
  • The type of recovery you are running.
  • How large the search space is.
  • Current hardware pricing.

In my experience, for many recoveries I handle, a strong multi-core CPU can be very competitive with high-end GPUs, especially when graphics cards are expensive. In this test system, I have an AMD Ryzen 9 9950X alongside the RTX 5090. The GPU is useful, but it is not automatically faster for every job.

If you use a non-NVIDIA OpenCL-compatible card, results may vary. My experience and focus are mostly with GeForce hardware.

7. Install Extended Wallet Support Modules

Some recoveries require extra modules beyond the basic installation. If you try to run one of these without the required package, BTCRecover usually tells you which module is missing and gives you a command to install it.

You do not always need every extended module. But if you want full functionality, or if your recovery type requires additional wallet support, you may need to install the full requirements from the documentation.

When I run the extended install command on Windows, it does not succeed immediately because some packages need build tools and other prerequisites.

Install Visual C++ Build Tools

The first missing piece is usually Microsoft Visual C++ Build Tools. The error message points you in the right direction. You want the Desktop development with C++ workload.

pip error requiring Microsoft Visual C++ 14.0 or greater
This build failure tells us we need the C++ build tools

Download and install the Build Tools from Microsoft, then run the BTCRecover extended requirements command again.

Install Rust Cargo

The next missing piece may be Rust. Some packages require cargo, the Rust package manager. You can get it from rustup.rs by downloading and running the installer.

After installing Rust, close your terminal and open a new one. This is important because the old terminal session will not automatically see the newly installed Rust tools.

Then retry the extended requirements command.

Fix the newer Python environment variable issue

On newer Python versions above 3.12, you may hit another build error related to PyO3 compatibility. The error tells you which environment variable to set.

In PowerShell, copy-and-pasting the full command shown in some errors may not work cleanly. Instead, type $env: first, paste the variable name after it, then add:

= "1"

So the pattern looks like this:

$env:PYO3_USE_ABI3_FORWARD_COMPATIBILITY = "1"
PyO3 error suggesting an environment variable for newer Python
Newer Python versions may need this compatibility variable

After setting that, run the extended requirements command again. Once it completes successfully, your BTCRecover installation should support the extended wallet features described in the documentation.

8. Test SLIP39 Recovery

With the extended modules installed, I test a SLIP39 recovery example from the usage examples section of the docs. This is useful because SLIP39 wallets use a different structure than standard BIP39 phrases, so they may require additional support.

If the command runs without missing-module errors and completes as expected, that confirms the extended installation is working.

At this stage, the system has:

  • Basic BTCRecover functionality.
  • GPU acceleration enabled for supported recoveries.
  • Extended wallet support modules installed.
  • A successful SLIP39 test run.

That means all of the main functionality available in BTCRecover should now work on that machine.

9. Critical Safety Advice: Air-Gap Before Entering Seed Words

This is the part I cannot stress enough.

If you are running BTCRecover on your normal desktop computer, disconnect networking before you enter any real seed words into the system.

That means:

  1. Turn off Wi-Fi.
  2. Unplug Ethernet.
  3. Disable Bluetooth if possible.
  4. Do not connect external drives that may be compromised unless you understand the risk.
  5. Only reconnect after you have recovered the correct seed and moved funds away from it.

The reason is simple: if your computer has malware, a connected network gives that malware a chance to leak sensitive information. A recovery session can expose seed material or derived keys in memory, logs, command history, or other places you may not expect.

If you are serious about recovering real funds, the safest approach is to use an air-gapped machine: a clean Windows installation on hardware with no network capability, or at least a system where all networking is physically disabled before any sensitive input happens.

Using your normal desktop can be fine for learning BTCRecover and practicing syntax. The command structure is generally consistent across platforms, so it is useful to become comfortable with the tool first. But do not mix that practice environment with real seed words unless you have taken proper precautions.

Conclusion

BTCRecover can be a powerful tool when your wallet backup has a small error or missing piece. On Windows 11, the setup involves a few moving parts: disabling S Mode if necessary, installing Python, adding the core requirements, optionally enabling NVIDIA GPU acceleration with PyOpenCL, and installing extended modules when needed.

The good news is that once it works, you can test it safely using documented examples before ever touching your real recovery phrase. The even more important part is security: keep networking disconnected before entering seed words on a normal desktop, and reconnect only after the funds are moved to safety.

I hope this guide helps you get BTCRecover running smoothly. If you get stuck, leave a comment with where you are having trouble — but please do not post real seed words, private keys, or passwords in public comments. And if you would like help with a specific recovery situation, you can request a private session or trusted recovery through my website: recovery services and consultations.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides