Was Bitcoin Core still running when you launched the second time?

Okay, looking at your logs, this sticks out:


If I'm reading this right:
- Armory is actually scanning the blockchain you have downloaded, but won't go online because it can't find Core.
- You have Armory itself installed in D:\Felipe\Bitcoin\Armory ?
- And you have the blockchain downloaded to D:\Felipe\Bitcoin ?
- Having those nested like that makes me a bit nervous. Can't say it won't work as is... but you could you maybe move/reinstall Armory to D:\Felipe\Armory instead? Your PC, so up to you.

Where is Bitcoin Core installed to? Program Files on C:\ ? Armory can't find it, as far as I can tell.

Launch Core from either the shortcut or the menu.
Yes leave that unchecked.


Yeah, that probably isn't going to work for you - While this is a common problem, we're somewhat tailoring the instructions to Marla_H here.
I'll take a look at your logs and post in your existing thread, ok?

Remove that line from ArmorySettings.txt

Create a file named "armoryqt.conf" (in the same folder as ArmorySettings.txt) and add this:
Try starting up again with that in place.

No, you misunderstand me. Not all Armory addresses. For one, P2SH-P2PK was only introduced in 0.96 and HD/root key wallets predate that AFAIK.
You can choose to have addresses in any (and all) of the 3 listed formats in one Armory wallet right now. I honestly don't remember what the default was when I first booted up Armory, but I suspect it was P2PKH. Up to you to decide which format you use (this is in the settings), and you can check which addresses (used or unused) are in which format via the wallet properties.

Edit: If your addresses are specifically P2SH-P2PK, then yeah you are going to have a bad time trying to get the exported keys to refer to the right addresses in other wallets. Armory does say that it requires 0.96+ to spend from them.
P2SH-P2WPKH is a bit less smooth, but doable. P2PKH is supported by everything bitcoin related that isn't ancient.

Does that help? Don't want to leave you with false ideas about it

That'd be a problem - DB log says your blocks are in Z:\AppData\Roaming\Bitcoin\blocks. Is that right?

The P2SH-P2PK address type is unique to Armory (as far as I know). Unless you want to craft your own transactions, you're limited to dealing with whatever forks Armory has a signer for - you can't just export the private keys and call it a day.
P2PKH is universally supported, and P2SH-P2WPKH is supported by other segwit wallets (assuming they follow the standards).

Thanks for nudge towards the zip. So, it seems like something is possibly choking related to passing in the working directory.
Directly running ArmoryQt.exe from either the zip or installer version works perfectly: DB launches and everything works as expected.
Launching from a shortcut hangs - Except if the shortcut's "Start In" field matches the install directory.

Sooo this works fine:


This does not work, and I believe is the default shortcut created by the installer:

This also does not work:

Can't believe it was such a minor thing - but RC1 didn't care about the working directory. Hooray for not really being a code problem?

Not sure. Could be something new in your logfiles. Would you mind posting fresh copies of them?

Good attitude to have, tbh.
And yes, you can stick to the Electron Cash plan. P2PKH is compatible with everything.

Looks sane.
One thing to note, you will need to split BCH in Armory if your coins are in P2SH-P2PK addresses.

Hold onto the old wallet's private keys for other splits. BTG, for example.

I think I've only ever installed over the top of an existing install i.e. not uninstalling first. Shouldn't make a difference, though.
Can always backup the Armory folder if you are worried.

That is the correct one.

Since your Armory won't load, check the name of the exe/zip you downloaded. armory_0.96.3.991 is RC2. armory_0.96.3.99 is RC1

For logs head to C:\Users\YourUsernameHere\AppData\Roaming\Armory (Or %appdata%\Armory)
Should see dbLog.txt and armorylog.txt there. Add those to pastebin (or cryptbin if preferred) and paste the links here.

Use RC1 for now, please. RC2 has an issue on Windows that you'd need to work around.

Won't affect receiving the coins - don't delete your wallet or anything like that.

Betting that you are using RC2 on Windows. Either use the workaround in that thread, or use RC1

Most stable version? If Armory isn't finding the blocks, that doesn't ring true to me.
Core 0.15 should be fine.

I would however strongly suggest you upgrade to Armory 0.96.4 RC1 on Windows, or RC2 if you aren't.
Armory doesn't use the chainstate files from Core at all, so a -reindex-chainstate won't make a difference. A standard -reindex might if there was some sort of block corruption, but nothing suggests that is required yet.
That said, if you've been hopping around different Armory versions, your Armory database might've been corrupted.

Either way, worth posting your log files:

So, you'll need to follow the instructions in the post I made just above yours. Either via a config file or editing a shortcut for Bitcoin Core.
For a config file, create a bitcoin.conf in D:\BitcoinCore\ and fill it with the first set.

Or for a shortcut... if you don't have one, create a shortcut to C:\Program Files\Bitcoin\bitcoin-qt.exe and add on the server and listen parts.

Then close Armory and Bitcoin Core. Start Bitcoin Core from that shortcut. Then start Armory.

Yeah, that all looks about right.
Just make sure the transaction has a few confirmations on the blockchain before exposing the private keys.

I think the intention is that you try restoring the wallet in that state and then go online again afterwards.