FabFilter Pro-Q not available if "Scan new/updated plug-ins on startup" disabled

EDIT: resolved! see 5th post by me in thread (had to do with Windows directory shortcuts) Steps to Reproduce 1. create a new project (Reaper 6.21) with scan option enabled 2. add fab filter pro-q on a track, confirm plugin is available 3. save project 4. disable "Scan new/updated plug-ins on startup" 5. reload Reaper 6. Observe pro-q configuration remembered, but plugin is not available for use Expectations: I expect all plugins to be available regardless of the scan checkbox value. At > 700 plugins, I'd rather avoid scanning if possible. This happens to other FabFilter plugins as well, I noticed it with Pro-L and some Black Rooster plugins too. Not sure if it was all or not, but Pro-Q is probably enough to start debugging. If more specific information is needed, please forward. I've attached a screenshot and the project file. PC info: OS Name Microsoft Windows 10 Pro Processor Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3504 Mhz, 4 Core(s), 4 Logical Processor(s) 16 gigs mem

Unfortunately I am still getting this in 6.23 :( I am using the same project file I have attached here to test it. Please let me know if I can help with any more info for this fix.

minor update, I upgraded to the latest sws to see if it fixed it somehow, and it did not.

Hmm, is it possible you have multiple versions of FabFilter Pro-Q 3.dll installed? Can you scan all of your VST paths to see if you find any duplicates?