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
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

thanks for the info
I had been choosing the compatibility tab - it has a box for run as administrator there also. But it says - privilege level. I see now the advanced is a different box. Should both boxes be selected or just the advanced?

I'm wondering if the complete uninstall will have any effect on the VST scan, since that's used by all the programs I have installed, like 8.5 and X1. It may keep it intact and be a waste of effort. Just wondering

X3's plugin manager REPLACED what had been there before, so if there is a problem with it, a complete removal of X3, as described above, followed by a clean install of X3, per above as well, will put a new copy of it in place.
 
Bob Bone
 

robert_e_bone
X3's plugin manager REPLACED what had been there before, so if there is a problem with it, a complete removal of X3, as described above, followed by a clean install of X3, per above as well, will put a new copy of it in place.
 
Bob Bone
 

Unfortunately the clean instal didn't help at all. VST scan crashes on Vsampler and under preferences VST settings the check boxes for scan failed pluggins and scan existing pluggins are greyed out. Even though Vsampler has been uninstalled. It apparently is only looking in the registry and not what's actually on the C drive. In the other post about the VST scan crash, I list the crucial registry spots where Vsampler is showing up and it's not in the X3 keys like I deleted for the clean install. There are keys for the VST folder that show Vsampler there even though I manually deleted it.
 
It seems to me that I need some guidance on what keys are safe to delete in the registry or how I can uninstall VST scan and then reinstall it. I really don't think reset is working correctly. IN the past I noticed several popup boxes that came up during the reset procedure, none of those happen now.

A number of people on this thread have said using 64 bit will fix a lot of gremlins.  I'm running 64 bit and having a huge amount of problems.  IMO the belief that running 64 bit will fix the problems is completely incorrect.  Different problems maybe, but less?  Well i'm presently trying to figure out why x3 has basically stopped working completely.  As is this guy .  

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
 

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
 

You've been very helpful, Bob and I apologize for the complexity of this being spread over 3 posts. But yes I've found all sorts of Vsampler items in the registry that weren't removed by the clean install instructions you gave me. Check out this post, which condenses a lot of what I've done and discovered
http://forum.cakewalk.com/VST-scan-not-resetting-Can-it-be-manually-reset-m3028540.aspx#3028540
 
After getting no response to my 3rd post in this saga. I went ahead and emailed tech support. It seems to me that all this can be fixed with clearing the VST scan registry data and any other VST scan data in files to effectively uninstall and reinstall it.
 
In the mean time I went back to the image file I did right after resolving the VST scan problem which has the Win updates. I had 2 crashes during the first day with this image, but it's possible those 2 crashes were the result of Win Media Player being 64 bit and X3 being 32 bit and my sound card getting confused, like you pointed out.
 
Thank you for giving me the very helpful suggestion of using Win Media Player and Control Panel / sounds to my on board sound driver, which has worked great and for the last 2 days I've not had a crash, so far. THis latest saga of me uninstalling and reinstalling X3 was because I was leary of those 2 crashes I had were because my initial installation of X3 was unstable without those updates.
 
So let's see if I get any more crashes. It's too early to tell, since monday and tuesday weren't that busy. I'll also wait to hear from tech support, because I would really like to know the procedure for fixing VST scan and I feel better doing a clean install of X3 on a fully updated machine.
 
 

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.

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.

I guess the real question is does it do any harm running it and installing it using the "run as administrator " option? Has anyone from Cakewalk discouraged it?