Cakewalk not starting with different install directory?

Downlaoded (not installed) Sonar Artis with the Command Center, then launched the install.exe and put everything to drive F (install dir, content dir, VST plugins dir). Launching Sonar now only shows me the initial logo and doesn't continue .. just hangs there. It's a freeshly installed W10 laptop (same thing with default dirs on my desktop works).
 
Any ideas?
 

Nope, doesn't. It just sits there doing absolutly nothing. I can not even kill the process in task manager. Everything else works perfectly .. that laptop is a daily work machine. Tried stopping the virus scanner (although the same scanne ron the dekstop does nothing to Cakewalk) etc .. nothing helps. And it is a freshly installed W10.

I'm not sure what you mean. If you merely use the Control Center to download things (right click) and not install anything, then the Control Center paths mean nothing, those seem only to be used if you install through the Control Center. If you run the downloaded installation EXEs by hand, you are asked to specify all necessary pathes, more than you can specify in the Control Center (like the main install dir etc). The registry etc points all to the F drive, as intended.

Sorry - I hadn't read your initial post properly, and didn't realize you had not used CCC for the installation.
 
I run all of my installs through CCC, and it manages it all just fine for me.  The only pain was sitting through installs of things like Dim Pro and Rapture, since they had been installed already, but I wanted to bring everything under the management of CCC so I installed them with command center on top of perfectly good prior installations of them.  Even that was maybe 10-20 minutes of extra time, but now CCC controls it all for me and that's fine.
 
Perhaps one of the paths for something you specified in the install is not correct?  It seems quite likely to be something done or not done in the install, or maybe something with Windows maintenance - some kind of issue local to your environment, as there is no general posting of similar issues from folks having post-install failures to launch.
 
Bob Bone