If you want you can get similar result from Sonar Utils by KPerry. See my Onedrive link in my signature to Onedrive/Sonar Utilities folder.

When bitflipper updates his Plugin Inventory program it will go back there too.

I figured out why Sonar reports a different number of plugins. 
There are several in their own folders that the report does not access. e.g Lexicon LXP Native Reverbs.
 
 

If Sonar scans a plugin then it is loaded into the registry inventory. If the location of the plugin is not in Sonar's scan path then Sonar won't know about it nor will it be in the registry

fireberd
I figured out why Sonar reports a different number of plugins. 
There are several in their own folders that the report does not access. e.g Lexicon LXP Native Reverbs.
 
 

I may be wrong without looking myself, but maybe part of the difference is in the ProChannel modules also.
They aren't actually VSTs outside of sonar so the utility may not recognize them like Sonar does ... without looking lol.
 
Also, you may need to add those additional paths to Sonar to get them to scan properly.
Certain plugins might register through a third-party and work that way, but not register directly in Sonar as expected.

sylent

fireberd
I figured out why Sonar reports a different number of plugins. 
There are several in their own folders that the report does not access. e.g Lexicon LXP Native Reverbs.
 
 

I may be wrong without looking myself, but maybe part of the difference is in the ProChannel modules also.
They aren't actually VSTs outside of sonar so the utility may not recognize them like Sonar does ... without looking lol.
 
Also, you may need to add those additional paths to Sonar to get them to scan properly.
Certain plugins might register through a third-party and work that way, but not register directly in Sonar as expected.

The ProChannel modules are listed as VST plugins in the registry's VST Inventory.

mudgel

sylent

fireberd
I figured out why Sonar reports a different number of plugins. 
There are several in their own folders that the report does not access. e.g Lexicon LXP Native Reverbs.
 
 

I may be wrong without looking myself, but maybe part of the difference is in the ProChannel modules also.
They aren't actually VSTs outside of sonar so the utility may not recognize them like Sonar does ... without looking lol.
 
Also, you may need to add those additional paths to Sonar to get them to scan properly.
Certain plugins might register through a third-party and work that way, but not register directly in Sonar as expected.

The ProChannel modules are listed as VST plugins in the registry's VST Inventory.

Thank you Mike!
I thought so, but wasn't in the studio, and wasn't sure if the utility counted them also with my "plug and play" memory. lol
 

Is there any chance you might add a CSV file option to the output? I use LibreOffice, so it'd be nice to be able to import the list into the Calc module (the direct creation of a Calc spreadsheet being the ideal, but beggars can't be choosers). Thanks!

I have a version here that can create a CSV. Send me a PM with your email address and I'll send it to you to try out. I never published it because it was never adequately tested. You can be my guinea pig.
 
This version does not quote strings. Let me know if your spreadsheet import requires strings to be quoted.

bitflipper
I have a version here that can create a CSV. Send me a PM with your email address and I'll send it to you to try out. I never published it because it was never adequately tested. You can be my guinea pig.

Gladly! It's been a while since I beta-tested anything. Happy to get back in the groove.
 

bitflipper
This version does not quote strings. Let me know if your spreadsheet import requires strings to be quoted.

From what I can tell at LibreOffice's wiki, quotes are an option. It should work without the quotes.

Thanks Bit, this was so easy to use. Pops right open in Excel. I was stunned at the missing stage of confusion. Nice and easy to play with in excel.