My Armory wallet has gone to zero balance and transactions are missing?

[LarrysCoins]

I just tried to send some of my bit coin in my armory wallet. When I pressed the send button to setup the transaction the program seemed to freeze and displayed a window I couldn't shut down. I had to reboot the computer to shut Armory down. After rebooting my wallet showed zero balance and all my transactions are missing? I restored my wallet from a paper back up, which seems to work but still have zero balance and no transactions. Have I been hacked, has my bitcoin been stolen?

[hosemary]

As you don't see any transaction, most probably your wallet isn't synced to the network properly.
Is your Armory wallet connected to bitcoin core or offline? Check the bottom right corner of the window.

Have I been hacked, has my bitcoin been stolen?

Don't worry. I guess it's only a syncing issue and to make sure of that, you can check your address(es) balance on block explorers like mempool.space.

[LarrysCoins]

Thanks for looking at this. My Armory screen says Node offline (0 blocks).
How do I get my Armory to sync again?
My Armory version I see on main screen is 0.96.3.992
I would like to check my addresses but I don't have any without my transaction listing.

[goatpig]

Delete the databases folder in your Armory appdata then update to 0.96.5:

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

[LarrysCoins]

Thanks for the guidance.
I upgraded to 0.96.5.
Deleted the data base folder as you directed.
My Armory screen has been stuck on node status part for last two weeks. Have generated 2595 131MB
blk02595.dat files. Have watched my HD fill with 340Gbytes so far.

Any idea if this is correct and how much further I will have to go? Still have 430G bytes of free space on my hard drive?

[nc50lc]

-snip- Have generated 2595 131MB
blk02595.dat files. Have watched my HD fill with 340Gbytes so far.

Any idea if this is correct and how much further I will have to go? Still have 430G bytes of free space on my hard drive?

That should be enough to fully sync Bitcoin Core, headsup: it'll reach about <700GB.
The blk files look about right as long as those aren't all "blk02595.dat" files but with sequential numbers like "blk02596.dat" and "blk02597.dat".

But can you tell the version of Bitcoin Core that you're using?
Because Armory v0.96.5 will not be able to use it if it's a new Bitcoin blocksdir and created by >v28.0.

[goatpig]

My chain is the blk050xx.dat at the moment

[LarrysCoins]

Still downloading blk data. Up to #4100.
Question: How do I look at the version of bitcoin core? You asked me to look at this but I don't know how too?

Other observations:
I rarely see Connected (In green) on the bottom right corner of the Armory screen, but have seen it once in awhile when restarting. It always says (0 blocks) weather connected or node offline. Is this correct?

[LarrysCoins]

found bitcoind exe and details show file version 0.15.1.0
file date is 11/6/2017 

[LarrysCoins]

Please help as my wallet seems lost?

[hosemary]

Please help as my wallet seems lost?

Is your wallet synced now?
If you still have issue with your wallet getting synced to the blockchain (as already stated) that's why you don't see any transaction in your wallet.


And don't worry. If you can't sync your wallet for any reason, you can export your private keys from Armory and import them into other wallets like electrum and access your fund.
Electrum is a SPV wallet and you won't have to download the blockchain for using that.

[nc50lc]

found bitcoind exe and details show file version 0.15.1.0

That's too old, since you've upgraded Armory to 0.96.5, you may update Bitcoin Core to v27.0 though it should still work.
You can download the older releases from here: https://bitcoincore.org/bin/

Please help as my wallet seems lost?

When goatpig instructed you to delete the databases folder,
Did you delete the literal "databases" folder inside armory folder or the "armory" folder itself?
Because the latter will get your wallet deleted, in this case, you can just restore it back since you have your backup.

[LarrysCoins]

I deleted the databases folder under the armory folder. Not the Armory folder.

[LarrysCoins]

should I upgrade to bitcoin core V27?
You keep asking if my wallet is synced, how do I tell? My wallet transactions are still missing and I always see zero blocks in the lower right hand corner of the armory screen. Usually the screen says node offline(0 blocks), but I have seen connected(0 blocks) a few times.

[nc50lc]

should I upgrade to bitcoin core V27?

For compatibility, it's recommended.
Based on the majority of the threads here, Armory v0.65.5 and Bitcoin Core v27.0 work great with each other.

You keep asking if my wallet is synced, how do I tell? My wallet transactions are still missing and I always see zero blocks in the lower right hand corner of the armory screen. Usually the screen says node offline(0 blocks), but I have seen connected(0 blocks) a few times.

Hmm, still 0 blocks processed although it successfully found bitcoind.

At this point, it's best to check the logs to find the issue, but do that after updating Core.
You can find those in your armory data directory, named: "armorylog.txt" and "dbLog.txt".
Find the specific session after the update since your old logs are included there (check the timestamp).

[LarrysCoins]

Still trying to recover my wallet. Have now down loaded up to blk05225. Armory says Initializing Bitcoin engine, building Databases, then Scanning Transaction History. It gets to 98% and stays there for days slowly downloading a couple new blocks per day while scanning transaction history. I am going to try to upgrade to bitcoin core v27. I have the current bitcoin debug log but don't see a way to up load a file. Please let me know how to attach the debug logs.

[nc50lc]

Still trying to recover my wallet. Have now down loaded up to blk05225. Armory says Initializing Bitcoin engine, building Databases, then Scanning Transaction History. It gets to 98% and stays there for days slowly downloading a couple new blocks per day while scanning transaction history.

It's been months.
It seems to sync really slow, if not your hardware, perhaps it's your very old Bitcoin Core version.

Once you updated, if you have enough free memory (RAM), you may consider increasing your Bitcoin Core's dbcache to at least 4~8GB or higher if your system can handle it.
Because you can do so by adding dbcache=4000 in your bitcoin.conf file inside bitcoin's datadir. (4000 value is in MiB)

And also, it's important to make sure that "prune" setting isn't enabled or those slow progress will just be wasted since Armory wont be able to utilize a pruned block storage.

I have the current bitcoin debug log but don't see a way to up load a file. Please let me know how to attach the debug logs.

You can open it as text and copy the last session's log.
If the contents are long, you may use paste.bin and post the link in your reply or paste the logs between [code][/code] tags.

But given that it's now syncing (slowly), that should work once finished as long as the prune setting that I've mentioned isn't ticked.

[LarrysCoins]

Hello,
Still having problems getting my wallet to sync.
Up graded to bitcoin core V27.0. It ran when I completed the install. Then I reopened armory and have the same results after a couple of days, it gets to 97% of scanning transaction history and never seems to complete. I don't see a way of checking the bitcoin conf settings. All I find is the bitcoin.conf file at C:\Program Files\Bitcoin\bitcoin.conf. All the settings are commented out in that file as shown below. I find the dbcache and the prune command as shown below:

# Maximum database cache size <n> MiB (4 to 16384, default: 450). In
# addition, unused mempool memory is shared for this cache (see
# -maxmempool).
#dbcache=<n>

# Reduce storage requirements by enabling pruning (deleting) of old
# blocks. This allows the pruneblockchain RPC to be called to
# delete specific blocks and enables automatic pruning of old
# blocks if a target size in MiB is provided. This mode is
# incompatible with -txindex. Warning: Reverting this setting
# requires re-downloading the entire blockchain. (default: 0 =
# disable pruning blocks, 1 = allow manual pruning via RPC, >=550 =
# automatically prune block files to stay under the specified
# target size in MiB)
#dbcache=<n>

Do you want me to uncomment these two lines and save the file. Like this below?
dbcache=4000
dbcache=0

I see no other bitcoin.conf files to check these setting on my system.

Here is the end of the debug.log located at C:\Users\Larry\AppData\Roaming\Bitcoin
Below this is a portion of the armorylog.txt located at C:\Users\Larry\AppData\Roaming\Armory

THANKS FOR HELPING ME OUT, I DONT KNOW WHAT TO DO AT THIS POINT TO RECOVER MY WALLET
 
025-11-09T00:59:27Z Bitcoin Core version v27.0.0 (release build)
2025-11-09T00:59:27Z Script verification uses 5 additional threads
2025-11-09T00:59:27Z Using the 'standard' SHA256 implementation
2025-11-09T00:59:27Z Default data directory C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-09T00:59:27Z Using data directory C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-09T00:59:27Z Config file: C:\Users\Larry\AppData\Roaming\Bitcoin\bitcoin.conf (not found, skipping)
2025-11-09T00:59:27Z Command-line arg: datadir="C:\\Users\\Larry\\AppData\\Roaming\\Bitcoin"
2025-11-09T00:59:27Z Using at most 125 automatic connections (2048 file descriptors available)
2025-11-09T00:59:27Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-11-09T00:59:27Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-11-09T00:59:27Z scheduler thread start
2025-11-09T00:59:27Z Binding RPC on address ::1 port 8332
2025-11-09T00:59:27Z Binding RPC on address 127.0.0.1 port 8332
2025-11-09T00:59:27Z Using random cookie authentication.
2025-11-09T00:59:27Z Generated RPC authentication cookie C:\Users\Larry\AppData\Roaming\Bitcoin\.cookie
2025-11-09T00:59:27Z Starting HTTP server with 4 worker threads
2025-11-09T00:59:27Z Using wallet directory C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-09T00:59:27Z init message: Verifying wallet(s)…
2025-11-09T00:59:27Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2025-11-09T00:59:27Z Using wallet C:\Users\Larry\AppData\Roaming\Bitcoin\wallet.dat
2025-11-09T00:59:27Z BerkeleyEnvironment::Open: LogDir=C:\Users\Larry\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Larry\AppData\Roaming\Bitcoin\db.log
2025-11-09T00:59:27Z Using /16 prefix for IP bucketing
2025-11-09T00:59:27Z init message: Loading P2P addresses…
2025-11-09T00:59:27Z Loaded 65810 addresses from peers.dat  520ms
2025-11-09T00:59:27Z init message: Loading banlist…
2025-11-09T00:59:27Z banlist.dat ignored because it can only be read by Bitcoin Core version 22.x. Remove "C:\Users\Larry\AppData\Roaming\Bitcoin\banlist.dat" to silence this warning.
2025-11-09T00:59:28Z SetNetworkActive: true
2025-11-09T00:59:28Z Script verification uses 5 additional threads
2025-11-09T00:59:28Z Cache configuration:
2025-11-09T00:59:28Z * Using 2.0 MiB for block index database
2025-11-09T00:59:28Z * Using 8.0 MiB for chain state database
2025-11-09T00:59:28Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2025-11-09T00:59:28Z init message: Loading block index…
2025-11-09T00:59:28Z Assuming ancestors of block 000000000000000000026811d149d4d261995ec5b3f64f439a0a10e1a464af9a have valid signatures.
2025-11-09T00:59:28Z Setting nMinimumChainWork=000000000000000000000000000000000000000063c4ebd298db40af57541800
2025-11-09T00:59:28Z Opening LevelDB in C:\Users\Larry\AppData\Roaming\Bitcoin\blocks\index
2025-11-09T00:59:28Z Opened LevelDB successfully
2025-11-09T00:59:28Z Using obfuscation key for C:\Users\Larry\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2025-11-09T00:59:40Z LoadBlockIndexDB: last block file = 5231
2025-11-09T00:59:40Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=47, size=70283464, heights=922748...922794, time=2025-11-08...2025-11-09)
2025-11-09T00:59:40Z Checking all blk files are present...
2025-11-09T01:02:46Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-11-09T01:02:46Z Opening LevelDB in C:\Users\Larry\AppData\Roaming\Bitcoin\chainstate
2025-11-09T01:02:48Z Opened LevelDB successfully
2025-11-09T01:02:48Z Using obfuscation key for C:\Users\Larry\AppData\Roaming\Bitcoin\chainstate: 4dc7cc3a1a56122f
2025-11-09T01:02:48Z Loaded best chain: hashBestChain=00000000000000000001a5817e106fc01b852c19da53700200fe2d945055174f height=922690 date=2025-11-08T04:46:42Z progress=0.999622
2025-11-09T01:02:48Z Opening LevelDB in C:\Users\Larry\AppData\Roaming\Bitcoin\chainstate
2025-11-09T01:02:48Z Opened LevelDB successfully
2025-11-09T01:02:48Z Using obfuscation key for C:\Users\Larry\AppData\Roaming\Bitcoin\chainstate: 4dc7cc3a1a56122f
2025-11-09T01:02:48Z [Chainstate [ibd] @ height 922690 (00000000000000000001a5817e106fc01b852c19da53700200fe2d945055174f)] resized coinsdb cache to 8.0 MiB
2025-11-09T01:02:48Z [Chainstate [ibd] @ height 922690 (00000000000000000001a5817e106fc01b852c19da53700200fe2d945055174f)] resized coinstip cache to 440.0 MiB
2025-11-09T01:02:48Z init message: Verifying blocks…
2025-11-09T01:02:48Z Verifying last 6 blocks at level 3
2025-11-09T01:02:48Z Verification progress: 0%
2025-11-09T01:03:31Z Verification progress: 16%
2025-11-09T01:05:20Z Verification progress: 33%
2025-11-09T01:06:01Z Verification progress: 50%
2025-11-09T01:07:32Z Verification progress: 66%
2025-11-09T01:09:08Z Verification progress: 83%
2025-11-09T01:10:14Z Verification progress: 99%
2025-11-09T01:10:14Z Verification: No coin database inconsistencies in last 6 blocks (16346 transactions)
2025-11-09T01:10:14Z  block index          646024ms
2025-11-09T01:10:14Z init message: Loading wallet…
2025-11-09T01:10:14Z BerkeleyEnvironment::Open: LogDir=C:\Users\Larry\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Larry\AppData\Roaming\Bitcoin\db.log
2025-11-09T01:10:14Z [default wallet] Wallet file version = 10500, last client version = 270000
2025-11-09T01:10:14Z [default wallet] Legacy Wallet Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total.
2025-11-09T01:10:14Z [default wallet] Descriptors: 0, Descriptor Keys: 0 plaintext, 0 encrypted, 0 total.
2025-11-09T01:10:14Z [default wallet] Wallet completed loading in             459ms
2025-11-09T01:10:14Z [default wallet] setKeyPool.size() = 2000
2025-11-09T01:10:14Z [default wallet] mapWallet.size() = 0
2025-11-09T01:10:14Z [default wallet] m_address_book.size() = 1
2025-11-09T01:10:14Z Setting NODE_NETWORK on non-prune mode
2025-11-09T01:10:14Z block tree size = 922797
2025-11-09T01:10:14Z nBestHeight = 922690
2025-11-09T01:10:14Z initload thread start
2025-11-09T01:10:14Z torcontrol thread start
2025-11-09T01:10:14Z AddLocal([2601:283:5103:56e0:8d92:88eb:b5c0:7d64]:8333,1)
2025-11-09T01:10:14Z Discover: Larry-HP - 2601:283:5103:56e0:8d92:88eb:b5c0:7d64
2025-11-09T01:10:14Z AddLocal([2601:283:5103:56e0::6140]:8333,1)
2025-11-09T01:10:14Z Discover: Larry-HP - 2601:283:5103:56e0::6140
2025-11-09T01:10:14Z AddLocal([2601:283:5103:56e0:c59b:bd61:cc8f:9bb0]:8333,1)
2025-11-09T01:10:14Z Discover: Larry-HP - 2601:283:5103:56e0:c59b:bd61:cc8f:9bb0
2025-11-09T01:10:14Z Bound to 127.0.0.1:8334
2025-11-09T01:10:14Z Bound to [::]:8333
2025-11-09T01:10:14Z Bound to 0.0.0.0:8333
2025-11-09T01:10:14Z 0 block-relay-only anchors will be tried for connections.
2025-11-09T01:10:14Z init message: Starting network threads…
2025-11-09T01:10:14Z net thread start
2025-11-09T01:10:14Z dnsseed thread start
2025-11-09T01:10:14Z addcon thread start
2025-11-09T01:10:14Z opencon thread start
2025-11-09T01:10:14Z Waiting 300 seconds before querying DNS seeds.
2025-11-09T01:10:14Z msghand thread start
2025-11-09T01:12:41Z UpdateTip: new best=0000000000000000000101393c4f6be6bb6ba4cbe9a13011d922f65c88c7068a height=922691 version=0x2e000000 log2_work=95.924965 tx=1267744524 date='2025-11-08T05:06:08Z' progress=0.999625 cache=1.7MiB(13753txo)
2025-11-09T01:13:46Z UpdateTip: new best=00000000000000000000f225b82c6f9002619ae29db18db238246b9a46c2a34c height=922692 version=0x20038000 log2_work=95.924978 tx=1267748847 date='2025-11-08T05:12:48Z' progress=0.999627 cache=2.7MiB(21108txo)













Here is the last armorylog.txt data
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1281 -
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1282 -
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1283 -
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.19041--Multiprocessor Free
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\Larry\AppData\Roaming
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\Larry\AppData\Roaming\Armory\
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 8.00 GB
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : AMD64 Family 16 Model 10 Stepping 0, AuthenticAMD
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 6 cores
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 51 GB
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 51 GB
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1305 -
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\Larry\AppData\Roaming\Armory\ArmorySettings.txt
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\Larry\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Larry\AppData\Roaming\Armory\ArmorySettings.txt
2025-11-08 17:58:36 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2025-11-08 17:58:36 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2025-11-08 17:58:36 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background.  
2025-11-08 17:58:36 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2025-11-08 17:58:36 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2025-11-08 17:58:36 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2025-11-08 17:58:39 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Larry\AppData\Roaming\Armory\ArmorySettings.txt
2025-11-08 17:58:39 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2025-11-08 17:58:39 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2025-11-08 17:58:40 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 1
2025-11-08 17:58:40 (INFO) -- ArmoryQt.py:2190 -    Wallet (2ZoMZTCiT):   "Restored - 2ZoMZTCiT            "   (Encrypted)
2025-11-08 17:58:40 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2025-11-08 17:58:40 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user.  Done!
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2025-11-08 17:58:42 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2025-11-08 17:58:42 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2025-11-08 17:58:42 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2025-11-08 17:58:42 (INFO) -- SDM.pyc:175 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2025-11-08 17:58:42 (INFO) -- SDM.pyc:340 - Called startBitcoind
2025-11-08 17:59:26 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-08 17:59:26 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Larry\\AppData\\Roaming\\Bitcoin']
2025-11-08 17:59:26 (INFO) -- SDM.pyc:451 - PID of bitcoind: 1480
2025-11-08 17:59:26 (INFO) -- SDM.pyc:452 - PID of armory:   14844
2025-11-08 17:59:26 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\guardian.exe', '14844', '1480']
2025-11-08 17:59:32 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2025-11-08 17:59:32 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\Larry\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\Larry\AppData\Roaming\Armory\" --dbdir="C:\Users\Larry\AppData\Roaming\Armory\databases"
2025-11-08 17:59:32 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\Larry\\AppData\\Roaming\\Bitcoin\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\Larry\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Larry\\AppData\\Roaming\\Armory\\databases"']
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:1824 - Connecting on port 62674
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2025-11-08 17:59:39 (ERROR) -- ArmoryQt.py:1198 - 51 attempts to load blockchain failed.  Remove mempool.bin.
2025-11-08 17:59:39 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2025-11-08 17:59:39 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2025-11-08 18:34:01 (INFO) -- ArmoryQt.py:4614 - Dashboard switched to auto-InitSync
2025-11-08 18:34:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode

[nc50lc]

All I find is the bitcoin.conf file at C:\Program Files\Bitcoin\bitcoin.conf. All the settings are commented out in that file as shown below.

That's just a sample bitcoin.conf file that should be pasted to the datadir if you want to apply any settings that you've commented-out.
So, you're using the defaults plus anything you set in the welcome screen (the first time you start Bitcoin Core).

Do you want me to uncomment these two lines and save the file. Like this below?
dbcache=4000
dbcache=0

Now that it shows that your Bitcoin Core is already synced to the tip of the blockchain, dbcache is not necessary to speed-up sync now.
That's if the logs have more lines showing "UpdateTip: new best" up to the latest block hash/height.

2025-11-08 17:58:42 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2025-11-08 17:58:42 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
-snip-
2025-11-08 17:59:32 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\Larry\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\Larry\AppData\Roaming\Armory\" --dbdir="C:\Users\Larry\AppData\Roaming\Armory\databases"
-snip-
2025-11-08 17:59:39 (ERROR) -- ArmoryQt.py:1198 - 51 attempts to load blockchain failed.  Remove mempool.bin.

It found bitcoind but failed to load the blockchain.
The issue seem to be Armory failing to find your datadir but it's correctly pointing to the same datadir used by your Bitcoin Core above. (\blocks is added by Armory)

Since you're on Windows and using the default paths, try to follow these steps: /index.php?topic=5562211.msg65948369#msg65948369
Including the notes about a possible "zombie armorydb process" when restarting Armory.

THANKS FOR HELPING ME OUT, I DONT KNOW WHAT TO DO AT THIS POINT TO RECOVER MY WALLET

Logs show that your wallet "Restored - 2ZoMZTCiT" is still loaded.
So it's just a matter of being able to sync Armory or just export the private keys to import to another wallet (if the former doesn't work).
For the latter, here's my reply with info and pointing to the relevant tutorial: /index.php?topic=5562211.msg65919317#msg65919317

[LarrysCoins]

Hi thanks for the tips but I dont think the paths are the problem.
In the logs I see this:
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\Larry\AppData\Roaming
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\Larry\AppData\Roaming\Bitcoin
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\Larry\AppData\Roaming\Armory\
2025-11-08 17:58:36 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
This looks correct to me. Let me know if you agree.

I did add the armoryqt.conf file at C:\Users\Larry\AppData\Roaming\Armory
The command I added is:
satoshi-datadir=C:\Users\Larry\AppData\Roaming\Bitcoin

Looking at the Bitcoin Core Gui under window information I see:
Datadir C:\Users\Larry\AppData\Roaming\Bitcoin
Blocksdir C:\Users\Larry\AppData\Roaming\Bitcoin\blocks

Looking at the dblog.txt I see this near the end which look suspicious because of the errors:
-INFO  - 08:32:59.453: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #909497 to #909834
-INFO  - 08:33:22.516: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:52) no history to scan
-INFO  - 08:33:30.641: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #909835 to #910171
-INFO  - 08:33:51.922: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #910172 to #910506
-INFO  - 08:34:24.266: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:52) no history to scan
-INFO  - 08:34:24.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #910507 to #910834
-INFO  - 08:34:52.547: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #910835 to #911166
-INFO  - 08:35:26.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #911167 to #911507
-INFO  - 08:35:57.266: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #911508 to #911840
-INFO  - 08:36:20.734: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #911841 to #912179
-INFO  - 08:36:41.563: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:52) no history to scan
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5115
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5116
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5117
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5118
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5119
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #5120
-ERROR - 08:36:49.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #5121

See allot of the no history to scan above these lines. Missing the map file seems to be a problem. What file is this and why would it be missing?
Again thanks for your support, really would like my bitcoin back.