Re: Armory 0.96 is out

I upgraded from Armory 0.95.1 with Bitcoin Core 0.13.2 to Armory 0.96.0 for Ubuntu/Debian 64-bit with GCC 5.3. because I had two unconfirmed transactions (2 weeks old), which I wanted to clear.
Now, the new version of Armory doesn't finish Scanning Transaction History (1 second left)....I started Bitcoin Core with "bitcoin-qt --disablewallet" manually (this was the only possibility to get it working with Armory 95.1, therefore I just continued to do the same with the new version)
In
armorylog.txt:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 12:32 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/andi/.bitcoin/
blocks" --datadir="/home/andi/.armory/" --dbdir="/home/andi/.armory/databases"
2017-05-10 12:32 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/andi/.
bitcoin/blocks"', '--datadir="/home/andi/.armory/"', '--dbdir="/home/andi/.armory/databases"']
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1188 - 3 attempts to load blockchain failed. Remove mempool.bin.
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
...1000x
2017-05-10 12:56 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
-----------------------------------------------

Help would be very much appreciated! Should I upgrade to Bitcoin Core 0.14.1 to solve my problem?