scook
Fortunately the log is easier to generate with the new option in Preferences > File > VST Settings.

The VST scan log is a great new feature addition for troubleshooting Plugin issues, but it won't be useful for finding my new "mystery plug", since you would have to have it turned on before every BandLab update.
(The documentation suggests you should only turn it on in preferences when seeking BandLab support)
 
I tested it just now, but of course it found no new plugins because the mystery plugin is not new anymore.
It only logs the last VST scan.
 
Years ago I installed a Keyboard Controller software that basically duplicated all my plugins, copying and renaming the DLL files. (it scans 522 plugins, but I only really have  around 200)
(Wish I'd read the manual more before installing that, they don't mention it when you buy it)
 
This scan log will be very helpful for me to clean up my VST mess.

My message #17 was in reply to #16 not the OP.
 
I do not pay attention to scan results after a CbB update. In fact, I rarely look at scan results.
 
For future reference, to audit the scan result of an update, set the scanner to manual scan BEFORE performing the update, apply the update, turn on the scan log, run a manual scan, review the log and restore the scan setting.

Okay scook, thanks  . . . I'll give it a whirl next update.