I have had something similar a while back. Just install over the current installation one more time. I have experienced that positive effect with a second install.

But since you have experienced the bad behaviour at least twice, there is a chance that at least one of the installation files is damaged.

Since RealBand works, take your working installation of BIAB 2014, copy it into a kind of a backup folder. Now you have the possibility to install installation file after installation file and test after each installation. If you have isolated a damaged file, as long as you have the untouched backup installation to reestablish a clean installation base, you may try to test with all the other installation files.

There are about eight installation files for BIAB 2016 and the 49Pak. So you should be able to identify the problem rather fast.

Last edited by GHinCH; 12/08/15 03:45 PM.

Desktop; i7-2600k, 8 GB mem., Win 10 Pro, BIAB 2017; RB 2017 - latest build
Laptop: i5-2410M, 4 GB mem, Win 10 Pro, BIAB 2017; RB 2017 - latest build