A few years ago I set up an offline storage of bitcoin in Armory. I dutifully printed out a 3(n) of 6(m) fragmented backup version 1.35c. I tested it and it worked. I'm trying to restore this wallet now and have all six pages here. When I sync the entire blockchain, then go to restore the wallet in Armory, it recognizes the proper Fragment ID, but when I accept it I get a line saying "This is for fragment #" and then it doesn't list any data. I go to the next line anyway and type in another page, then another, giving me three. No change. In fact, on the "Restore wallet fragments" window I get no indication I've done anything.

If I then add a seventh fragment, then immediately remote this blank one, suddenly I get the display updated with all three (or six) fragment IDs and they're correct. So it obviously got the data. Unfortunately, the "Restore from fragments" button never illuminates so I'm stuck at that point. On the right under "Wallet being restored" nothing ever shows up.

This has been replicated on three PCs running the latest release. Somehow on one of them I *did*manage to get the appropriate wallet ID restored, but it shows a balance of 0l.0 because that machine never got the entire blockchain and frankly it's so slow I really don't want to spend a week with it pulling down the blockchain only to maybe have the same problem.

Surely this UI error hasn't persisted for the couple of weeks I've been screwing around with this off and on, has it? 

Yep. Odd. So I basically just renamed my L:\Armory folder, created an empty one, and had Armory rebuild the database from the blockchain. Then imported my wallet files from the old folder. Seems to be working.

I hadn't done any actual transactions with my wallet in a while until yesterday. I noticed that while I could send bitcoins out, the database didn't seem to be updating. I'd have a bunch of confirmations visible on blockchain.info, and none reflected in Armory. So after much fiddling around, I upgraded Bitcoin Core to 0.15.0.1, and Armory to the latest version which appears to be 0.96-beta-a3d01aa722.

ArmoryDB, however, commits suicide at 81% through scanning the transaction history:

I don't know why it's falling on its face like this but I presume that there's a corrupt block. Unfortunately, since it isn't telling me which one to delete and redownload or even giving me a timeframe, it isn't so easy.

I'm going to try a complete rebuild of the database and see how that works.