Armory wallet hangs on "Scanning Transaction History" Since Bitcoin Core 25.0

[OtisG]

Hello,
After installing Bitcoin Core 25.0 a couple of weeks ago, my Armory wallet will not complete opening.
It hangs at about 43% complete during Scanning Transaction History.
It's done this at various times in the past, and the fix was to simply rename the "databases" directory to let Armory rebuild it.
I've done that, but it won't get past 43%.
I've let it run overnight more than 12hrs, and it won't finish.

Any thoughts?
OtisG

[BitMaxz]

How about the rebuild and rescan from the help menu have you tried that?

If it doesn't work then would you mind sharing your armory logs?
You can export the logs by going to file --> export log file or go to the armory folder and look for armorylog.txt and share the content here make sure to put the logs inside the insert code tag.

[OtisG]

Thank you for your quick reply.

I have not tried that; I will do so this morning and report back.

[OtisG]

I did try the rebuild an rescan, but it still gives the same results. The computer in questions is Windows 11, and it also recently downloaded and installed some upgrades.

As a test I copied the wallet to an older Windows 10 PC I have with Bitcoin Core 25.0, and Armory works as it should from there. It looks like the issue is perhaps Windows 11 related. I'm pressed for time today, but I will plan on sending logs to you tomorrow from the Windows 11 PC.

Thank you for your help.

[BitMaxz]

I did try the rebuild an rescan, but it still gives the same results. The computer in questions is Windows 11, and it also recently downloaded and installed some upgrades.

As a test I copied the wallet to an older Windows 10 PC I have with Bitcoin Core 25.0, and Armory works as it should from there. It looks like the issue is perhaps Windows 11 related. I'm pressed for time today, but I will plan on sending logs to you tomorrow from the Windows 11 PC.

There might be something that causes this issue if it is just your OS it might be a compatibility issue.

Can you try to change the compatibility mode to Windows 10 or 7?
To do that right-click the Armory shortcut --> properties --> compatibility then enable "Run this program in compatibility mode" and choose Windows 10 or below.
Also, do this in Bitcoin core then reboot the PC.

If it didn't work try disabling the firewall and exclude Armory and Bitcoin core from your Anti-Virus.

[goatpig]

1. Did your chain data get pruned after you installed 25.0?
2. How many blocks is Core showing?
3. How much disk space do you have left?

[OtisG]

I did try the rebuild an rescan, but it still gives the same results. The computer in questions is Windows 11, and it also recently downloaded and installed some upgrades.

As a test I copied the wallet to an older Windows 10 PC I have with Bitcoin Core 25.0, and Armory works as it should from there. It looks like the issue is perhaps Windows 11 related. I'm pressed for time today, but I will plan on sending logs to you tomorrow from the Windows 11 PC.

There might be something that causes this issue if it is just your OS it might be a compatibility issue.

Can you try to change the compatibility mode to Windows 10 or 7?
To do that right-click the Armory shortcut --> properties --> compatibility then enable "Run this program in compatibility mode" and choose Windows 10 or below.
Also, do this in Bitcoin core then reboot the PC.

If it didn't work try disabling the firewall and exclude Armory and Bitcoin core from your Anti-Virus.

Apologies for my slow reply: work's been crazy.

I tried all of the above, and none of it worked. Changing to compatibility mode made things even more wonky.

[OtisG]

1. Did your chain data get pruned after you installed 25.0?
2. How many blocks is Core showing?
3. How much disk space do you have left?

1. No, it didn't get pruned.
2. All the blocks are downloading in Bitcoin Core.
3. 1TB total with 280GB free.

[OtisG]

How about the rebuild and rescan from the help menu have you tried that?

If it doesn't work then would you mind sharing your armory logs?
You can export the logs by going to file --> export log file or go to the armory folder and look for armorylog.txt and share the content here make sure to put the logs inside the insert code tag.

Apologies for getting back to this thread so slowly.
Rebuild/rescan did not change anything.
Here is the content from an updated ArmoryLog.txt log from this morning; the BTC blockchain is up to date.

Code:

2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1281 - 
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1282 - 
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1283 - 
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.22621--Multiprocessor Free
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\REDACTED\AppData\Roaming
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\REDACTED\AppData\Roaming\Bitcoin
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\REDACTED\AppData\Roaming\Armory\
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    : 
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 15.71 GB
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : Intel64 Family 6 Model 85 Stepping 4, GenuineIntel
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 16 cores
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 278 GB
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 0 GB
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1305 - 
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\REDACTED\AppData\Roaming\Armory\ArmorySettings.txt
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\REDACTED\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\REDACTED\AppData\Roaming\Armory\ArmorySettings.txt
2023-10-20 08:12:54 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2023-10-20 08:12:54 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2023-10-20 08:12:54 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2023-10-20 08:12:54 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background.  
2023-10-20 08:12:54 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2023-10-20 08:12:54 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for 
2023-10-20 08:12:54 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2023-10-20 08:12:56 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\REDACTED\AppData\Roaming\Armory\ArmorySettings.txt
2023-10-20 08:12:56 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2023-10-20 08:12:56 (INFO) -- ArmoryQt.py:2120 - Loading wallets...

2023-10-20 08:12:57 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: X ********** REDACTED **********
2023-10-20 08:12:57 (INFO) -- ArmoryQt.py:2190 -    Wallet REDACTED   (Encrypted) ********** REDACTED **********

2023-10-20 08:12:57 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2023-10-20 08:12:57 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2023-10-20 08:12:59 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = D:\Users\REDACTED\BitCoin-Blockchain
2023-10-20 08:12:59 (INFO) -- SDM.pyc:254 - Found Bitcoin Core link on desktop: C:\Users\REDACTED\Sync
2023-10-20 08:12:59 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2023-10-20 08:12:59 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2023-10-20 08:12:59 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2023-10-20 08:12:59 (INFO) -- SDM.pyc:175 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2023-10-20 08:12:59 (INFO) -- SDM.pyc:340 - Called startBitcoind
2023-10-20 08:12:59 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Users\REDACTED\BitCoin-Blockchain
2023-10-20 08:12:59 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=D:\\Users\\REDACTED\\BitCoin-Blockchain']
2023-10-20 08:13:00 (INFO) -- SDM.pyc:451 - PID of bitcoind: 412
2023-10-20 08:13:00 (INFO) -- SDM.pyc:452 - PID of armory:   9572
2023-10-20 08:13:00 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\guardian.exe', '9572', '412']
2023-10-20 08:13:06 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2023-10-20 08:13:06 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = D:\Users\REDACTED\BitCoin-Blockchain
2023-10-20 08:13:06 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\Users\REDACTED\BitCoin-Blockchain\blocks" --satoshi-port=8333 --datadir="C:\Users\REDACTED\AppData\Roaming\Armory\" --dbdir="C:\Users\REDACTED\AppData\Roaming\Armory\databases"
2023-10-20 08:13:06 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="D:\\Users\\REDACTED\\BitCoin-Blockchain\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\REDACTED\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\REDACTED\\AppData\\Roaming\\Armory\\databases"']
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:1824 - Connecting on port 61538
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2023-10-20 08:13:11 (ERROR) -- ArmoryQt.py:1198 - 31 attempts to load blockchain failed.  Remove mempool.bin.
2023-10-20 08:13:11 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2023-10-20 08:13:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2023-10-20 08:13:13 (WARNING) -- ArmoryQt.py:4110 - Called updateSyncProgress while not sync'ing
2023-10-20 08:13:15 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
********* OtisG: SEVERAL PAGES OF THESE WITH NO ERRORS, REMOVING FOR BREVITY **********
2023-10-20 08:22:07 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2023-10-20 08:27:10 (INFO) -- ArmoryQt.py:5475 - BDM state is scanning -- force shutdown BDM
2023-10-20 08:27:10 (INFO) -- SDM.pyc:465 - Called stopBitcoind
2023-10-20 08:27:10 (WARNING) -- SDM.pyc:515 - bitcoind exited, bitcoind STDOUT:
2023-10-20 08:27:10 (WARNING) -- SDM.pyc:517 - 
2023-10-20 08:27:10 (WARNING) -- SDM.pyc:518 - bitcoind exited, bitcoind STDERR:
2023-10-20 08:27:10 (WARNING) -- SDM.pyc:520 - 
2023-10-20 08:27:10 (INFO) -- SDM.pyc:471 - ...but bitcoind is not running, to be able to stop
2023-10-20 08:27:12 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!

[nc50lc]

Here is the content from an updated ArmoryLog.txt log from this morning; the BTC blockchain is up to date.

Code:

2023-10-20 08:12:59 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Users\REDACTED\BitCoin-Blockchain
-snip-
2023-10-20 08:13:11 (ERROR) -- ArmoryQt.py:1198 - 31 attempts to load blockchain failed.  Remove mempool.bin.

Does setting Bitcoin's datadir to "D:\Users\<Username>\BitCoin-Blockchain" in the GUI intentional?
Because for some reason, it wont load.

Try to start Bitcoin Core (bitcoind.exe) with --datadir="D:\Users\<YOUR_USERNAME>\BitCoin-Blockchain" command line argument to see that there's no issue in Bitcoin Core.
If it wont start, tell us the error or the related entry in 'debug.log' file inside that data directory.

[OtisG]

Here is the content from an updated ArmoryLog.txt log from this morning; the BTC blockchain is up to date.

Code:

2023-10-20 08:12:59 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Users\REDACTED\BitCoin-Blockchain
-snip-
2023-10-20 08:13:11 (ERROR) -- ArmoryQt.py:1198 - 31 attempts to load blockchain failed.  Remove mempool.bin.

Does setting Bitcoin's datadir to "D:\Users\<Username>\BitCoin-Blockchain" in the GUI intentional?
Because for some reason, it wont load.

Try to start Bitcoin Core (bitcoind.exe) with --datadir="D:\Users\<YOUR_USERNAME>\BitCoin-Blockchain" command line argument to see that there's no issue in Bitcoin Core.
If it wont start, tell us the error or the related entry in 'debug.log' file inside that data directory.

Yes, that datadir is intentional, because I have configured the data to be on a separate drive.
Running bitcoin-qt.exe has never been a problem, and running bitcoind.exe with the above command line arguments works 100% as expected.
Armory won't kick off Bitcoin Core anymore, but it used to; I must have misconfigured something in Armory during all the debugging I attempted.
I just start bitcoin-qt.exe before launching Armory.

Here is the content from an updated ArmoryLog.txt log from this morning; the BTC blockchain is up to date.

Code:

2023-10-20 08:12:59 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Users\REDACTED\BitCoin-Blockchain
-snip-
2023-10-20 08:13:11 (ERROR) -- ArmoryQt.py:1198 - 31 attempts to load blockchain failed.  Remove mempool.bin.

Does setting Bitcoin's datadir to "D:\Users\<Username>\BitCoin-Blockchain" in the GUI intentional?
Because for some reason, it wont load.

Try to start Bitcoin Core (bitcoind.exe) with --datadir="D:\Users\<YOUR_USERNAME>\BitCoin-Blockchain" command line argument to see that there's no issue in Bitcoin Core.
If it wont start, tell us the error or the related entry in 'debug.log' file inside that data directory.

Yes, that datadir is intentional, because I have configured the data to be on a separate drive.
Running bitcoin-qt.exe has never been a problem, and running bitcoind.exe with the above command line arguments works 100% as expected.
Armory won't kick off Bitcoin Core anymore, but it used to; I must have misconfigured something in Armory during all the debugging I attempted.
I just start bitcoin-qt.exe before launching Armory.

FYI - I just now fixed the directory setting for Armory to spawn bitcoind when I launch Armory; it's synch'ing with the blockchain now.
This is the point where "Scanning Transaction History" stops at 43%.
Incidentally, the estimate for when the transcation history scan will finish never updates from 11 minutes.

[nc50lc]

It's a long shot, but to make sure that it's totally not caused by Bitcoin Core, check your 'debug.log' in "D:\Users\<Username>\BitCoin-Blockchain" for possible blockchain inconsistencies.

If nothing works, you might have to downgrade to v24.1 or your previous working build.
There's no major changes in v25's release notes that could cause incompatibility with you current blockchain.

[OtisG]

It's a long shot, but to make sure that it's totally not caused by Bitcoin Core, check your 'debug.log' in "D:\Users\<Username>\BitCoin-Blockchain" for possible blockchain inconsistencies.

If nothing works, you might have to downgrade to v24.1 or your previous working build.
There's no major changes in v25's release notes that could cause incompatibility with you current blockchain.

I verified the Bitcoin Core debug.log has no errors and no inconsistencies found.
Also, as an FYI, a couple of weeks ago I deleted the blockchain and redownloaded the entire thing; it took ~6hrs.
I downgraded to Bitcoin Core v24.1; Armory still sticks at 43%.
I also tried deinstalling Armory and reinstalling it; same problem.

I'm thinking Windows 11 downloaded updates/patches about the same time I installed Bitcoin Core v25.
In a pinch, I can use a separate Windows 10 server for Armory, but that's an old PC I'd like to use it for other purposes.
Windows 11 is my fastest PC, so if I can figure out this problem, it would be awesome.
 

[nc50lc]

I'm thinking Windows 11 downloaded updates/patches about the same time I installed Bitcoin Core v25.
In a pinch, I can use a separate Windows 10 server for Armory, but that's an old PC I'd like to use it for other purposes.
Windows 11 is my fastest PC, so if I can figure out this problem, it would be awesome.

If you think that it's the cause of the issue, then try to uninstall the latest updates of your W11 machine.
Refer to this article to see how: support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-update

Then, since you've already downgraded and confirmed that you have the complete blockchain but the issue remains, then we can deduct Bitcoin Core out of the suspects.

[HCP]

Interestingly... I have Armory and Bitcoin Core v0.25.1 working ok, but the Testnet version of Armory is exhibiting a similar behaviour to what the OP has. Armory Testnet is getting stuck at "Scanning Transaction History".

It is always at 88% (tried it 3 times now)... very strange. I can't find any obvious errors anywhere that are causing this issue. :-/

[goatpig]

Interestingly... I have Armory and Bitcoin Core v0.25.1 working ok, but the Testnet version of Armory is exhibiting a similar behaviour to what the OP has. Armory Testnet is getting stuck at "Scanning Transaction History".

It is always at 88% (tried it 3 times now)... very strange. I can't find any obvious errors anywhere that are causing this issue. :-/

There's a weird tx in testnet that breaks the DB scanner. I have fixed this in the dev branch, but that code is for along compared to 0.96.5 that I can't just ship the fix back into it.

[OtisG]

I'm thinking Windows 11 downloaded updates/patches about the same time I installed Bitcoin Core v25.
In a pinch, I can use a separate Windows 10 server for Armory, but that's an old PC I'd like to use it for other purposes.
Windows 11 is my fastest PC, so if I can figure out this problem, it would be awesome.

If you think that it's the cause of the issue, then try to uninstall the latest updates of your W11 machine.
Refer to this article to see how: support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-update

Then, since you've already downgraded and confirmed that you have the complete blockchain but the issue remains, then we can deduct Bitcoin Core out of the suspects.

Today I reset Windows 11 by running the built in Windows utility to deinstall all programs completely including Windows 11. I chose the option to download the Windows 11 installation files from the Internet, and I also chose the option to keep my personal files and folders. After that, I reinstalled Bitcoin Core 25 and Armory.

Summary: I get the same Armory result with "Scanning Transaction History" hanging at 43%.

The nice thing is Windows 11 starts a whole lot faster now!, so it wasn't a lost cause.

[goatpig]

Summary: I get the same Armory result with "Scanning Transaction History" hanging at 43%.

1. How much free disk space do you have on the drive with the blockchain data?
2. Can you start bitcoind/qt on its own? What's your top block? Is your Core instance in sync with the network?
3. After starting bitcoind/qt on its own, assuming it's in sync, start ArmoryDB by itself from the command line and post the output here (go through pastebin for big splashes of text)