robert_e_bone
@GMP - if you still have issues, then I think some closer examination of your download/installation/system is in order.
 
It might be something like Windows maintenance not being up to data prior to doing the Sonar X3 install.  Perhaps antivirus software was running during download and/or install and interfered with things.  Possibly want to try a complete removal of the current install of X3 and do it again with Run As Administrator.  Do these issues occur with all projects in X3, opening of older projects in X3, with particular plugins present, or perhaps with no plugins present?
 
Do the original download files have hash values that match the published hash values from the Sonar install page from the web site?
 
Lots of stuff to look at.  The fact that not so many folks report these kinds of issues suggests it is something unique to your system, or download, or install, or 3rd-party plugins.
 
Bob Bone
 

robert_e_bone
Aah - by 'hash values', I was referring to a set of data that helps to identify whether or not files that you download were corrupted during the download or not.
 
Cakewalk generated and published the 'hash values' for each of the several download files that comprise whatever version of Sonar you downloaded.  The importance of the Hash Values is that you can then use any one of a zillion freeware Hash Value generator programs to generate Hash values for the Sonar download install files, and then you can compare your hash values against the ones that Cakewalk generated for the same files.  If they match, then your download files are all intact - with no corruption.  If they don't match, then you know that somehow one or more of the downloaded files was corrupted during the download, and you will have to download them again.
 
Here is the link to the Sonar installation instructions web page: 
 
http://www.cakewalk.com/support/kb/pages/x3_download_installation_instructions.aspx
 
At the bottom of the above page, there are links to pages that display information on the exact breakdown of the download files for whichever flavor of Sonar you downloaded.  Part of that information on those pages are MD5 Hash Values for each of the download files for the version you downloaded (X3, Studio, Producer).
 
So, go to the above link, then click on the appropriate details page for the version you downloaded, and write down those MD5 Hash Values.
 
Then, go download one of the free Hash Value Generator applications that are on the web, and generate Hash Values for the files YOU downloaded.
 
Then, compare the hash value you generated for the 1st download file against the Sonar web page's Hash Value for the 1st download file and make sure they match.  repeat this for each of the download files, and then please post back on whether or not everything matches up OK, or if there is a problem.
 
Here is a link to a freeware Hash Value Generator app you can use to generate Hash Tag Values for your downloaded files - to compare against the Cakewalk published ones:
 
http://www.winmd5.com/
 
Bob Bone
 

robert_e_bone
Well, perhaps a COMPLETE removal of X3 and a clean install of it might fix your scan problems.
 
To completely remove X3, let's say producer version:
 
1.  Use Control Panel and uninstall Sonar X3 Producer
2.  Navigate to C:\ProgramData\Cakewalk and if present, delete the SONAR X3 Producer folder
3.  Navigate to %appdata%\Cakewalk, and delete SONAR X3 Producer, if present
4.  Start REGEDIT.
5.  Expand: Computer\HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer, and delete X3 key (and its sub-keys)
6.  Expand: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\SONAR Producer, and delete X3 key (and its sub-keys)
 
PLEASE NOTE that it is recommended that you Export your Registry PRIOR to deleting the above keys, in case you need to recover them due to any mistakes you happen to make.
 
OK, so after doing all the above, Sonar X3 Producer Edition will be completely removed from your computer, and you can now install it again (known as a 'clean install).
 
THIS time, I would suggest you temporarily suspend/disable your antivirus software, just prior to launching the Sonar install.
 
In addition, I always also right-click on the Sonar installer program and click on Run As Administrator.  While there may be no need for it, I still always do it this way, and needed or not, I never have any install problems, so I just choose to do it this way.
 
FURTHER NOTE - PRIOR to deleting the SONAR X3 Producer folders above, you might want to save any custom content you created, such as custom project templates, drum maps, and that sort of thing, just in case.
 
I also always RUN Sonar with it permanently set to Run As Administrator, again it might not be needed for Sonar itself, but some plugins work better with this option set.  To set this - right-click on the Sonar program launch icon, then click on Properties, click on Advanced, then check Run As Administrator, then OK, then Apply.
 
After installation is complete, you can restart your antivirus software.
 
I hope that helps, 
 
Bob Bone

robert_e_bone
I would like to better understand the leftover pieces of the VSAMPLER that you had removed.
 
Can you please detail what pieces of it were left behind, after your uninstall?
 
If you run REGEDIT, you can search for VSAMPLER without disturbing anything (it will not delete/modify anything by itself, it is just a search).  Please do search for it and list the keys that are still in your system that are still there.
 
Also, you are SURE that VSAMPLER is no longer present in any folder in the search path that Sonar uses?
 
Thanks for hanging in there - I am sorry if any of my questions were addressed earlier - I am just trying to make sure I understand the situation as completely as possible.
 
Bob Bone
 

mrdrwest
What does your project consist of?
 
Please stop installing applications as administrator unless prompted for elevated privileges: Note, some plugins may require admin privileges to complete installation, but not to run afterwards.
 
Sonar X3 does not require admin privileges to run, unless you have a poorly written plugin(s) that requires it.