Studio midisound
Your questions earlier Bob
1. I don,t know what this means..I,m the only user of my pc and I don,t know if I run als ADM...where can I see that
2..No antivirus
3..It,s à 64 bit install. 4 Day,s ago, it is not. the download version but the hard copy on 4 dvd,s
4..Windows 7. Intel i7. 950. 3.07 GHz. REM 8 in 8 out + focusrite mic preamp
Never had any problem with 8.5.3...the problems startend when I installed x3

The "run as administrator" thing is important and even if it doesn't fix the dx plugins problem, go ahead and do it.  To "run as administrator" right click on the X3 icon (or X3.exe file) and choose "Properties", then either choose "Advanced" or "Compatibility" (I don't know what version of Windows you're running) and check the "Run as Administrator" box and then hit apply, then close.    Good luck.

It would have been the 'easy fix', and was worth a shot.
 
Since you were not familiar with Run As Administrator, I am thinking your install was done without setting that option 'on', and that this may be a part of what you are having trouble with.
 
I do not have anywhere near enough coffee in me to type out the instructions for a 'clean' removal of Sonar, although I am willing to fight my brain on this and try.  :)
 
In any case, it is my recommendation that you:
 
1.  Save off any custom content - project and/or track templates or whatever, so you do not lose them when removing the current install of Sonar.
 
2.  Do a clean removal of the current Sonar X2 install, including any shared components, as they too may not work properly if installed without the Run As Administrator option set.  I will list these steps at the end of this post.
 
3.  Install Sonar again, THIS time with the explicit Run As Administrator option set, per above, to make sure your installation process has the highest level of privileges possible.
 
4.  Once installed, I also recommend you permanently set the Run As Administrator option for the Sonar launch icon.
 
PLEASE NOTE that prior to beginning any of the above, I HOPE someone else on the forum can review and either give the above steps the go-ahead, or add/correct where needed.
 
In any case, I hope the above will correct your issues.  
 
Here are the steps I follow for a clean removal of a particular installation of Sonar.  PLEASE NOTE that these steps are written assuming you have X2 Producer installed.  (If you have a different version of X2 - Studio, etc., then these steps will be a bit different, and if you post back with the exact version of X2 that you have I will update the instructions to match the version you tell me you have ).
 
1.  Open Windows Explorer or File Explorer (depending on Windows version), and navigate to wherever your Cakewalk Content folder is located.  By default, that will be in C:\Cakewalk Content.
2.  Save off any custom content you created in X2, such as project templates or track templates, drum maps.  These folders will be in the SONAR X2 Producer folder that you should see after completing the first step above.  NOTE, the removal process will also get rid of any custom key bindings and effects presets (for effects that came with Sonar), so you may need to backup that stuff too - though I do not have any info on that.
3.  Once you have saved off anything you want from above, delete the SONAR X2 Producer folder.
4.  Now, still in Windows/File Explorer, paste in: %appdata%\Cakewalk and hit Enter.  This will take you to a normally hidden folder for application data for Cakewalk, within which there is a SONAR X2 Producer folder - delete the SONAR X2 Producer folder, if present.
5.  Now, uninstall Sonar X2, through Control Panel>Uninstall Program.
6.  Now you need to delete a couple of Windows Registry keys for Sonar X2.  NOTE: it is recommended that you back up your Registry data prior to making manual changes to it.  To do so, run REGEDIT, which is the Registry Editor.  There is an Export option under File, where you can export all of your Registry data, to be recovered if you royally screw something up.
7.  After exporting your Registry data to save it off, delete the following 2 registry keys, if present:
 
 HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\X2 
 HKEY_LOCAL_MACHINE\Software\Cakewalk Music Software\SONAR Producer\X2    
 
The above steps will completely remove Sonar X2 Producer from your system, other than the saved custom content and backup exported Registry data.  
 
Now you can do your install of X2, making sure to this time around do so with the explicit Run As Administrator option set.
 
Bob Bone
 
 

Thank you very much for all the effort and trubble you going true to solve my problem, but I have a question. You now talk about X2 but don,t you mean X3?
Gr. Frits

Yes - I meant X3 - I DID go look at your first post, to see if a particular version had been specified, and my eyes saw the X2, but not the X3.  DOH.
 
Everything else is the same, just substitute X3 for X2.
 
IF you download maintenance for X3, I also recommend temporarily suspending your antivirus software during both its download and its install, and also recommend running any patch installation programs with Run As Administrator, as well.
 
I look forward to hearing back from you after you digest and apply all the stuff from above.  :)
 
Bob Bone
 

Brain farts for everybody!
 
I have had multiple cranial misfires today already, should be a GOOD day.  :)
 
Bob Bone
 

1.  No need to lose sleep over any of this - I certainly do not want you to.  And, I didn't mean to scare you or anything like that.  All I did was list the steps to cleanly remove an installed version of Sonar.  I have done this myself many times, over the years, and lots of other folks have too.  Nothing to be scared of - the steps are just like a recipe to follow - like you were making cookies.
2.  Free will gives us all the freedom to do as we choose.  You are only accountable to yourself - I am not disappointed in you - no reason to be.  I am not sure why you would think I might be.
3.  You could safely remove any particular installed Sonar version, and install it again, without need for doing anything with reloading the entire operating system.  If you choose to reload your entire computer, that is certainly your choice, but not required, as far as for anything I had written in earlier posts.
4.  IF you do choose to reload your entire computer, Sonar 8.5.3 will install just fine, with whatever version of whatever plugins it has, and even if some are no longer present in X2 or X3, those plugins will still be there because you installed them with 8.5.3 - I hope that makes sense.  For example, they replaced V-Vocal with Melodyne in X3.  My V-Vocal is still on my system, from an earlier release of Sonar, so it does not get deleted when I install X3.  It's just that X3 ships with Melodyne, so BOTH V-Vocal and Melodyne live side by side on my computer.  I hope that better explains it.
 
 
This is just a suggestion - why not take a good backup, and hold off on reloading your entire operating system for the moment, and just go through the steps to remove the current X2 you have installed now, following the steps I listed earlier?
 
Then, install X2 again, with Run As Administrator, and see if that fixes your Sonar issues.
 
You could then decide to either leave the operating system alone, or then choose to move to a solid-state primary drive as a separate issue, separate from Sonar.
 
Just a suggestion, 
 
Bob Bone
 

I will be online and available for the next couple of hours, and while I will be working on taxes, I will keep checking back to see if you have any posted problems or questions.
 
Bob Bone
 
 
 

I don,t think I can do this this weekend...first I have to make back ups. So I trie this in the next couple of days.

Just a couple of days ago I followed your instructions for deindtall and reinstall of X3.After trying out a couple of days it makes me verry happy to say that the program is running ok now and didn,t have any problems with the TTS1 anymore.To anyone who helped me ..thank you verry much
Greetings from Holland, Frits

Funny...  while I completely understand all the reasons why the Run As Admin option is needed - something I've recommended many times with the software I support at work  - I've never actually had to use it myself with SONAR!   I'm not sure why since I'm on a stock install of Win7 x64, but everything just seems to work.
 
Now with that said, I am looking forward to my first instance of needing Run As Admin in 5, 4, 3, 2...   
 
 

I swear I read on the Cakewalk site that it was no longer necessary to install as Admin. Of course I  just looked for this and could not find it.
 
Only thing I found was if you get this
Installation Error: DeleteFile Failed; code 5 Access Denied
Then run as Admin.
 
So I did not run as Admin when I ran the X3 install. I have had no issues whatsoever and I run as a user belonging to Administrators.
If your user account is part of the Administrator group you have elevated privileges anyway and if the installer encounters a permissions issue, the UAC warning should pop up and allow you to run whatever is complaining. Most people on a non-corporate PC do not run as a local user but as a member of the Admin group.
Normally installing a program as administrator is required if the program writes to folders where a local user may not have write permissions. It is also required if the program is to used by all local users on that pc.
 
Sometimes programs will install as another unique user just for that program. Perhaps some 3rd party plugins or synths do this and require running Sonar as Admin.  
 
One of my friends had an issue with the C runtime libraries during install but I think he declined the UAC popup.
 
Maybe one the bakers could chime in on this and give a definitive answer?
 
Michael
 

I thought that was the case, BUT there have been NUMEROUS instances with X1, X2, AND X3, where problems went away immediately after installing with Run As Administrator, and also often with launching Sonar with Run As Admin.
 
I understand the doc says it can, but reality begs to differ, as far as I can tell.
 
Bob Bone
 

Bob,
Yes I know there are privileges a member of admin does not have by default. System protected files and so forth. This is why you will sometimes get the UAC popup even if you are an admin (unless you disable the UAC notification).
There are also accounts with even higher privileges...e.g.  Trusted Installer and System. There are protected elements of the registry that NO user can modify without a special utility as well.
In the setup compiler I use (Inno setup) you can tell it to create the installer so that it will run as admin if there is something that needs admin privileges during install.
 
I would not be surprised that you would need to run Sonar as admin if you installed as admin. 
 
All I am saying is that Cakewalk said you don't need to install or run as admin, I did not and do not and everything works. I just would like to understand why some folks need to since I make my living designing hardware and writing code.
 
I am completely in agreement with you Bob, if necessary by all means run as admin. After all the point is to make music, yes?
 
Things like this are especially difficult to track down if you do not know the exact history of the PC in question.
I am still su****ious of 3rd party plugins/synths and perhaps installs of previous Sonar versions. 
 
Michael