Incorrect scan path for Pro Channel modules inserted by Platinum install into the registry

In the past I had always installed both the 32 and 64 bit versions of Sonar on my main daw, using the 32 bit version and planning on making my permanent move to 64 bit.

Halfway through last year, I made the move to using the 64 bit version of X3.

With Platinum, I installed only the 64 version and I noticed that there was an entry in ProChannel, as an insertable module, GlossEQM available but it didn't have a graphic associated to it.

When I tried to insert GlossEQM, I would receive an error message about C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal\PCS-GlossEQM.dll, I would click Ok and then it would insert a blank module with no graphics or controls called GlossEQM.

I renamed C:\Program Files (x86)\Cakewalk to C:\Program Files (x86)\Cakewalk-archived, did a vst scan and now my Pro Channel modules are showing up correctly with GlossEQM gone.

I don't believe this will be an issue because my laptop, not my main daw, doesn't have a C:\Program Files (x86)\Cakewalk folder presumably because I had only the 64 bit version of X3 installed on it and installed only the 64 bit version of Platinum.

All is working well but wanted to point out this little inconsistency to the bakers.

On a side note, the Platinum seems to be more solid than X3e was.

scook
There should not be a GlossEQM in the PC pick list. The EQ is a permanent fixture in the PC and there can only be one per PC. Are you manually adding PC module paths to the VST scan path?

Yes, I'm aware of that.
I did not add anything to the scan path, it was trying to scan the 32 bit "shared utilities\internal" folder on it's own, for whatever reason.
The only things listed in my vst scan path are my 32 bit vst path, my 64 bit vst path and the path to the 64 bit vst3's.
None of these paths reference the mentioned "shared utilities\internal" folder.

scook
There is a hidden scan path, in 64bit X3, it is HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST X64\VSTInternalPath which is added to the user maintained scan paths.

(for Sonar X series)
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST X64\VSTInternalPath only shows "C:\Program Files\Cakewalk\Shared Utilities\Internal"

(for Sonar Platinum)
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\Cakewalk VST X64\VSTInternalPath  shows both "C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal" and "C:\Program Files\Cakewalk\Shared Utilities\Internal"

I've deleted the "C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal" path entry from
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\Cakewalk VST X64\VSTInternalPath

Sorry for it being TMI but I was trying to be as succinct and detailed as possible.

Renaming the folder as I mentioned in my initial post took care of the problem, I'm sure the registry key did/will too.

Yes I migrated the settings during the Platinum install but it's weird that it added a path to the registry for Platinum that didn't exist in the X series entry.

Definitely a bug that the bakers need to be aware of.

scook
Did cleaning up the key fix the problem?

I renamed "C:\Program Files (x86)\Cakewalk-archived" back to "C:\Program Files (x86)\Cakewalk", did a vst scan and indeed removing that registry entry did the trick.

I don't why it did it but the Platinum install should not have added that entry in the registry, it didn't exist in the registry from previous installs for Platinum to migrate...

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.

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.

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.

Same problem here - I just searched to see if anyone else had this issue and found your thread. Thanks for the tips.