Hi all,
 
I've always had my Cakewalk installs on a D:\DAW folder - easier to find it all, backup, shorter folder names than "Program Files" etc.... I guess many will do similar with SSD drives as well.
 
As we know, CCC doesn't let you customise the install directory, only content and VSTs.  Annoying, but whatever, I just download and install manually and only use CCC to tell me what needs updating.  I fully support the feature request made in other post to allow CCC to a) just perform the download, and b) run every install in advanced/manual (rather than its silent/automatic) mode.  But anyway, that is a side issue to my current problem.
 
In the past, running the installs I get to change the main Cakewalk installation path.  Haven't updated for a while and just went to install 22.07 - and when using the manual install and selecting Advanced, I get to choose various paths such as VSTPlugins and Content, but the program itself insists on going to C:\Program Files\Cakewalk\SONAR Platinum.  At this stage I've cancelled the installation as I really don't want it to go there, and don't want to break the existing install. 
 
I was previously on Manchester (21.12), and just to test downloaded and installed 22.03 now.  Both of these still let me choose the path. 22.07 Doesn't.  Has this changed for anyone else either? (maybe in an earlier version, I haven't tried the versions between 22.03 and 22.07?)
 
And if so, has anyone got a workaround? Or hope Cake realise its a problem and wait for a later version that gives the customisation back?
 
Hope to hear from others who might be in the same boat.
Rob.

WRT the first half of this post, running the Command Center in with Verbose Mode enabled should show the same prompts as running the installers manually. This option has been available for some time.

Thanks - didn't pick that up when I looked first time, checked all the Path options but that was on the other tab!

scook
WRT the first half of this post, running the Command Center in with Verbose Mode enabled should show the same prompts as running the installers manually. This option has been available for some time.

scook,
 
So, since the OP (or anyone else) cannot choose the install path of the core program manually with the latest update, and since he will receive the same options under CCC as he did manually, isn't he still facing the same limitation? Or, did I misunderstand your point? And, if one can no longer choose where everything goes by doing a manual install, and likewise one faces the same limitations using CCC, what in the world was the logic in removing the complete custom install option?
 

I cannot say for sure. I use default locations. It might be the install process only permits setting the program path during the initial install (or a clean reinstall). My understanding is this is not an initial install so the program path is already set.

scook
I cannot say for sure. I use default locations. It might be the install process only permits setting the program path during the initial install (or a clean reinstall). My understanding is this is not an initial install so the program path is already set.

Ok, but as he said, his initial installation and subsequent updates were all on his D: drive - he could always set the main program installation path manually. It's just the latest update that won't allow him to set the installation path to the D: drive. It only allows installation on the C: drive. If true, that is a fundamental change. And not for the better. Why would Cakewalk take away a customer's option to choose where to install programs?
 
I've got a lifetime of updates, but I can no longer put them where I want on my computer? Doesn't make sense. Rob from Sydney, I hope you're wrong. Maybe you missed something?
 

there is no way cakewalk would take a way the option of where Sonar is installed.
im sorry if im misunderstanding the question but there is just no way.
too many people have custom set ups.
 
My guess is the OP is not using admistrator privy's or he missed something in the install / in CCC

Rob from Sydney
Hi all,
 
I've always had my Cakewalk installs on a D:\DAW folder - easier to find it all, backup, shorter folder names than "Program Files" etc.... I guess many will do similar with SSD drives as well.
 
As we know, CCC doesn't let you customise the install directory, only content and VSTs.  Annoying, but whatever, I just download and install manually and only use CCC to tell me what needs updating.  I fully support the feature request made in other post to allow CCC to a) just perform the download, and b) run every install in advanced/manual (rather than its silent/automatic) mode.  But anyway, that is a side issue to my current problem.
 
In the past, running the installs I get to change the main Cakewalk installation path.  Haven't updated for a while and just went to install 22.07 - and when using the manual install and selecting Advanced, I get to choose various paths such as VSTPlugins and Content, but the program itself insists on going to C:\Program Files\Cakewalk\SONAR Platinum.  At this stage I've cancelled the installation as I really don't want it to go there, and don't want to break the existing install. 
 
I was previously on Manchester (21.12), and just to test downloaded and installed 22.03 now.  Both of these still let me choose the path. 22.07 Doesn't.  Has this changed for anyone else either? (maybe in an earlier version, I haven't tried the versions between 22.03 and 22.07?)
 
And if so, has anyone got a workaround? Or hope Cake realise its a problem and wait for a later version that gives the customisation back?
 
Hope to hear from others who might be in the same boat.
Rob.

Rob,
 
I can verify/vouch that current release 22.7.0.42 doesn't ASK or allow setting an install path, it assumes C:\Program Files (and installs there).  I also install, and have been since about Windows 3.1,  on a D:\  drive  (I would have installed it on a "D:\"  when using CW for DOS version 2 but only had ONE 40MB drive then :-) )
 
I also install WITHOUT using CCC (i.e., manually the old fashioned way, actually CCC is just more overhead I don't want or need).  Therefore, any paths set or not in CCC are immaterial, at least in my case.  Plus, I run everything as Admin (actual Administrator - no UAC even in play)
 
Anyone can test this in about 2-3 minutes - try to INSTALL current release (manually) and see if it even ASKS you where.  It use to be the FIRST path (if you select Advanced and not Basic  - install) that you can change, that it asks for.  You can verify that with any, and ALL, previous SPLAT releases it does ask for path to install and that's where it installs.
 
Don't have to actually complete the install just manually start current then any previous release and go to last step where it lists where and what it's about to install -then hit cancel.
 
Larry
 

Same problem here. The installer just installed to C when my previous install was on F

Thanks Larry, yes, that's exactly the behaviour I'm observing, thanks for the confirmation.
 
To some of the confusion everywhere, yes, Scook's solution doesn't fix this problem, but did solve my oversight of the extra option in CCC.  However the problem I'm having is completely unrelated to CCC so easier just to test with manual installs.
 
Given it was my first update in a while, I was also unsure if it was a new (22.07) change or not.  I've since downloaded 22.06 to test and the path could still be changed there.
 
Also just tested 22.07.0.38 (the early access) version and it does NOT let the path change either.
 
Administrator privileges don't seem to change anything.
 
I wonder if anyone at Cakewalk can provide any advice on whether this is intentional or an oversight?  Are custom install paths gone for good or will I just update to 22.06 for now and hold out for a fix in the (near?) future?
 
Earwax - I also hope I'm wrong and missed something but haven't managed to have any more luck yet.  I'm keen if you can try it out just to check it isn't a set-up issue I (and Larry) have. Again as Larry said, hit CANCEL at the confirmation dialog when it shows all the paths, you don't have to go ahead with the install.
 
Rob.