I was merely suggesting a possible reason for the s drive shenanigans. Never called anyone an ahole AFAICT.
 
This is one of those reasons I don't use any auto doohickeys (including CCC) at all on my DAW. Probably wasting a lot of my own time unnecessarily but at least I can control/see where everything is going/what is happening.
 
Not so coincidentally I've never had a problem with CCC as a result. lulzity

I rolled back to Ipswich. Upon 1st launch I had a single error about a single blue tubes vst upon launch.
Then subsequent launches of ipswich were error free as if the scanner corrected the inventory. I am also successful when inserting the fx that were complaining before.  
 
I will try Jamaica plains 32 bit again.

Hey sorry for the uprising.
I just tried Jamaica again and this time it worked.
 
As you was.

Beepster
I was merely suggesting a possible reason for the s drive shenanigans. Never called anyone an ahole AFAICT.

 
To be clear wasn't referencing you. Sorry for confusion Beep.

Wait no it's not fixed. I went back to relaunch Jamaica  and got the image errors again.
Bizarre.

I disconnected the S: drive map and it's all good again.
So I don't know.
 
Gotta get back at it.

What I would do, and remember I'm a dum dum, is go into the Sonar VST scanner's file paths to see if anything in there is pointing to your s drive.... AND I would go into the s drive itself to look for any plugin/Cakewalk/whatever files that should not be there.
 
Sonar is reaching out to the server drive for a reason. It thinks something it needs is there. Disconnecting it probably just removed the path from the scan automatically and once you hook it back up again it'll start hunting again.
 
Again I say... irdum... just making suggestions of where I would look first.
 
Edit: and of course if you do find any paths or files that should not be make them not be anymore (delete them).

Solved guys.
 
The was actually an search folder for s:\program file....64 bit dlls
in my 32 bit's scan options. I don't know how it got there and why other versions didn't care but there we are.
 
Make sense. 64bit dlls were found there and... oh wait, didn't I read that the vst scanner was going to be more discretionary and not include unauthorized vsts or similar? perhaps that is why previous versions did not seem to care about 64bit dlls being found in a 32 bit search path?
 
All I know is previous versions all the way back to x1 days on this partition didn't and don't care about that entry. It has been removed and it's all good now.