VST scanner fails to register plugin when VST3 file is located in a folder by the same name.
For example when
someplugin.VST3 is located within a folder name someplugin.VST3
C:\PROGRAM FILES\COMMON FILES\VST3
└───F-em (64 bit).vst3 (directory)
└───Contents
├───Resources
└───x86_64-win
───F-em (64 bit).vst3 (file)
Seeing more of this happening lately. I'm thinking that some programming SDK (maybe JUCE?) is creating that kind of folder str