• SONAR
  • [Solved by scook] Can't Scan VSTs in Sonar X3e Scan Button Greyed Out (p.2)
2016/08/05 10:55:16
pinguinotuerto
In the Cakewalk/Shared Utilities folder I have a Plugin manager, but not a VST Scanner.
2016/08/05 10:56:23
chuckebaby
pinguinotuerto
In the Cakewalk/Shared Utilities folder I have a Plugin manager, but not a VST Scanner.


try installing X3E and let us know what happens.
2016/08/05 11:06:11
pwalpwal
this really is a thread that needs cakewalk input - shared components/utilities are no longer backwards compatible? this is exactly the reason i put off installing a post-x1 demo, as the shared stuff gets updated but left behind after uninstall, noel even suggested it as a way of getting an updated plugin scanner... http://forum.cakewalk.com/demo-question-m3196110.aspx
2016/08/05 11:08:08
pinguinotuerto
I hear ya, pwalpwal!!!!!!!!!!!!!!
2016/08/05 11:17:38
robert_e_bone
The Cakewalk Plugin Manager DID overlay the older scanner, but that was - to the best of my knowledge - the only component that was forced to go to a new version.  All else was kept separate.
 
As scook indicated, a reinstall of X3e will put the older version of the scanning utility back in place for you.
 
Additionally, that reinstall process is not a particularly lengthy process to do - a matter of minutes, really, so it is a reasonable solution, and in this case, the best one.
 
I am additionally wondering if your computer has all Windows Update maintenance applied, and if not, I would suggest you consider getting it up to date on maintenance.
 
Bob Bone
 
2016/08/05 11:20:58
robert_e_bone
As to the overlaying of the scanning utility - I don't know why they did it that way, but for those running older versions of Sonar, would it work to save off the original scanning program, so that the original could be restored without doing a reinstall of X3e?  Just saving it off under an alternate name?
 
Bob Bone
 
 
2016/08/05 11:26:25
pwalpwal
robert_e_bone
The Cakewalk Plugin Manager DID overlay the older scanner, but that was - to the best of my knowledge - the only component that was forced to go to a new version.  All else was kept separate.


thanks bob, but i think cakewalk should say which bits really are left alone (like, is it really all else?) and which aren't, otherwise it's just speculation - i'll speculate that there's more than just the scanner... happy to be proved wrong though! we're engineers, we need to know where the goalposts are!
2016/08/05 11:27:12
pwalpwal
robert_e_bone
As to the overlaying of the scanning utility - I don't know why they did it that way


i'll speculate it's to do with the complexities of uninstallers...
2016/08/05 12:33:57
chuckebaby
I would agree with the need for more input on what uninstalling a Cakewalk Sonar Demo actually removes.
I did quite a bit of searching on this topic to try and help pinguinotuerto solve this in a timely fashion.
The results returned were slim to none.
 
There were topics on uninstalling previous versions, uninstalling present versions but none that covered uninstalling Demo versions. 
Though its not often.This is not the first time I've heard someone say uninstalling the Sonar Demo has changed their current settings in some ways (not missing the VST Scanner) but similar subject lines.
2016/08/05 13:03:49
pinguinotuerto
It's such a bummer and such a hassle that this happened. That's why I don't like installing demo versions, and I regret it now. I wish someone from Cakewalk would chime in and help me out, since they don't seem to have too many support staff working at the moment.
I'm wondering what else the uninstall might have broken that I'm not aware of yet!
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account