You may need to also blank out the paths in the settings > general tab. I think they override your armoryqt.conf settings.

If Armory and Bitcoin Core 's downloaded blockchain aren't up to date with whenever you last made a transaction the balance shown won't be accurate. You were only at 25% a few hours ago so let it run unless it is very clear you had some and transferred it away in the transaction log.
Something to check before writing it off.

Great!
Select your wallet > Wallet Properties > Backup This Wallet
There are digital backup options available there alongside the paper option. You need a backup of some form if you value these coins at all.

Did you have Armory open while trying to install the newer version? That is the only way I can think of that the installer would likely fail.

You're welcome to wait the 30 hours but I fear that version of Armory is not actually working correctly.
File > Export Log File
Will create a log file that you can upload somewhere (pastebin is a common choice) and share a link to here. That'd allow us to diagnose the issue more easily.

Have you checked that your address has received the coins you expected on an online block explorer, like blockchair?
If so then you can be confident your coins have transferred and are safe but Armory hasn't got to processing that point of the blockchain yet.

The installer will just install over the top of your existing Armory installation. Even if you did uninstall first it should not delete your wallet files.
All that being said the best way to keep your wallet safe is to create and test a paper backup. Armory prompts you to make one when making the wallet. Did you do this? If not, make one immediately and test it.

Unsure what you mean by this. You don't think what will let you do what?

Are you running 0.96 as you said in your first post or 0.96.5?

If the former, you need to upgrade. Old versions have some database bugs and don't play nice with newer Core versions.

https://btcarmory.com/releases/
or
https://github.com/goatpig/BitcoinArmory/releases/

Might need to reset the Armory database after upgrading but try without first.

Not sure why it had to build from source this time.
Try pinging droark here: https://bitcointalk.org/index.php?topic=5200633.0

Thanks for running the other lines again and sorry, I should have been a bit more specific for the openssl step.

Run this
instead of
Just the first - the second one will install openssl 1.1 again. You don't want that
I don't think you need to run the other steps again, just the first one above.

For all the shasum & GPG steps you need to run the commands in the same directory/path as the downloaded files, so you'd need armory_0.96.5_osx.tar.gz and sha256sum.txt.asc from here: https://github.com/goatpig/BitcoinArmory/releases/
I don't recommend skipping the verification steps but they aren't vital to getting Armory to run. They are important for verifying that you haven't got corrupt or otherwise tampered with software.

Should just be a case of following the three steps under for the rest: https://github.com/goatpig/BitcoinArmory/blob/master/README_macOS.md#running-armory
Again, make sure you have openssl 1.0. Good luck!

Looks like you skipped a few commands if that was the entire terminal?
Not using Mac myself but I'm fairly sure you were meant to run these one by one too.


After that it looks like you've got openssl 1.1 rather than 1.0. droark suggests this:

As for the "Downloading and Verifying Armory" steps you've got a typo.
should be
Another typo later on with the asc file - in the next command it doesn't look like you downloaded that file from step 4 as well.
This doesn't look like an offline install so just use copy and paste for each line instead of typing them out

Have you both followed all the steps here?
https://github.com/goatpig/BitcoinArmory/blob/master/README_macOS.md

You do not need txindex, Armory maintains its own database.
Make sure you're running Armory 0.96.5.

This'll be the one: https://github.com/goatpig/BitcoinArmory/blob/master/PublicKeys/goatpig-signing-key.asc

Author's thread from last year for reference: https://bitcointalk.org/index.php?topic=2647522
Sounds like it is worse than before if Armory no longer opens?

Navigate to the github page that has each GPG key i.e. they start with:
Then click the "Raw" button on the right hand side. Once the page has loaded, Ctrl + S or File > Save as and save the file. Then import as above, but the filenames should be just "goatpig-signing-key.asc" and "laanwj-releases.asc" unless your browser does something strange or you rename them.

Neither is the offline deb. The latest offline deb was for 0.96.2 and as per my previous post it doesn't include all dependencies for modern versions of Ubuntu.

As far as I can tell it should work. I think you might have problems broadcasting transactions, but unsure.

Nope. The offline and online device model still exists. Newer versions of Ubuntu/Debian retired and no longer include the older version of the QT framework that Armory uses. Including these packages (and their dependencies!) in the offline archive would bloat the filesize and probably be a pain to maintain.
N.B. The devs are working hard to modernize the codebase for v0.97.

The somewhat easy method around this is to grab the .deb files from the apt cache on the online machine and copy to/install on the offline machine. This isn't without flaws.

I believe the bootstrap file is largely irrelevant these days. You would probably be better to copy over whatever blockchain data you have and continue syncing.
Armory wallets aren't tied to a specific platform - wallet files should be interoperable but make sure you have your paper backup anyway.
It really depends on how much happier with Windows you are. 10 has some quirks related to Armory <-> node operation that aren't experienced on Windows 7 or on Linux. With 7 support ending in January, the options dwindle.

I'd update the online machine to 0.96.5 and see if you still have the same problem. Note that there are signing fixes in 0.96.5 that aren't in 0.96.4 and you might need those on the offline machine.

This is the problem. Your CPU doesn't support an instruction that Armory is frequently compiled for. Please try the latest noasm build: https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.5/armory_0.96.5_amd64_gcc4.9_noasm.deb

Note that a lot of Armory is Python rather than C/C++, but if using gcc4.9 does not work properly you can try a 0.96.4 noasm build or you are going to need to compile your own version.

Unfortunately that is the old Armory website (https://btcarmory.com/ is the maintained site). The current Linux build notes will work a lot better.

Yup.
This is important. You can attempt to repair the wallet by using the seed.
That won't work unfortunately. Armory's recovery seed is not compatible with others.


@eddy390
What version of Armory are you using on the offline wallet? I vaguely remember a bug in older versions that wouldn't show certain windows.
0.96.5 is the current version. Available via the top thread in this forum or https://btcarmory.com/

Based on that log Armory is also spawning bitcoind - Assuming you still want to manually run bitcoind on another user you can stop Armory starting bitcoind in the GUI.
File > Settings > Uncheck "Let Armory run Bitcoin Core/bitcoind in the background"

I don't think Armory supports RPC auth via rpcuser and rpcpassword, and having those flags in the bitcoin.conf would probably cause issues connecting? Instead Armory needs to be able to read the .cookie file in the bitcoin data directory (Bitcoind/core creates this).

Yes.
How are you shutting down Bitcoin Core normally?
Outside chance, but your hard drive that has the blockchain could be failing? Worth checking.