In which case it sounds like the path to the wallet file might be incorrect... where exactly are the recovered_wallet.dat files located? and what are their exact names?

As mentioned earlier... use the command that has the --datadir=. option in it if you get "no such file or directory __db.001"

As mentioned earlier... use the command that has the --datadir=. option in it if you get "no such file or directory __db.001"

I missed your other question, sorry about that.


Try changing to the Downloads folder using cd C:/Users/Catherine/Downloads and then run the command that HCP posted just now.

---

No you can skip that part and just do the dumping that we're trying to help you get done.  

where is your pywallet.py file? Does the folder "C:\Users\Catherine\Downloads\pywallet\" exist?

If it does exist, does your command prompt say:

The easiest way is to just leave off the --passphrase option... if you don't include it, and the wallet.dat has a passphrase, it won't be able to show the private keys

For instance:


Also, if you get a "No such file or directory" error about there not being a __db.001 file... you will need a --datadir, so the command would be:

Once you're ready to output with the private keys displayed, just remember to add the --passphrase option back

OK, let's take another look at this...

Can you please be more specific about the syntax error message that you were getting when you trying copying the command lines that I recommended earlier? Are you able to copy/paste them from the terminal window?

It's difficult to know what the actual solution is, when the actual problem is not well defined

We will use the commands that HCP wrote earlier in this thread but slightly modify it for our new PyWallet and recovered wallets directory path. Blue is my modifications to the commands which apply to your present scenario (I hope he doesn't mind).


This will make the screen output completely silent, instead redirecting everything to your pywallet-output.txt file. Then, open the pywallet-output.txt file generated in the Downloads folder to see the screen output of PyWallet.

Is is possible for you to post the stack trace that appears for some of these errors: For example this is a "mock" exception that I made up and want you to look for ones that are printed in this format:

In foo.py, line 13:
    a = string[i+1]
IndexError: Requested index out of range

Now it doesn't have to specifically be IndexError, I am interested in any log on the screen that prevents pywallet from working.

Meanwhile since you can see the private keys are on your screen, you can "capture" the screen output to a file by typing at the end of the command "> screen_output.txt". Try adding it at the end of the dumpwallet command and see if you get any private keys into the file.

Do you mean old version of Python, pywallet or both? Anyway, it's better to create new thread rather than hijacking this thread.

What is version of your Python? Newer pywallet version doesn't support Python 3 completely. Have you tried use Python 2.7 and use older version of pywallet (https://github.com/jackjack-jj/pywallet/tree/b52c955f8c93a75745166ebf281448016e1f22e2)?

I'm not even sure you CAN load the recovered .dat file into Bitcoin Core... Pywallet is quite old... and doesn't really work with newer wallet files... so I doubt that the wallet files that it generates will work with newer versions unless you upgrade the wallet file, or run Bitcoin Core in the legacy "non-HD" mode.

First, make several copies of the recovered wallet .dat, to save you having to run the pywallet --recover again if anything goes wrong.

- Then make sure that Bitcoin Core is not running
- Then put one copy of the recovered wallet .dat into the Bitcoin Core Data Directory and rename it "wallet.dat"
- Start Bitcoin Core with the -upgradewallet command

If that doesn't work... try starting Bitcoin Core with -usehd=0 command


If both of those fail, then you're going to have to try and extract the private keys from the recovered wallet dat and import them into a wallet manually.

To achieve that, your best option is to probably to use the pywallet "dumpwallet" command... with the recovered_wallet_1511377727.dat file... and just dump the whole thing out to a text file. If you give it the wallet passphrase that you selected when you did the "recovery", it will also include the private keys

To check that the command is working OK and pywallet can dump the wallet:

To dump the wallet out to a text file, with private keys encrypted (so you can check the addresses):

At this point, you should find a "walletDump-NoKeys.txt" file in "C:\Users\Catherine\Dowloads\pywallet" that you can open with a text editor... you should be able to see all the addresses that have been "recovered". I would suggest searching through these to see if you can find addresses that hold coins (input the addresses on a block explorer like www.blockchain.info).



To dump out the wallet INCLUDING your private keys to the screen ONLY:

To dump out the wallet INCLUDING your private keys to a text file:

You should find a "walletDump-withKeys.txt" in the "C:\Users\Catherine\Dowloads\pywallet" that you can open with a text editor... all your "recovered" addresses and private keys should be visible... the private keys are the ones labelled "sec".

Import the private keys, that match the addresses that have coins, into the wallet of your choice.

I don't think that pywallet can do a low-level scan of the harddisk, it expects a wallet.dat file. And Python would be very slow anyway compared to my C program.