Could not load wallet file: the error message was null

HCP

legendary

Activity: 2086

Merit: 4314

If you're using Windows 10, it could quite possibly be a "permission" error... I was attempting something the other night and some Python scripts were kicking out errors because some of the new Windows 10 defender and security settings attempt to block reading/writing from some C:\ folders Undecided

Try starting the command prompt as administrator:

1. Click the "Start" button (press Windows key)
2. Type: command prompt - you should see something like this:

3. Click the "Run as administrator" option on the right hand side

You should see the command prompt open with admin privileges:

Note how it says "Administrator: command prompt" in the title bar... give that a go and see if the Python script works ok then.

wooly7

newbie

Activity: 1

Merit: 0

HI all,

I am also having and issue accessing my Multibit classic Wallet, it says the null message.

I have tried using python to run the scripts but keep getting this

IOError: [Errno 2] No such file or directory: Freshy.Wallet

running directory C:\Python27\Scripts\multibit_recovery-master\decrypt_multibit_classic_walletkeys.py Freshy.wallet.

The .Wallet file is in that directory and it doesnt load the scrips

IF anyone has an idea please let me know.

Thanks all.
Wooly

radowch

newbie

Activity: 1

Merit: 0

Quote from: HI-TEC99 on May 26, 2017, 12:56:44 PM

Quote from: HELLNAUT on May 26, 2017, 10:41:18 AM

Hi All

Im having this same problem and trying to download other versions of multibit and the same error is being returned.
i reverted back to all versions below 5.18 with zero success.

ive made backup of my wallet already as well just incase.
is there anything else i can try doing?

appreciate the help.

Can you remember if you put a password on your wallet? If you didn't try opening your wallet file in notepad and looking for "org.bitcoi[Suspicious link removed]oduction" at the start of it. Newer wallets are in a format called protobuf, and newer wallets without a password definitely start with "org.bitcoi[Suspicious link removed]oduction". I'm not sure what older format wallets start with.

If you have a newer format of wallet without a password the instructions in the quote below might work. Any hex editor should work as well as the one I linked to in the quote,

If you have an older format wallet (called serialised format) you can try adapting the instructions in the quote. I can't test them because I can't find a download for an old enough version of multibit. You search for "75 71 00 7e 00 11 00 00 00 41". If you find that series of bytes you probably have an older format wallet. In that case you can either try using the instructions at this link.

https://bitcointalksearch.org/topic/m.909038

Alternatively you can search for each 20 in the file and copy the 32 bytes following every instance of 20. They might be private keys. If you remove any spaces and put them into the offline webpage described in the quote it will reject any false positives, and show any real private keys in a range of formats you can import into electrum.

Quote

Since version 0.4.0 multibit classic wallet files are in a format called Google protocol buffer format (protobuf). Open a file with a .wallet extension in a hex editor and look for the following sequence of bytes 08 01 12 20. The next 32 bytes after that should be your private key in hex format. After you get your private key in hex format you can convert it to a normal format using an offline copy of the bitaddress website.

I tested this on an unencrypted wallet (one with no password) in multibit version 0.5.1.6 and it worked for me.

This is the hex editor I used, although any other is probably sufficient.

http[Suspicious link removed]ditor.org/home.php

This is the bitaddress website. I advise you not to directly paste private keys into it.

https://www.bitaddress.org/

Instead look for this link at the bottom of the page and use it to download a zipped copy you can run offline.

https://github.com/pointbiz/bitaddress.org/archive/v3.3.0.zip

This is my multibit wallet file opened in the hex editor with the bytes 08 01 12 20 that precede a private key highlighted.

https://i.imgur.com/AjyUKQG.png

This is the 32 bytes of a private key (in hex format) highlighted.

https://i.imgur.com/dpTWlkS.png

This is the 32 bytes of a private key (in hex format) copied directly from the hex editor into notepad.

https://i.imgur.com/q3Gx5JW.png

This is the 32 bytes of a private key after removing the spaces in notepad.

https://i.imgur.com/zAHJn0q.png

This is the private key copied from notepad and pasted into an offline copy of the bitaddress wedsite. Click the view details button to get the private key converted to normal formats.

https://i.imgur.com/ocV54EW.png

This is my multibit wallet's address 1F84fkbMng6dJpGZmtycRbUe72B7XSYbeT shown on the right hand side of bitaddress. Every raw private key can convert into two different bitcoin addresses, which is why there's two.

https://i.imgur.com/NtL8U7X.png

This is my multibit wallet's address 1F84fkbMng6dJpGZmtycRbUe72B7XSYbeT shown in multibit.

https://i.imgur.com/CAeWY5t.png

You can import your private key into the wallet of your choice to get control of yours coins back. Electrum's a good choice.

If you install electrum you can use these instructions to import your private keys from multibit into it.

http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

Hey man,

my name is Jorge and I am from Madrid. I don't know you and you don't know me but you just became my friend. You just helped me recover some money with your replies at as i was having serious issues recovering my old multibit wallet. I finally got to extract a private key and recover my btc.

So I just wanted to thank you and encorage you to keep helping others, you are so fucking good at it and we, the ignorant people of the internet, need guys like you so badly.

Cheers mate!

Lucius

legendary

Activity: 3220

Merit: 5628

Blackjack.fun-Free Raffle-Join&Win $50🎲

Quote from: HCP on June 14, 2017, 08:27:18 PM

Quote from: Lucius on June 14, 2017, 10:47:18 AM

Only thing I will try is to install new copy of MB and then import my private keys,just to check is wallet.dat file causes this problem,but if your explanation is correct then MultiBit is no longer for use-some say it has been so for long time.

Yep... MBC is basically "abandoned"... they claim it is in "maintenance mode", but given they haven't even fixed their "current" version (MBHD), I very much doubt that MBC will be updated ever.

Quote from: https://multibit.org/releases.html

MultiBit Classic
MultiBit Classic is:

free and open source under the MIT licence
designed to work directly with any Bitcoin full node (no servers)
not related to the Bitcoin Classic full node project
a legacy product so you should upgrade to MultiBit HD
It is now considered to be a legacy product and is in maintenance mode. This means that only essential security and network compatibility updates will be made to the codebase.

The security model of MultiBit Classic is weaker than MultiBit HD so we only recommend using it if you have private keys that cannot be migrated.

Note that release numbers are not continuous but are based on distributions made available through the main website

I remove my wallet and all files and install fresh copy of MultiBit Classic-import my private keys and wallet is sync and working normal,I even send one transaction.But when I close wallet and open again there is no balance/wallet,just empty MB with big 0.Nothing else can not be done regarding this problem,so advice to anyone to just send your coins to some other wallet.

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: Lucius on June 14, 2017, 10:47:18 AM

Only thing I will try is to install new copy of MB and then import my private keys,just to check is wallet.dat file causes this problem,but if your explanation is correct then MultiBit is no longer for use-some say it has been so for long time.

Yep... MBC is basically "abandoned"... they claim it is in "maintenance mode", but given they haven't even fixed their "current" version (MBHD), I very much doubt that MBC will be updated ever.

Quote from: https://multibit.org/releases.html

MultiBit Classic
MultiBit Classic is:

free and open source under the MIT licence
designed to work directly with any Bitcoin full node (no servers)
not related to the Bitcoin Classic full node project
a legacy product so you should upgrade to MultiBit HD
It is now considered to be a legacy product and is in maintenance mode. This means that only essential security and network compatibility updates will be made to the codebase.

The security model of MultiBit Classic is weaker than MultiBit HD so we only recommend using it if you have private keys that cannot be migrated.

Note that release numbers are not continuous but are based on distributions made available through the main website

Lucius

legendary

Activity: 3220

Merit: 5628

Blackjack.fun-Free Raffle-Join&Win $50🎲

Quote from: HCP on June 13, 2017, 09:37:47 PM

Quote from: Lucius on June 13, 2017, 09:54:02 AM

I delete spv file and wallet is start to sync and on some 20% it stop and start again from 0.For full sync it take 2+ hour but after closing and starting wallet again it just start to sync again.I check log data and there are some errors recorded:

Loading wallet from 'C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet'
com.google.bitcoin.store.UnreadableWalletException: Transaction did not deserialize completely

This looks pretty much exactly like the error plaguing MultiBit HD at the moment... Something got changed with the way transaction hashes are calculated back in Feb... I believe a "Version" field got added in to the mix... https://github.com/bitcoinj/bitcoinj/commit/be09b620626681c9e51a211ee314a34cb7958a12

Newer versions of bitcoinj obviously work... as they have this new modification, but MultiBit Classic and MultiBit HD both use an older bitcoinj library... so they don't have the version field and therefore generate a hash that is different... the hash comparison fails... and the very obscure error message comes out that "the wallet could not be loaded." Undecided

At this point, I don't think there is anything you can do to make MBC start working properly again Sad

Unless you feel like recompiling with an up-to-date bitcoinj library included. Tongue

There is pretty much zero chance of this bug ever being fixed in MBC by the Devs as MBC is no longer developed or maintained from what I can tell... and it isn't looking all that great for MBHD either! I reported the issue to them like a month ago... and no sign of an update as yet Undecided

I suggest you let it sync up fully... DON'T close the wallet... then export your keys (Tools-> "Export Private Keys")... DON'T put a password on the file:

Then you can open the .key file in a text editor and get all your keys and import/sweep them into another wallet... Personally, I recommend Electrum as a solid replacement for MBC and MBHD users.

Only thing I will try is to install new copy of MB and then import my private keys,just to check is wallet.dat file causes this problem,but if your explanation is correct then MultiBit is no longer for use-some say it has been so for long time.

I wrote already that now I use Electrum,have my private keys export long time ago from MB.Thanks for help&advice again

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: Lucius on June 13, 2017, 09:54:02 AM

I delete spv file and wallet is start to sync and on some 20% it stop and start again from 0.For full sync it take 2+ hour but after closing and starting wallet again it just start to sync again.I check log data and there are some errors recorded:

Loading wallet from 'C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet'
com.google.bitcoin.store.UnreadableWalletException: Transaction did not deserialize completely

This looks pretty much exactly like the error plaguing MultiBit HD at the moment... Something got changed with the way transaction hashes are calculated back in Feb... I believe a "Version" field got added in to the mix... https://github.com/bitcoinj/bitcoinj/commit/be09b620626681c9e51a211ee314a34cb7958a12

Newer versions of bitcoinj obviously work... as they have this new modification, but MultiBit Classic and MultiBit HD both use an older bitcoinj library... so they don't have the version field and therefore generate a hash that is different... the hash comparison fails... and the very obscure error message comes out that "the wallet could not be loaded." Undecided

At this point, I don't think there is anything you can do to make MBC start working properly again Sad

Unless you feel like recompiling with an up-to-date bitcoinj library included. Tongue

There is pretty much zero chance of this bug ever being fixed in MBC by the Devs as MBC is no longer developed or maintained from what I can tell... and it isn't looking all that great for MBHD either! I reported the issue to them like a month ago... and no sign of an update as yet Undecided

I suggest you let it sync up fully... DON'T close the wallet... then export your keys (Tools-> "Export Private Keys")... DON'T put a password on the file:

Then you can open the .key file in a text editor and get all your keys and import/sweep them into another wallet... Personally, I recommend Electrum as a solid replacement for MBC and MBHD users.

Lucius

legendary

Activity: 3220

Merit: 5628

Blackjack.fun-Free Raffle-Join&Win $50🎲

Quote from: NeuroticFish on June 13, 2017, 05:07:25 AM

Quote from: Lucius on June 12, 2017, 10:32:06 AM

I am still using old Multibit Classic 0.5.19 and yesterday when I was open wallet there is some message that could not load wallet/or something like that,it just start to sync and after some time after sync everything is working.Today I open wallet again and same thing happened,so it is time to import private keys in other wallet.I read that maybe some of files(spv chain file) is corrupted so wallet is sync every time when is open,someone who had a similar experience?

I had this problem in the past. After 2-3 such silly restarts, it stabilized and had the data OK. But my guess is that I was just lucky.
However, I did the same as you back then: I switched to Electrum and I am happy with that choice.

A word of advice though: keep your private key (if you use the same wallet) or the seed words (if you made a new wallet) somewhere safe. Even Electrum is not perfect - some cry from time to time that they cannot start Electrum and it's better to have your back covered.

No luck for me with MultiBit Classic this time,so Electrum is now my new wallet-have some small problems so far but my coins are safe,I export private keys long time ago

Quote from: HCP on June 13, 2017, 07:01:21 AM

Quote from: Lucius on June 13, 2017, 04:58:46 AM

I just checked and message is that The wallet "C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet" could not be loaded. Loading the backup wallet.I have two wallet in MB and this is always working without problem,now for some reason my main wallet is not loading after open MB.

Ahhhh ok. I suspect that this might be similar to the MultiBitHD issue with "Password did not unlock the wallet". There may be a transaction that is failing a "hash" calculation because the bitcoinj library is out of date. Which makes the app think your wallet is corrupt when it isn't.

I think I've seen another case of this, but can't find the thread. Undecided

If it still errors out after you have finished syncing, can you check the debug log in %appdata%/MultiBit/log directory and see if you get anything more specific error-wise.

I delete spv file and wallet is start to sync and on some 20% it stop and start again from 0.For full sync it take 2+ hour but after closing and starting wallet again it just start to sync again.I check log data and there are some errors recorded:

Loading wallet from 'C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet'
com.google.bitcoin.store.UnreadableWalletException: Transaction did not deserialize completely

ERROR c.g.bitcoin.net.ConnectionHandler - Error writing message to connection, closing connection java.nio.channels.CancelledKeyException

It seems that there is some serious problem,some time ago I have also similar problem with Multi Doge wallet and even after clean install and many attempts I did not manage to run that wallet again.

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: Lucius on June 13, 2017, 04:58:46 AM

I just checked and message is that The wallet "C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet" could not be loaded. Loading the backup wallet.I have two wallet in MB and this is always working without problem,now for some reason my main wallet is not loading after open MB.

Ahhhh ok. I suspect that this might be similar to the MultiBitHD issue with "Password did not unlock the wallet". There may be a transaction that is failing a "hash" calculation because the bitcoinj library is out of date. Which makes the app think your wallet is corrupt when it isn't.

I think I've seen another case of this, but can't find the thread. Undecided

If it still errors out after you have finished syncing, can you check the debug log in %appdata%/MultiBit/log directory and see if you get anything more specific error-wise.

NeuroticFish

legendary

Activity: 3500

Merit: 6205

Looking for campaign manager? Contact icopress!

Quote from: Lucius on June 12, 2017, 10:32:06 AM

I am still using old Multibit Classic 0.5.19 and yesterday when I was open wallet there is some message that could not load wallet/or something like that,it just start to sync and after some time after sync everything is working.Today I open wallet again and same thing happened,so it is time to import private keys in other wallet.I read that maybe some of files(spv chain file) is corrupted so wallet is sync every time when is open,someone who had a similar experience?

I had this problem in the past. After 2-3 such silly restarts, it stabilized and had the data OK. But my guess is that I was just lucky.
However, I did the same as you back then: I switched to Electrum and I am happy with that choice.

A word of advice though: keep your private key (if you use the same wallet) or the seed words (if you made a new wallet) somewhere safe. Even Electrum is not perfect - some cry from time to time that they cannot start Electrum and it's better to have your back covered.

Lucius

legendary

Activity: 3220

Merit: 5628

Blackjack.fun-Free Raffle-Join&Win $50🎲

Quote from: HCP on June 12, 2017, 06:51:47 PM

Are you getting an error message relating to a "BlockStoreException"?? If so, you could try the following:

1. Shut down MB Classic.
2. Backup the files in your "%appdata%/MultiBit" directory.
NOTE: For windows 7-10, this is usually something like c:\Users\YOURPCUSERNAME\AppData\Roaming\MultiBit
Examples for OSX/Linux here: https://multibit.org/help/v0.5/help_troubleshooting.html

3. Delete the multibit.spvchain from your "%appdata%/MultiBit" directory.
4. Open MB Classic and let it sync.

If that still doesn't help, can you look in "View -> Messages" and see if there are any error messages posted there... if there isn't anything obvious there, have a look in the multibit.log file that should be in "%appdata%/MultiBit/log" directory.

Also, you should really upgrade to a better wallet. MBC 0.5.19 is no longer maintained or supported by the devs... the max fee it will use allow you to use is 0.0005 btc which will be a max of ~220 sats/byte) and you may find your transactions always take a long time to confirm (especially with the current 300+ sats/byte fee levels!)

I just checked and message is that The wallet "C:\Users\Home\AppData\Roaming\MultiBit\multibit.wallet" could not be loaded. Loading the backup wallet.I have two wallet in MB and this is always working without problem,now for some reason my main wallet is not loading after open MB.

I have backup of all files and private keys so I delete spvchain file and open wallet,same message is show again and I choose option to reset blockchain and transaction,now waiting to wallet sync.

Regarding upgrading to new wallet,I am already import my private keys to Electrum,thanks for help and advice

HCP

legendary

Activity: 2086

Merit: 4314

Are you getting an error message relating to a "BlockStoreException"?? If so, you could try the following:

1. Shut down MB Classic.
2. Backup the files in your "%appdata%/MultiBit" directory.
NOTE: For windows 7-10, this is usually something like c:\Users\YOURPCUSERNAME\AppData\Roaming\MultiBit
Examples for OSX/Linux here: https://multibit.org/help/v0.5/help_troubleshooting.html

3. Delete the multibit.spvchain from your "%appdata%/MultiBit" directory.
4. Open MB Classic and let it sync.

If that still doesn't help, can you look in "View -> Messages" and see if there are any error messages posted there... if there isn't anything obvious there, have a look in the multibit.log file that should be in "%appdata%/MultiBit/log" directory.

Also, you should really upgrade to a better wallet. MBC 0.5.19 is no longer maintained or supported by the devs... the max fee it will use allow you to use is 0.0005 btc which will be a max of ~220 sats/byte) and you may find your transactions always take a long time to confirm (especially with the current 300+ sats/byte fee levels!)

Lucius

legendary

Activity: 3220

Merit: 5628

Blackjack.fun-Free Raffle-Join&Win $50🎲

I am still using old Multibit Classic 0.5.19 and yesterday when I was open wallet there is some message that could not load wallet/or something like that,it just start to sync and after some time after sync everything is working.Today I open wallet again and same thing happened,so it is time to import private keys in other wallet.I read that maybe some of files(spv chain file) is corrupted so wallet is sync every time when is open,someone who had a similar experience?

HCP

legendary

Activity: 2086

Merit: 4314

Oohhhhhhhh OK... so YAY! #greatSuccess Cheesy

strider1973

newbie

Activity: 18

Merit: 0

Quote from: HCP on June 10, 2017, 12:25:02 AM

Quote from: strider1973 on June 09, 2017, 08:47:19 AM

Thank you HCP.

It was a real pain, but thanks to your scripts I was able to recover a fraction of a BTC that was sent to my Mutlibit 0.5.18 installation. And I couldn't access the wallet file anymore due to the error message

Firstly, you're welcome...

secondly, So you weren't able to get all of the coins from your wallet? Huh

I'm wondering if maybe my script is not finding all the UTXO's that it should... I am fairly sure it will only find "confirmed" coins... so if you had an inbound transaction that was unconfirmed, it won't have found any coins in that address and would not have put out the private key...

Let me know, and I can probably create a script that will just dump ALL the keys from the wallet... I should probably do that just to be safe I guess... Undecided

No, the script worked well! The output of your script were about 8 keys, only the last key contained the address where the fraction of the BTC (0.07 BTC) were sent to about 2 weeks ago. So the whole "exercise" was just about recovering the whole 0.07 BTC ("a fraction of a BTC"), where I finally succeeded.

And next time I use the command line I know how to copy-paste text from it, thank you very much HI-TEC99!

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: strider1973 on June 09, 2017, 08:47:19 AM

Thank you HCP.

It was a real pain, but thanks to your scripts I was able to recover a fraction of a BTC that was sent to my Mutlibit 0.5.18 installation. And I couldn't access the wallet file anymore due to the error message

Firstly, you're welcome...

secondly, So you weren't able to get all of the coins from your wallet? Huh

I'm wondering if maybe my script is not finding all the UTXO's that it should... I am fairly sure it will only find "confirmed" coins... so if you had an inbound transaction that was unconfirmed, it won't have found any coins in that address and would not have put out the private key...

Let me know, and I can probably create a script that will just dump ALL the keys from the wallet... I should probably do that just to be safe I guess... Undecided

HI-TEC99

legendary

Activity: 2772

Merit: 2846

Quote from: strider1973 on June 09, 2017, 08:47:19 AM

Quote from: HCP on May 27, 2017, 05:18:42 AM

I have some python scripts that will extract the keys from your wallet if you have the password: https://github.com/HardCorePawn/multibit_recovery

If you have a ".key" file, then use decrypt_multibit_classic_keys.py
If you have a ".wallet" file, then use decrypt_multibit_classic_walletkeys.py

Thank you HCP.

It was a real pain, but thanks to your scripts I was able to recover a fraction of a BTC that was sent to my Mutlibit 0.5.18 installation. And I couldn't access the wallet file anymore due to the error message

Could not load the wallet file "C:\..." The error message was "null"

I had to use the full command line to Python (so c:\Pytohn27\python dectrypt_..." instead of just "python") to make it work. I got the decripted keys, wrote them off the screen (copy-pasting didn't seem to work in MS-DOS) and sweeped them into Electrum.

So thank you again for your help!

It's great you got your coins back.

If you want to copy-paste from the command line then click the small icon at the top left of the command window. A menu appears that you can use to select everything, then copy it. Alternatively you can select something, then press your enter key to copy it.

strider1973

newbie

Activity: 18

Merit: 0

Quote from: HCP on May 27, 2017, 05:18:42 AM

I have some python scripts that will extract the keys from your wallet if you have the password: https://github.com/HardCorePawn/multibit_recovery

If you have a ".key" file, then use decrypt_multibit_classic_keys.py
If you have a ".wallet" file, then use decrypt_multibit_classic_walletkeys.py

Thank you HCP.

It was a real pain, but thanks to your scripts I was able to recover a fraction of a BTC that was sent to my Mutlibit 0.5.18 installation. And I couldn't access the wallet file anymore due to the error message

Could not load the wallet file "C:\..." The error message was "null"

I had to use the full command line to Python (so c:\Pytohn27\python dectrypt_..." instead of just "python") to make it work. I got the decripted keys, wrote them off the screen (copy-pasting didn't seem to work in MS-DOS) and sweeped them into Electrum.

So thank you again for your help!

HELLNAUT

newbie

Activity: 16

Merit: 0

http://imgur.com/a/pYfkL

Does that look right?

HCP

legendary

Activity: 2086

Merit: 4314

Looks like you haven't installed the required python libraries... https://github.com/HardCorePawn/multibit_recovery#windows

try this command:

Code:

C:\Python27\Scripts\pip install protobuf pylibscrypt bitcoin

I PM'd you my Skype address... feel free to to hit me up there, it might be faster than using Forum Posts/PMs

HELLNAUT

newbie

Activity: 16

Merit: 0

http://imgur.com/a/bX0Le

This is the next error with what ive managed to gain so far?
not quiet sure what this means.

HCP

legendary

Activity: 2086

Merit: 4314

You're getting there... but you need to "cd" (aka change directory) into the Programming Studies/multibit_recovery-master folder...

So... once you have done f: and you have the f:> prompt... type:

Code:

cd "Programming Studies"
cd "multibit_recovery-master

Note: adjust the spelling and stuff as required... it's 0730 hrs and I just finished a 12hr night shift... and I'm typing this from my phone... Tongue

Anyway, you should end up with the prompt that looks like:

F:\Programming Studies\multibit_recovery-master>

Then you can run the python scripts using the commands from before.

As for your new error... that is the exact same error that MultiBit HD users are starting to see. I believe it is related to the use of outdated bitcoinj libraries.

Still no fix for MultiBit HD as far as I'm aware... and MB Classic is no longer developed, so it's probably never going to be fixed. Undecided

HELLNAUT

newbie

Activity: 16

Merit: 0

My python 2.7 was installed to my C drive while the script you wrote
is in my F drive.

What would the code look like then?
is there any chance you can give me the precise code on here and from the screen
shots i previously posted?

im super noob at this Sad

http://imgur.com/a/ibRTw

below screen shot is my attempt at trying different variation of it.
http://imgur.com/a/rTMxf

in the windows Command line.

so to give you abit of an idea,

python 2.7 is installed to c:
and the scripts you wrote are saved to my F:programming studies/multibit_recovery-master
my wallet file and key file are in F:programming studies/multibit_recovery-master

from the screen shots ive provided i hope this helps.

thank you again kindly for your assistance through this nightmare.

-----------------------------------------------------------------------------------
Ok this is interesting, there is a new error being generated by multibit 5.12 when i tried reopening my wallet file on there.
first it was the null error and now its a serialisation error.

screen shot is as below, this is not the null error anymore but something different.
I hope this doesnt mean my wallet is corrupted...
http://imgur.com/a/9Wlp7

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: HELLNAUT on May 27, 2017, 05:25:11 PM

Ok ive gone to the github and downloaded the files and created its own directory for it.
I got a syntax error being generated: from attempting to recover the wallets.
http://imgur.com/a/svuQM
this is what I've changed it to.
ran the below commands in the python command line.
python decrypt_multibit_classic_walletkeys.py multibit.wallet <--- your instructions
python decrypt_multibit_classic_walletkeys.py new beginning.wallet <----what I've done.
-------------------------------------------------------------------------------------------------------------
python decrypt_multibit_classic_keys.py multibit-\new beginning-20170526193454.key
^
my wallet file name & key file both attempted
http://imgur.com/a/TJT3y
have i done the right thing here?

Close... but you don't run it from the "Python" commandline... you just run it from the normal windows command line Wink

And make sure you are in the right folder... so looking at your screen shot, you'll want to be in: F:\Programming Studies\multibit_recovery-master

Your command prompt should look like:

F:\Programming Studies\multibit_recover-master>

NOTE: Your wallet has a space in the name, which means you'll need to use "quotes" around the name (or just change the filename and remove the space, either way will work)... so your command should be:

Code:

python decrypt_multibit_classic_walletkeys.py "new beginning.wallet"

if you get:

Quote

'python' is not recognized as an internal or external command,
operable program or batch file.

you'll need to use the full path to the Python executable:

Code:

C:\Python27\python.exe decrypt_multibit_classic_walletkeys.py "new beginning.wallet"

strider1973

newbie

Activity: 18

Merit: 0

I have the same issue with Multibit 0.5.18.

I created a new address to receive BTC. And when I wanted to open the wallet, I got "could not load wallet file" and "the error message was "null""

I've tried to install Phyton and to use the scripts mentioned above, but I just get the message: "Import error: No module named 'google'"

Any help is very welcome...

HELLNAUT

newbie

Activity: 16

Merit: 0

Ok ive gone to the github and downloaded the files and created its own directory for it.

I got a syntax error being generated: from attempting to recover the wallets.

http://imgur.com/a/svuQM

this is what I've changed it to.

ran the below commands in the python command line.

python decrypt_multibit_classic_walletkeys.py multibit.wallet <--- your instructions

python decrypt_multibit_classic_walletkeys.py new beginning.wallet <----what I've done.

-------------------------------------------------------------------------------------------------------------

python decrypt_multibit_classic_keys.py multibit-\new beginning-20170526193454.key
^
my wallet file name & key file both attempted

http://imgur.com/a/TJT3y

have i done the right thing here?

the file names that are on the screen shots were created by multibit and unchanged.
all though the only thing i changed was copying 1 file into the python directory.
which was the wallet file I'm trying to recover and then the wallet file with the random numbers as in the above
screen shot.

I believe this is the datestamp file new beginning-20170526193454.key

Id like to thank you again for the help
through this hell im facing.

HCP

legendary

Activity: 2086

Merit: 4314

I have some python scripts that will extract the keys from your wallet if you have the password: https://github.com/HardCorePawn/multibit_recovery

If you have a ".key" file, then use decrypt_multibit_classic_keys.py
If you have a ".wallet" file, then use decrypt_multibit_classic_walletkeys.py

HI-TEC99

legendary

Activity: 2772

Merit: 2846

Quote from: HELLNAUT on May 27, 2017, 01:18:40 AM

I remember the password i placed on the wallet.
strangly enough i downloaded hex editor and went through to find the private keys but had no success.

good chance because it was created with 5.18 multibit classic.
the encoding is different.

im also unable to find the hex value with the screen shot provided.

Those instructions won't work if there is a password on the wallet. If there's a password on it then its contents are encrypted (scrambled). If it's encrypted you can't read the private keys inside the wallet, or see the sequences of bytes that precede them.

HELLNAUT

newbie

Activity: 16

Merit: 0

I remember the password i placed on the wallet.
strangly enough i downloaded hex editor and went through to find the private keys but had no success.

good chance because it was created with 5.18 multibit classic.
the encoding is different.

im also unable to find the hex value with the screen shot provided.

HI-TEC99

legendary

Activity: 2772

Merit: 2846

Quote from: HELLNAUT on May 26, 2017, 10:41:18 AM

Hi All

Im having this same problem and trying to download other versions of multibit and the same error is being returned.
i reverted back to all versions below 5.18 with zero success.

ive made backup of my wallet already as well just incase.
is there anything else i can try doing?

appreciate the help.

Can you remember if you put a password on your wallet? If you didn't try opening your wallet file in notepad and looking for "org.bitcoin.production" at the start of it. Newer wallets are in a format called protobuf, and newer wallets without a password definitely start with "org.bitcoin.production". I'm not sure what older format wallets start with.

If you have a newer format of wallet without a password the instructions in the quote below might work. Any hex editor should work as well as the one I linked to in the quote,

If you have an older format wallet (called serialised format) you can try adapting the instructions in the quote. I can't test them because I can't find a download for an old enough version of multibit. You search for "75 71 00 7e 00 11 00 00 00 41". If you find that series of bytes you probably have an older format wallet. In that case you can either try using the instructions at this link.

https://bitcointalksearch.org/topic/m.909038

Alternatively you can search for each 20 in the file and copy the 32 bytes following every instance of 20. They might be private keys. If you remove any spaces and put them into the offline webpage described in the quote it will reject any false positives, and show any real private keys in a range of formats you can import into electrum.

Quote

Since version 0.4.0 multibit classic wallet files are in a format called Google protocol buffer format (protobuf). Open a file with a .wallet extension in a hex editor and look for the following sequence of bytes 08 01 12 20. The next 32 bytes after that should be your private key in hex format. After you get your private key in hex format you can convert it to a normal format using an offline copy of the bitaddress website.

I tested this on an unencrypted wallet (one with no password) in multibit version 0.5.1.6 and it worked for me.

This is the hex editor I used, although any other is probably sufficient.

http://www.wxhexeditor.org/home.php

This is the bitaddress website. I advise you not to directly paste private keys into it.

https://www.bitaddress.org/

Instead look for this link at the bottom of the page and use it to download a zipped copy you can run offline.

https://github.com/pointbiz/bitaddress.org/archive/v3.3.0.zip

This is my multibit wallet file opened in the hex editor with the bytes 08 01 12 20 that precede a private key highlighted.

This is the 32 bytes of a private key (in hex format) highlighted.

This is the 32 bytes of a private key (in hex format) copied directly from the hex editor into notepad.

This is the 32 bytes of a private key after removing the spaces in notepad.

This is the private key copied from notepad and pasted into an offline copy of the bitaddress wedsite. Click the view details button to get the private key converted to normal formats.

This is my multibit wallet's address 1F84fkbMng6dJpGZmtycRbUe72B7XSYbeT shown on the right hand side of bitaddress. Every raw private key can convert into two different bitcoin addresses, which is why there's two.

This is my multibit wallet's address 1F84fkbMng6dJpGZmtycRbUe72B7XSYbeT shown in multibit.

You can import your private key into the wallet of your choice to get control of yours coins back. Electrum's a good choice.

If you install electrum you can use these instructions to import your private keys from multibit into it.

http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

HELLNAUT

newbie

Activity: 16

Merit: 0

Hi All

Im having this same problem and trying to download other versions of multibit and the same error is being returned.
i reverted back to all versions below 5.18 with zero success.

ive made backup of my wallet already as well just incase.
is there anything else i can try doing?

appreciate the help.

icanscript

hero member

Activity: 686

Merit: 502

Quote from: jim618 on May 07, 2015, 06:48:09 AM

If it is a _very_ old wallet it could be in the format that was used in the very early days of bitcoinj/ MultiBit.

These wallets were in a format called 'serialised' that isn't supported by the latest code.

If you have a look in https://multibit.org/releases the older versions (That could open it) are still available.

If you do use an old version of MultiBit makes sure you make copies of your wallets and I would recommend moving any bitcoin in there out straight away. Those old versions you don't want to use more than the absolute minimum.

The old wallets tended to be larger (megabyte+) whereas the newer format tend to be smaller. I forget when the format changed exactly - 2013 I think.

Thank You, I will look into this

jim618

legendary

Activity: 1708

Merit: 1066

If it is a _very_ old wallet it could be in the format that was used in the very early days of bitcoinj/ MultiBit.

These wallets were in a format called 'serialised' that isn't supported by the latest code.

If you have a look in https://multibit.org/releases the older versions (That could open it) are still available.

If you do use an old version of MultiBit makes sure you make copies of your wallets and I would recommend moving any bitcoin in there out straight away. Those old versions you don't want to use more than the absolute minimum.

The old wallets tended to be larger (megabyte+) whereas the newer format tend to be smaller. I forget when the format changed exactly - 2013 I think.

icanscript

hero member

Activity: 686

Merit: 502

Hi,

I have a backup of an old wallet, Not sure how much is in there but when I try to "open wallet" it shows the error "Could not load wallet file: the error message was null". The file seems intact and shows lots of numbers when I open it in wordpad and it looks neatly grouped.

Anyone have any ideas? can I export the private key from this?

Topic: Could not load wallet file: the error message was null (Read 2871 times)