I tried your trick, and it worked--except that Waves VSTs still aren't showing up. Do you have waves VSTs showing up by any chance?

Unfortunately, I discovered that the bug with Waves AUs still exists in 8.4, making them a pain to use.

Thanks,

Kilroy

Same thing here. Moved VSTs to user-specific plug-ins folder and it looks like they all showed up except the Waves. AU Waves work though, so that's strange that the VSTs won't show. Perhaps, it's because they don't belong in the user-specific VST folder? Which leads me to ask... if the AUs show up without having to move those, why should we be required to move our VSTs to our user-specific folder? Doesn't make sense.

Same issue here. The entire system VST folder does not show up. I copied all my VSTs into a different folder and set that as my custom VST folder in preferences and that folder does show up with all my 64 bit plug-ins.

We have located a problem on OSX concerning missing plugins in your VST panel. This should be fixed in the upcoming beta version. You can help by confirming following will fix the problem.

If you start any ableton version in 32 bit mode, your ableton preferences.cfg will be locked to this bit depth. This is the reason for 64 bit plugins not showing up in the browser in spite of deeper rescans holding alt.

If you start the 64 bit version after this you will only see 64 bit plugins, and the 32 bit plugins will be missing. Should you wish 32 bit plugins, please repeat the steps, or launch the 32 bit version as the first thing.

We have not heard of windows users with this problem. If yes, please reply to this thread and try the same steps as for OSX to verify the fix. The cfg file is located here under windows:
C:\Users\[username]\AppData\Roaming\Ableton\Live 8.4b2\Preferences

I would like to close this thread as the risk is to high that we oversee another problem than the VST scanning problem. This VST scanning problem is known and will be fixed in 8.4b2. For more information please see