ampfixer
For some reason I have an old version of VST scan in the Kingston download package. In JP it was 5.9.0.40 but with Kingston it has changed to 5.3.0, an older package. It seems to my tiny brain that this older scan version doesn't like Kingston. I just installed 1 new plug and the VST scan said 88 removed and 66 added. Nonsense.
 
Noel and co. know that something's going on and I'm sure that it will get sorted after the US holiday. FIve stars for the Cake crew because even at this time of family and celebration they've been sending me pm's about the issue and I can't ask for better care than that.

Even after scanning failed plugins I assume.
Forgive my ignorance - how do you find the "VST Scan" version number? Thanks.

Noel directed me to it. Program files\cakewalk\shared utilities bottom of the page. Click on the the file and check properties. There's a product version number with 3 digits and file version with 4 digits. The 4 digit number seems to be the important one. In JP it was 5.9.0.40 and in MY Kingston D/L it has reverted back to 5.3.0.0

ampfixer
Noel directed me to it. Program files\cakewalk\shared utilities bottom of the page. Click on the the file and check properties. There's a product version number with 3 digits and file version with 4 digits. The 4 digit number seems to be the important one. In JP it was 5.9.0.40 and in MY Kingston D/L it has reverted back to 5.3.0.0

Thanks..
 
Well my VstScan.Exe is in a different file path (D:\Cakewalk Shared\Shared Utilities) because I moved the shared utilities folder elsewhere. Searched my hard drive for any other copies, this is the only one.
 
I show 5.3.0.0 with Kingston as well... So it looks like it didn't get packaged correctly... that could explain some of the plugin issues being reported here... No issues so far for me, but I guess that is down to good luck.
 

I'm leaving it to the professionals to sort out. No value in being the armchair quarterback for me.

Well, I've updated to Kingston and my VST Scan # is 5.4.1.0!! I've been having some new clicking issues with a couple of plugins-McDSP seems to be a culprit. Wonder if all this is related.
 
 

southpaw3473
Well, I've updated to Kingston and my VST Scan # is 5.4.1.0!! I've been having some new clicking issues with a couple of plugins-McDSP seems to be a culprit. Wonder if all this is related.

I'm not certain, but I'm pretty sure that's the correct number of the VST scan prg. I'm sure it will be clarified in a few days. As long as things are working I won't sweat the details .

Hmmm, I just checked the scanner briefly and the one in Kingston is 5.4.1.0, but the one in JP is 5.3.0.0 I have not rolled back enough to find a 5.9.0.40 version.
 
What is the creation date on that file you found? That is an easier way to find it, as it would have been compiled before that month's release.
 
5.3.0.0 = 10/13/2015
5.4.1.0 = 11/22/2015

The proper VST scanner version for Kingston is 5.4.1.0. Its still somewhat mysterious how John got the older version on his system. We had a prior release candidate installer that had 5.4.0 but we didn't ship that version.
My best theory is that somehow John's machine got delivered a previous binary from Amazon and its stuck in a cache somewhere. Which country are you based in - it might be relevant from amazon's caching point of view? Its pretty hard to diagnose stuff like this over email so I think a support person will have to do more testing with him when work resumes on Monday.
The only problem with 5.4.0 was the first scan problem he ran into. After that it fixes it self up so its not a huge issue despite being disconcerting to see. The scan itself won't affect the operation of plugins.
 
 

Mine is also showing 5.3.0 (22/11/2015 4:04 PM). I have installed the update manually from my cakewalk account (SONAR_Platinum_UP10_Setup_21.10.0.30.002.exe 440,176,584 bytes)

5.3.0.0 in UK. And I did not update straight away. Then again I'm using a different file path as well (see above).