VST scanner fails to register plugin when VST3 file is located in a folder by the same name.

[TheSteven]

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 structure when compiling a plugin and the developer instead of extracting only the VST3 is copying the whole folder structure (that includes the plugin) into their installer.
While this is stupid - the issue with the VST scanner failing to register the plugin could probably be avoided if the scanner would verify that *.VST3 is a file and not a directory.

 

[Starship Krupa]

I've seen this happen as well. And yes, silly move on the part of the plug-in developers.

Still, CS should be able to tell the difference between a dll and a directory.