• SONAR
  • Incorrect scan path for Pro Channel modules inserted by Platinum install into the registry (p.2)
2015/01/20 15:24:08
gustabo
Checked the entire registry and nowhere did the x86 shared utilities folder location show up associated with an x64 installation of Sonar x, only with x86 installation of Sonar X.
Platinum was not installed as an x86 app so it should not have migrated any settings from any previous x86 app and I did select my Sonar X3 Producer (64 bit) as the source of preferences migration.
2015/01/20 15:37:08
scook
I did not expect the internal 32bit path would be in the 64bit X series registry anywhere. Just wanted to confirm the machine still had the internal 32bit path in a 32bit X series registry entry which appears to be the case.
 
Also assumed, based on the initial post, only 64bit Platinum was installed.
 
To summarize:
1) The machine had 32bit and 64bit X3 Producer installed when 64bit Platinum was installed.
2) During installation 64bit Platinum picked up both the 32bit and 64bit VSTInternalPath from X3 and added them to the 64bit Platinum VSTInternalPath
 
2015/01/20 16:01:17
gustabo
scook
To summarize:1) The machine had 32bit and 64bit X3 Producer installed when 64bit Platinum was installed.
2) During installation 64bit Platinum picked up both the 32bit and 64bit VSTInternalPath from X3 and added them to the 64bit Platinum VSTInternalPath

Yes, that is correct.
2015/02/10 14:09:35
Splat
Could you post a CWBRN number here please?
https://www.cakewalk.com/Support/Contact/Problem-Report
 
Thanks..
2015/02/10 15:22:14
gustabo
Nope, I fixed it so I never reported it. My problem may have just been a fluke, never saw anyone else ever have an issue like mine.
2015/02/10 16:22:32
Splat
OK thanks... I treat this as a troubleshooting thread then and pop it into the Sonar forums...
If we get loads of "me too's" we can always move it back...
 
Cheers...
2015/02/20 05:30:52
LJB
Same problem here - I just searched to see if anyone else had this issue and found your thread. Thanks for the tips.
2015/03/02 09:04:44
Noel Borthwick [Cakewalk]
This issue has been fixed in the Braintree update as far a i know. I believe the root cause was a bug in the migration code which would migrate the internal path from an earlier version of SONAR. In fact it would migrate from SONAR X2 if present rather than SONAR X3. In Braintree I now restore the proper internal path after the migration process.
 
However users who already migrated earlier might still have the bad path in there. Your work around is good. Alternatively users can force migration again after installing Braintree to fix it up. This may or may not be a desirable solution however since any post migration customized settings would get lost. 
To force migration again go to HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\Platinum
Then change the value of Migrated Existing Preferences to 0 and restart SONAR.
 
If you don't feel comfortable editing the registry call tech support and they can help you. Users who didn't migrate shouldn't have had this issue.
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account