Opening X1 songs.

rkl122

grumbleweed4162


...... - checking for everything I can do to make the file association work but it just does not want to know.
I'm getting the impression that this is either a unique problem or nobody else opens X1 by clicking on an song file.

........
  

Doing the stuff you've already tried should have accomplished this automatically, so if you do in fact find the 8.5 version referenced in those keys, there's probably something else going on - eg. a UAC problem. 

HTH  -Ron

rkl122

......- I logged in as my son and could associate X1 with the song file (and had the fun of watching what Sonar does when somebody else goes to use it for the first time).
As I am the main user on the pc and have all of the admin rights what can I do to make it respond as it should? (I'm not keen on messing with the registry). ..........

Ah.  Multiple logins.  (Not the case here; would have been helpful to mention this in first place, but understood you didn't appreciate significance.)  Hopefully someone with direct expertise will advise.  (Cancel my registry tweak advice.)

Perhaps X1 was installed from your son's account, without admin rights. The fact that you have admin rights doesn't automatically expose the program's initiation to them.  Windows distinguishes user privileges from program privileges.   (That's why even an administrator gets that "this program needs to be elevated, etc. " message sometimes.)  When you are logged in, does X1 appear in the Control Panel's Programs and Features section (as it should under your son's login)?  Your son could unintall and you could reinstall from your own login, but there may be a less tedious way. 

One thing to try under your login, since you have admin rights:  navigate to the actual X1 install directory - probably C:\Program Files\Cakewalk\SONAR X1 Producer\ right click on sonarpdr.exe click properties=>security tab=>Advanced=>Permissions.  Select all administrators and click Change Permissions  Select them again and click Edit.  Assign full control.  "OK" out.  May as well repeat the process for the entry representing just yourself. 

What I'm not clear on is whether file associations are in a single place in the registry and simply need to be exposed on a per user basis, or whether they need to be defined initially on a per user basis.  If the above does not work, then I can only think to uninstall completely from your son's login and reinstall from your own, since it's during install that the proper file associations should be established.  (Come to think of it, the problem may stem from simply bypassing that screen during the install.  Then again, that doesn't explain why it works properly under your son's login.)

It's not a complicated issue (despite my making it sound so ;) , just needs to be done right.  Hopefully someone with more explicit knowledge of the process will confirm/improve/modify/replace my advice.

Good luck,

-Ron