streckfus
I only installed the VST3 versions for FabFilter.  

Yes, I am past that point. It is slow going because I have to toggle between a bunch of screens and it takes a long time for my reset to complete. There is a problem with VST3 renaming. I have not figured out exactly what is going on.
 
Been able to change some VST3 names by double-clicking on the plug-in in the Plug-in Manager, entering a friendly name then open the new plug-in name properties and save it away. Once the name is changed it does not want to change again. That is the extent of my research so far.
 

scook
Been able to change some VST3 names by double-clicking on the plug-in in the Plug-in Manager, entering a friendly name then open the new plug-in name properties and save it away. Once the name is changed it does not want to change again. That is the extent of my research so far.

 
I followed those same steps (double-clicking the plugin from the manager) and this time the rename took, at least as far as the browser window was concerned.  I placed the newly named plugins in my layout, saved it, then inserted them into an FX bin on a track, and the name defaulted back to the original.  I went back into the plugin manager and they had reverted back to their original names.
 
I also tried renaming the actual .vst3 file name in my scan path just to see what would happen, and that too was a no-go.  Couldn't remove "FabFilter" from the file name.  Which is kinda funny since the OP wants to see the company name and I don't. :)

I have not tried it but renaming the dll may work if you change the Cakewalk ini variable VSTPluginNameFormat to use the dll name
 
There appears to be something odd going on with renaming VST3 plug-ins. I will make some more time tomorrow to look at it (getting late here). FWIW, the names are stored in the VST inventory in the registry and that is why using the plug-in manager to rename plug-ins is lost when a VST reset happens. It is possible to rename the plug-ins directly in the registry bypassing all the Cakewalk tools.

There are 6 .ini files, two for each version of Sonar (X2 Producer, X3 Producer, Platinum).  One in the hidden AppData\Roaming directory and another in the ProgramData\Cakewalk directory.  I assume both files for Platinum would need to be changed?  When I go to the File>Initialization File through Preferences there's nothing there.
 
Getting late here too so I'll probably save it for tomorrow, but thanks for the heads up.

The programData files are the master files. I would not change those. They are used to revert to factory settings. The files is AppData are the user files read by SONAR. There is no need to work at the OS level, the front end for Cakewalk.ini is Preferenences > File > Initialization File. To see the "Initialization File"  option make sure the Advanced radio button is selected at the bottom of the Preferences dialog.

Yep, I went through Sonar first and went to the initialization file there, but there wasn't any content in that window.

Probably doesn't matter though because I renamed all VST and dll files, rescanned, and the default names came back, I'm guessing because of what you said about the registry.

So I just switched the names back to normal. Not a huge deal since I typically put those plugins in a particular order anyway, it would just be nice to clean things up a bit.

Who knows, maybe it's a glitch that'll get worked out in the next update in a couple weeks!

The Cakewalk.ini is empty by default. Add the VSTPluginNameFormat variable and set the value 1. Unless this is done Cakewalk will not use the dll name for the plug-in. It uses the VST name, a variable inside the plug-in.
 

Because you have waves plugins select 2 as the variable for VSTPluginNameFormat=2 at least I think it'is. Not at my PC at the moment.

One of the options adds the Waves she'll dll name to the back of the plugin name.

Heard back from tech support and they weren't able to replicate the FX Bin/Renaming issue with FabFilter plugins on their side of things.  I did specify that I was using VST3 plugins for Pro-Q 2, Pro-C and Pro-DS and also directed them to this thread to demonstrate that I'm not the only one who's running into issues trying to rename the plugins through the VST Configuration/Properties dialog.
 
Thanks for the clarification on the .ini setup.  I tried renaming the FabFilter .dll and .vst files, but when I brought them into an FX bin I got an error message and the plugin wouldn't open.  So it looks like the .ini workaround won't do anything since both the VST and DLL files have the same names with FabFilter listed first.
 
Thanks for the feedback on this, and sorry to the OP for sort of hijacking this thread.

i just wish there was a way that FX names in the FX Bins can use the name I give it in my custom Plugin-In Layout over the actual VST registered name, as I like my names better.