Hello everyone, I hope you all are having a great day. A few days back, I started facing this error that anytime I installed a new plugin, its facing this error, "There was a problem opening the plugin (plugin name) for an unknown reason. Please make sure it was installed correctly". I don't know why this is happening and I really need to sort this out. All the plugins are working just fine in Ableton. It;s just FL Studio that's facing this issue. I will attach screen shots as well for reference. I also saw that any time I installed a plugin, the vendor name is changed to Navie D. I bought this guy's plugin called NoteGrabber2 and since then I am facing this issue. I really need help solving this. Any help is appreciated.

 

try disabling "Rescan plugins with errors" if enabled in FL...

 

They are still popping up in my plugin manager. Even after turn the said option off.

 

FL Studio frequently experiences errors during plugin scanning. Often, this is because a plugin is installed in the wrong folder or duplicates exist in the same folder. Sometimes, if plugins are not programmed correctly, FL Studio can cause errors in the assignment process.

Try uninstalling FabFilter and deleting all remaining files, then install only VST3 or only VST2 in the following folders:

VST3 Plug-in path:

C:\Program Files\Common Files\VST3
32-bit VST3 plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3

VST2 Plug-in path:

C:\Program Files\Steinberg\VSTPlugins
C:\Program Files\VSTPlugins
C:\Program Files\Common Files\VST2
C:\Program Files\Common Files\Steinberg\VST2

32-bit plug-ins on 64-bit Windows: C:\Program Files (x86)\Steinberg\VstPlugins

 

I noticied now that my plugins are getting scanned alright, but only VST2s. For example, Fabfilters plugins are getting scanned perfectly, but only VST2. The VST3 is getting error as shown in the above photos.

 

Did you already remove this plugin to see if that really is your problem?

 

Yes, I already removed the plugin. Stil facing this issue. I think Navie D has some rights to change my plugins or something, I don't know. Please help. I am up for any solution.

 

I have not used FL in years, but that one just seemed like common sense and had not been confirmed as deleted. Here's a different AI take on it, and one that makes sense.

See if this applies

Spoiler

What’s probably going on

1. VST3 registration in Windows uses XML “.vst3” plugin info files
   Each VST3 plugin has a companion “info” record stored in
   
   
   C:\ProgramData\Common Files\VST3
   
   and its internal registration data lives under the Windows registry at
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\VST3
   
   and/or
   
   
   HKEY_CURRENT_USER\SOFTWARE\VST3
   
   
2. NoteGrabber2 likely wrote malformed or hijacked entries there
   Some developers mistakenly register their plugin as the default or overwrite global VST3 registry associations (for example, writing their own vendor name as a blanket value). If those registry keys or plugin descriptors got corrupted, FL Studio would fail to initialize any VST3 plugin, while VST2s (which don’t rely on that system-level registration) still work fine.
   
   
3. Ableton works because it’s more permissive with broken VST3 descriptors
   Ableton doesn’t validate vendor metadata as strictly, so it may still load the binaries — whereas FL refuses to open any plugin whose registration data doesn’t parse cleanly.

What to check or repair

1. Check the VST3 registry keys
   Open regedit and inspect:
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\VST3
   HKEY_CURRENT_USER\SOFTWARE\VST3
   
   Look for anything mentioning Navie D, NoteGrabber, or unexpected default values (like “Vendor = Navie D” for unrelated plugins).
   If found, export those branches for backup, then delete the corrupted ones.
   
   
2. Clean VST3 cache / rebuild it
   Delete the contents of FL Studio’s VST3 cache:
   
   
   %LOCALAPPDATA%\Image-Line\FL Studio\Settings\PluginManager
   
   (You can just delete the cache files; they’ll rebuild automatically.)
   Then open FL → Plugin Manager → Clear plugin cache → Rescan (fast scan unchecked).
   
   
3. Repair VST3 installation
   If the registry keys are heavily damaged, you can reinstall the VST3 SDK redistributable (Steinberg’s runtime) or reinstall a known good VST3 plugin like FabFilter to re-register the VST3 subsystem properly. That often repairs global registration automatically.
   
   
4. Last resort: clean registry reset
   If all VST3s continue failing, export and delete both HKEY_LOCAL_MACHINE\SOFTWARE\VST3 and HKEY_CURRENT_USER\SOFTWARE\VST3, then reinstall any VST3 plugins to rebuild clean entries.

In short
NoteGrabber2 almost certainly damaged your system-wide VST3 registration, not FL Studio itself.
That’s why:

• Only FL (which strictly parses vendor entries) is choking,
  
  
• All vendor names show as Navie D,
  
  
• VST2s still load fine, and
  
  
• Ableton (more forgiving) still runs everything.

Fix is: clean the VST3 registry keys and FL’s plugin cache, then reinstall one or two known-good VST3s to repopulate the registry.

 

First, delete the "NoteGrabber2" plugin and notify the developer if there's a solution.

Could you check if you have this package installed and then delete it?

Navie D's Free Minipack (FL Studio Tutorial Pack) – Free sound pack
www.itsnavied.com/choice

 

I have deleted the plugin. I am still facing this error. Is there any windows settings that I can check for residuals of Navie D.

 

A: This might be because you installed noteGRABBER into a custom folder.
DAWs typically require plugins to be installed in the VST3 folder to be visible.


Try reinstalling noteGRABBER into one of these folders:

- `C:\Program Files\Common Files\VST3`
- `C:\Program Files (x86)\Common Files\VST3`

A: A full list of common problems can be found at www.notegrabber.com/support.
If you want to contact me directly, email me at [email protected].