2

Just downloaded the CLI binaries from getmonero. When trying to load a wallet in the CLI I get one of two errors:

Error: failed to load wallet: std::bad_alloc

Error: failed to load wallet: basic_string::_M_replace_aux

The errors don't appear together. Each time I try I get one of them, seems pretty random to me.

I can load the wallet using the old CLI binary.
Anything to do about it?

Edit:
The solution suggested by dEBRUYNE works in the sense that my wallet can now be opened. However, this way I lose information I cannot restore, about past outgoing transactions (specifically, addresses I sent to).
Furthermore, I just noticed that v0.11.1.0 doesn't support subaddresses yet, and I should note that my previous cli did support it, and my wallet did have subaddresses, so I guess this caused the incompatibility.

  • ZoneAlarm antivirus shows the Monero 13.0.4 zip file for Windows64 containing three viruses! not-a-virus.Net Tool.Win32.Tor.Jok.awo Sheesh. Will I EVER be able to install and use Monero without major problems? – Guest Nov 3 '18 at 21:34
  • @Guest - This is a false positive produced by your AntiVirus (as the monero software contains a solo miner). I'd advise to create an exception (i.e. whitelist) for the Monero software in your AV. – dEBRUYNE Nov 4 '18 at 10:16
  • I did the steps for the GUI and got this response. Daemon failed to start Please check your wallet and daemon logs for errors. You can also try to start monerod.exe manually. – jerry Aug 29 '19 at 19:59
  • @jerry - Did you recently update your GUI version? – dEBRUYNE Aug 30 '19 at 6:43
  • I did recently update my GUI. As I was in the process of syncing the GUI my computer restarted and that's when I encountered this problem. – jerry Aug 30 '19 at 12:28
3

First, make sure you're running either CLI v0.13.0.4 or GUI v0.13.0.4.

Both errors imply an incompatible wallet cache, which results in monero-wallet-cli not being able to open it. Fortunately, the fix is quite trivial.

Perform these steps and you should be able to open your wallet again.

  1. Browse to the directory your wallet files are located. By default, this is the same directory as monero-wallet-cli.

  2. Rename <wallet-name> (the file without extension) to <wallet-name>-old.

Note that, because you renamed the wallet cache, <wallet-name>.keys now doesn't have a accompanying wallet cache. Therefore, monero-wallet-cli will create a new wallet cache, which will simultaneously trigger a wallet refresh from scratch. A wallet refresh from scratch, however, shouldn't take that long to complete.


GUI:

If you're using the GUI, you can utilize the following steps:

  1. Exit the GUI.

  2. Browse to the directory your wallet files are located (Documents\Monero\<wallet-name> on Windows | home/<username>/Monero/<wallet-name> on Linux | Users/<username>/Monero/<wallet-name> Mac OS X).

  3. Rename <wallet-name> (the file without extension) to <wallet-name>-old

  4. Restart the GUI. This will trigger a wallet refresh from scratch, which shouldn't take longer than 30 minutes.

| improve this answer | |
  • I accepted the answer because it lets the wallet be opened. Although, a method that would allow to keep all information in the <wallet> file is preferred. – Jona Nov 30 '17 at 6:48
  • 1
    Currently there's no such method unfortunately. However, the information is retained in <wallet-name>-old. – dEBRUYNE Nov 30 '17 at 10:36
  • Once subaddresses are supported in the official release, would my wallet be readable? – Jona Nov 30 '17 at 12:31
  • Did you create your wallet using compiled binaries (from master)? – dEBRUYNE Nov 30 '17 at 16:03
  • 1
    Then probably yes. – dEBRUYNE Dec 1 '17 at 0:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.