• SONAR
  • Sonar Platinum custom install directory - broken in recent versions? (p.2)
2016/07/28 06:40:22
fireberd
I have my projects on a different drive.  I had to reset it to the drive I have it on.  It had been changed back to the "C" drive by Sonar update.
2016/07/28 17:00:31
SigiZ58
Same Problem here!
 
Hello,
 
since a while I am in Sonar. I have installed my Sonar Platinum to Drive D:\Musik\Cakewalk\....
 
With the newest update SONAR_Platinum_Setup_22.7.0.41 the installer forces the Installation to c:\program files\Cakewalk...
 
It does not make any difference if I install with the Command Center or use the installer file. No difference if I choose simple or expanded Installation. I can change all pathes ... except the application. It says it takes the path from the previous Installation, but that is not true, as I have it on drive d:
 
I checked registry entries, but all point to the correct path (d:\musik\...)
 
I am sure this is new as I made already several updates and never had this issue before.
 
I use German language - no idea if this happens also in other languages.
 
Until now Platinum as well as Artist is affected.
 
Please look into this, as it is **** to change a million registry entries to make it work on drive d: again....
 
And even a reinstall shows this as final choice
 
Zielordner:       C:\Program Files\Cakewalk\SONAR Platinum       D:\Musik\Cakewalk\Shared Components\ (Shared Components)       L:\Library\Cakewalk\Cakewalk Content\ (Application Content) 
 
For me this is important as I have all my music applications NOT on drive C: And I dont want them there.
 
Thank you.
 
 Siegfried
2016/07/29 17:49:01
SigiZ58
No more replies to this thread ? Are really only a couple of people affected by this issue ?
I decided to make a Support ticket. I really hope, Cakewalk takes us serious and realize this is a bug and promise to fix it so that we can stop to wave our arms.
It has been working until and with June Update.
For me this is more important then new Features in the moment :-)
 
2016/07/29 20:35:27
bluesplayer
I didn't report it here but I also activated a support ticket as a Lifetime SPlat user (and being a customer since 1989)  I tired calling but you know how that goes!
 
2016/07/30 10:49:10
ziki.records@gmail.com
Hi, same problem... i DO NOT Want to install to c:\program files\Cakewalk...!!!
2016/07/31 07:27:07
Rob from Sydney
Good idea Sigi and Bluesplayer - I've just logged a ticket too.  I know Cakewalk usually follow along here (and will definitely read the 2016.07 thread you have posted into) but keen to know the problem is logged.
 
I can only imagine it is an easy fix and a simple error on Cakewalk's behalf - but on the other hand why would that part of the installer code have even got touched unless something was meant to change!
 
I guess since a) its still pretty early days for 2016.07 yet and b) there is a lot of people, but still maybe not that much as a proportion, who install it to custom paths, it hasn't got that bigger mention here yet.
 
My main concern for others who rely on that setup and aren't aware of this "bug" (?), click through the installer without realising and then has to go through the effort to rollback/move/fixup their system.
2016/07/31 13:33:57
mcdonalk
I wish you all the luck in the world getting a response to your support ticket.
 
I, too, am delaying the update until this issue is resolved, since I also use a preferred alternate location.
2016/07/31 17:53:05
SigiZ58
I am really curious how it comes out. I am relative new to Sonar. The program fits my demands very well. With the Support we will see how it goes. When you read through the forum, the comments relating this seems ..uugh ... ambivalent. 
 
But a ticket seems in any case be the correct way, at least for the protocol. 
2016/08/01 17:06:40
SigiZ58
After the last reply in the Sonar 2016 07 Upgrade thread I checked again the Installation.
 
This is the outcome:
Running SONAR_Platinum_Setup_22.6.0.26.exe
1) Language
2) 64/32 Bit
3) "Previous Cakewalk Product detected"
4) License Agreement
5)  Basic/Advanced (->Advanced)
6) Choose Application Path
7) Startmenu Path
8) Shared Folders Selection (In Grey, as these are set from previous Installation)
-> remark: if you choose at step 5 Basic, then also the folder c:\program files is Chosen, even if your current Application Directory is customized! This means, only the library/content Settings are used from the previous Installation!
 
Running SONAR_Platinum_Setup_22.7.0.41.exe
1) Language
2) 64/32 Bit
3) "Previous Cakewalk Product detected"
4) License Agreement
5)  Basic/Advanced (->Advanced)
6) Choose Application Path -> Has been removed with this release
7) Startmenu Path -> Has been removed with this release
8) Shared Folders Selection (In Grey, as these are set from previous Installation)
-> remark: this seems, as if the developer have removed this, thinking this only is needed by a fresh Installation. This works with the library, but obviously not with the application path (did not work before also, see the above remark when you choosed Basic Installation). Until now it was not a big Problem, as you could override this Settings with Option 7)
 
The main bug is (and was) that the application path is not preserved with an upgrade Installation! 
The problem in this release is you cannot any longer correct this problem with manual set the correct application path. In every future upgrade Installation this will be overwritten again.
 
Prove:
Would the application path be used from the previous Installation, you should be able to use the Basic Installation Option and not get the actual Appplication Installation overwritten with C:\Program Files\Cakewalk.... in this case.
 
Solution for the developers: Use the current application path in the Installation Routine instead overwriting it with C: !   
 
 
 
 
 
 
 
2016/08/02 06:18:36
Rob from Sydney
I've just put an update into the main 22.07 thread since at least it got Lance's attention there.
 
In short a workaround (see the other thread for more info) - at least for me here, your results may vary; Uninstall (using Control Panel -> Programs and Features) then immediately (new) install of 22.07 gave me the choice for the path, and has installed to there.
 
Not prepared to mark this solved yet - it clearly isn't how its meant to work, but at least got me up to the current version.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account