It sounds like the original exclude list (the one you renamed) is preventing a crash during plugin scans. If so, you should recover this file before doing another scan. Do this before launching Band-in-a-Box. Then, go to the Plugins Options dialog and look for the specific plugin that you want to un-exclude.
I restored the exclusion files and went to the plugin settings and un-excluded any Waves plugins (somewhat cumbersome task because the dialog closes each time I exclude an individual plugin; there are probably over 100 plugins on the lists, including about 20 instances of PG Vocal Remover, for some reason). Below are the scan results. BIAB crashes when it gets to
BIAS Pedal_x64.dll, despite the fact that this plugin is on the exclude list. Still no access to Waves plugins.
12:08:10 PM : Reading VST plugin file at: C:\Program Files\vstPlugins\sforzando VST_x64.dll
12:08:10 PM : Reading VST plugin file at: C:\Program Files\vstPlugins\WaveShell1-VST 11.0_x64.dll
12:08:11 PM : Error: Could not connect to plugin (C:\Program Files\vstPlugins\WaveShell1-VST 11.0_x64.dll). This is a shell plugin, but no individual plugins were found.
12:08:11 PM : Reading VST plugin file at: C:\Program Files\vstPlugins\WaveShell1-VST 12.6_x64.dll
12:08:11 PM : Error: Could not connect to plugin (C:\Program Files\vstPlugins\WaveShell1-VST 12.6_x64.dll). This is a shell plugin, but no individual plugins were found.
12:08:11 PM : Reading VST plugin file at: C:\Program Files\vstPlugins\WaveShell1-VST 12.7_x64.dll
12:08:13 PM : Error: Could not connect to plugin (C:\Program Files\vstPlugins\WaveShell1-VST 12.7_x64.dll). This is a shell plugin, but no individual plugins were found.
12:08:16 PM : Reading VST plugin file at: S:\Program Files\VstPlugIns\BIAS Pedal_x64.dllUPDATE: I added BIAS Pedal_x64.dll to the exclude list again, and this time when I ran the scan I got an access violation error; I e-mailed the report to your attention. Thanks.