• SONAR
  • Why does Sonar X2 install to C: when I don't want it to?
2012/12/27 15:49:07
ontime
I have set ALL my install paths during the installation of Cakewalk Sonar X2 Producer to another drive. Not a SINGLE path references C: and YET HERE I AM WATCHING A BOATLOAD OF CONTENT GET PUT ON C: DURING INSTALL.

I have a SSD on a tight space budget for my operating system on C:. I want Cakewalk on my hulking magnetic disk. The install routine seemingly offers me a choice of paths. But apparently only for most of the program. It's still throwing up all over C:\ProgramData\Cakewalk\SONAR X2 Producer with "Drum Maps", "Groove Quantize Files", "Metronome", "Plug-in Menu Layouts", etc.

C'mon. This really isn't on. At the end of the day I can live with the 6GB chucked onto my C: but the program really shouldn't be doing this without asking.

Update: it seems some people aren't even bothering to read this post before replying - daveny5 seemed to chip in about something completely unrelated for some strange reason - probably never seen a SSD and is completely baffled by the idea that a system may have multiple partitions. What a n00b.
2012/12/27 16:03:21
scook
Yes, there are parts the must go in C:\ProgramData but it does not take up that much space. On my setup, C:\ProgramData\Cakewalk uses 195MB on disk. Most of the parts of a complete SONAR Producer installation that take up large amounts of disk either prompt for an installation directory or can be relocated after installation. If you wish to relocate stuff after installation, this thread may help http://forum.cakewalk.com...673527&mpage=1#2673527
2012/12/27 17:07:39
Kroneborge
Not sure why there is anything that "must" go on C. There is zero need for it.
2012/12/27 17:23:11
ontime
Thanks scook.
2012/12/27 17:50:10
daveny5
I would let Sonar put everything where it wants to otherwise you may have problems. You can put your projects and audio where you want, but you should let it put the program on C:.
2012/12/28 01:47:04
Bristol_Jonesey
And the problem with moving stuff around after installing is that any future updates may fail because certain files aren't where the installer expects them to be, so you'll corrupt your installation
2016/06/06 16:50:26
Ash Telecaster
This is a bad practice. Cakewalk needs to rethink this and correct it. 
2016/06/06 19:20:09
craigr68
This is one of my complaints also.  I predict a SSD in my future and would like to spare the C drive.  However, I wonder if it would run noticeably faster with the Cakewalk code on the SSD. 
 
Currently, I'm running SONAR Pro with spinning hard drive partitions C & D.  I'm pretty sure during installation that I was not allowed to change the location of most of the core program.  However I was allowed to with later purchases of Z3TA and Rapture Pro which I put on D drive.  I guess it's not a huge amount of C space, but here's my current Cakewalk folder sizes (the ones I know of):
 
Folder                              Space Used    Files    Folders
C:\Program Files\Cakewalk           5.36G         16121    770
C:\Program Files (x86)\Cakewalk     656M          2391      90
C:\ProgramData\Cakewalk             1.28G         3558     151
D:\CAKEWALK\CONTENT                 9.33G         56734    1380 (contains project files, z3ta, rapture pro samples)

2016/06/06 19:39:06
ampfixer
Ash Telecaster
This is a bad practice. Cakewalk needs to rethink this and correct it. 




No, responding to a 4 year old post is bad practice. 
2016/06/07 05:13:32
Bristol_Jonesey
ampfixer
Ash Telecaster
This is a bad practice. Cakewalk needs to rethink this and correct it. 




No, responding to a 4 year old post is bad practice. 


Correct.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account