You can change the folders in Sonar preferences. Change and move them.

Has anyone confirmed whether symlinks have any effect on latency or drop-outs?  Or any bad effects whatsoever on Sonar?
 
(I have a linux background, so am used to symlinks, but have only recently started using them in Windows, mostly as a way to get stuff off my C drive.  symlinks have no effect on server performance, but I haven't really considered whether they'd introduce a tiny bit of latency in regards to multimedia streaming.)

Unless I overlooked it, no one has mentioned the reason that is most important for me in wanting to keep as little as possible on C: apart from actual system files.
 
I upgrade and rebuild my system from time to time, which usually involves a clean install. For example, every couple of years I might get a new processor and motherboard, and you generally can't just stick your old system drive into the new machine and expect things to work right. (Some backup software promises "hardware independent" restores, but I haven't tried that.)
 
So an OS installation is needed, which generally means formatting C: and losing everything on it. If you've got scads of sample libraries and the like on C:, they're going to disappear, and you're going to have to put them back by re-installing the libraries, which can be painfully time-consuming.
 
I would much rather keep track of any symbolic links I've made and restore those after a fresh OS install than have to reload libraries.

I prefer to use junctions and never had any latency issues introduced. The "redirection" is seemless for me.
I use Junction Link Magic on Win10Pro.

vanceen
 
I would much rather keep track of any symbolic links I've made and restore those after a fresh OS install than have to reload libraries.

Not following your logic here.  If the libraries are on a separate drive, you don't have to reload them.  Simply point Kontakt (or UVI or whatever) to their location.

JonD

vanceen
 
I would much rather keep track of any symbolic links I've made and restore those after a fresh OS install than have to reload libraries.

Not following your logic here.  If the libraries are on a separate drive, you don't have to reload them.  Simply point Kontakt (or UVI or whatever) to their location.

That works fine for Kontakt, but some synths insist on loading onto C:.

Yeah, I found that some of the "smaller" synths install themselves on C, which is annoying.
 
So regarding junctions vs symlinks: what is the difference, in terms of what we are trying to accomplish here: move entire Cakewalk (and NI) related directories off of C and then link/junction to them?

Macrium would be my go-to for imaging/copying system drives.

Symlinks have been working fine.  In fact, they seem a smart way to go, given that older projects were crashing when I tried to load them after changing Sonar's folder locations to the a new drive.