I've got this happening too, and while I do run as administrator, and always have, it never happened before the JP update.

That is most likely coincidental. If the scanner is running without you doing anything but loading a project or changing plugin settings, its definitely due to the plugin writing to its folder. Please the folder of all the plugins being used in the project for newly updated files. That will lead you to the one doing the update.
 
You should be able to verify this by not running as admin. If the random scans stop happening then its definitely caused by plugin writes to the folder.

Noel Borthwick [Cakewalk]
That is most likely coincidental. If the scanner is running without you doing anything but loading a project or changing plugin settings, its definitely due to the plugin writing to its folder. Please the folder of all the plugins being used in the project for newly updated files. That will lead you to the one doing the update.
 
You should be able to verify this by not running as admin. If the random scans stop happening then its definitely caused by plugin writes to the folder.

Well the same thing is happening since I've updated to JP...not an issue in Ipswich though...another coincidence? It appears that there are quite a few VST scanning issues coming through related to the JP update, as I'm not doing anything different. My scan gets caught on a WAVE Bass Rider Mono VST - which includes the stereo version as well - and it doesn't get caught in Ipswich...that says to me JP issue.

Have just tried running NOT as an administrator, and the same thing happens. The setting in preferences is "automatic background scan".
 
It's not a big deal or anything, doesn't cause any practical problems, but it is an oddity.

Hmm that is odd if its triggering a scan when you are not running SONAR as admin. That would imply something external is updating the scan folder. Can you try running this utility to detect which file is being updated in the folders when the scan runs?

Will do tomorrow and report back.

I just checked, and yes, I am running Sonar as Administrator.   I'm not even sure why, maybe some testing at one point.  I'm going to try running without administrator, and see if that resolves the issue.

Is it any file or just dll/vst3 that triggers the scan (the FileSystemWatcher event can be set to be global or pattern matching)?

Hi Folks,
 
I believe I have a reproducible case where the VST scanner is intermittently updating (every 5 minutes or so). Would any of you experiencing this issue be willing to send me a project so I can verify the behavior? I would just need the .cwp file without the audio so I can see what plugins are involved. If you can PM me with a link to the project that would be helpful.
 
Thanks!