Not so easy, it turns out.
 
I even tried installing the command center where I want Cakewalk, no luck there.
 
I set the folders in settings in the command center, uninstalled everything and reinstalled... it all went to the C drive.
 
I'm missing something.

While I always use defaults I use directory junctions to move bits to other locations.

Thanks, Scook!
 
I ran the command program as administrator and executed this...

Example
Microsoft Windows [Version 10.0.16299.19]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>mklink /J "C:\Program Files (x86)\Cakewalk" "E:\Program Files (x86)\Cakewalk"
Junction created for C:\Program Files (x86)\Cakewalk <<===>> E:\Program Files (x86)\Cakewalk

 

I think I've got everything working again.
 
One of the things I learned along the way was this...
 
TH3 was saying it was reported to be installed to one directory when it was running from the other.
 
It turned out the Cakewalk had both the E drive path and C Drive path for VSTs in the VST area of preferences. Removing this resolved my issue.

Before you create the junction in the old location, you move the folder to the new location.
 
For example, if you are wanting to move
C:\Cakewalk Content
C:\Program Files (x86)\Cakewalk
C:\Program Files\Cakewalk
to
E:\Cakewalk Content
E:\Program Files (x86)\Cakewalk
E:\Program Files\Cakewalk
 
First you copy the data to the E drive, and then you create the junction by opening the command window and running...
 
mklink /J "C:\Cakewalk Content" "E:\Cakewalk Content"
mklink /J "C:\Program Files (x86)\Cakewalk" "E:\Program Files (x86)\Cakewalk"
mklink /J "C:\Program Files\Cakewalk" "E:\Program Files\Cakewalk"
 
At this point, everything works exactly like it did before. Cakewalk doesn't know you've moved the stuff.