Oh yeah, the installer only knows what it has built and whatever gets done manually to a hard drive will never automatically be reflected in the registry.
 
One thing I find strange about those entries, they look like 64bit version of SONAR entries. Notice the "Cakewalk VST X64" in one of them and "BitBridge" in two of them. These are not part of a 32bit installation. I though this was a 32bit X3 install.

scook
Oh yeah, the installer only knows what it has built and whatever gets done manually to a hard drive will never automatically be reflected in the registry.
 
One thing I find strange about those entries, they look like 64bit version of SONAR entries. Notice the "Cakewalk VST X64" in one of them and "BitBridge" in two of them. These are not part of a 32bit installation. I though this was a 32bit X3 install.

A few years ago when I installed X1, I did dabble with 64 bit X1 and 64 bit 8.5, so they're still installed

Is there a possibility that all these mixed versions have driven the registry insane?

Anderton
Is there a possibility that all these mixed versions have driven the registry insane?

What's strange is that my first installation of X3 with all these mixed versions was fine after I uninstalled Vsampler and hit vst reset, but now since I did all my Win updates, video card updates, and motherboard updates, uninstalled and reinstalled X3, the VST scanner has gone haywire.
 
Any more suggestions?

I don't know what to say at this point. That's a lot of updates to happen all at once...even under the best of circumstances Windows strikes me as a bit of a house of cards. At this point it's probably Cakewalk tech support time if scook doesn't have a solution.

No, I don't. There have been at least three pretty lengthy threads on this case. The initial scanning issues (forgot about that one) which was resolved (or so I thought) only to be followed up with a general X3 stability thread and now after a wholesale machine update and re-install the scanner has gone south. At least, that is what I believe is the story.
 
Yeah, we could go through a few more cycles of tear down and rebuild with a few registry cleanups on the side but this is when a phone call (or two or three) to tech support may provide the most direct solution. I would point the support staff the the volumes that have documented in these threads. Hopefully they can sort it out.

 
Unfortunately the clean install deleting registry keys 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. Vsampler also shows up in pluggin manager as an excluded pluggin.
 
Here are the registry keys below I'd think would get rid of the problem. Note also that even though I manually deleted Vsampler.dll from cakewalk/vstplugins, it still shows up in the registry.

HKEY_CURRENT_USER\Software\Cakewalk Music Software\ExcludedPlugIns

HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST X64\Inventory\c:/program files (x86)/cakewalk/vstplugins/VSampler3.dll

HKEY_CURRENT_USER\Software\FX-MAX\BitBridge\VoLEffect\c:\program files (x86)\cakewalk\vstplugins\VSampler3.dll

HKEY_USERS\S-1-5-21-3235901495-1408207914-819435497-1004\Software\FX-MAX\BitBridge\VoLEffect\c:\program files (x86)\cakewalk\vstplugins\VSampler3.dll
 
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.

Gerry,
I'm thinking you have to get back to an image made BEFORE your Windows update AND the original install of X3.
In reviewing your "Event Viewer" data the VSTscan.exe is v5.0.6.352.
v5.0.3.0 is what I have for X2. My guess is that the uninstall of X3 left the newer version of vstscan in place.
I've rolled my office system back to when it was working properly with X2.
My "problem" projects seem to be only ones that were started on the office machine and moved out to the studio.
AND started AFTER the most recent rounds of Windows Updates.
I know this heresy flies in the face of "keep your system up to date" but I've been "leary" of MS updates for ages.
Goes back to XP, maybe Win98se.
I'm kind of an "If it ain't broke" guy.
HTH; with the caveat that I am no expert.
T

DeeringAmps
Gerry,
I'm thinking you have to get back to an image made BEFORE your Windows update AND the original install of X3.
In reviewing your "Event Viewer" data the VSTscan.exe is v5.0.6.352.
v5.0.3.0 is what I have for X2. My guess is that the uninstall of X3 left the newer version of vstscan in place.
I've rolled my office system back to when it was working properly with X2.
My "problem" projects seem to be only ones that were started on the office machine and moved out to the studio.
AND started AFTER the most recent rounds of Windows Updates.
I know this heresy flies in the face of "keep your system up to date" but I've been "leary" of MS updates for ages.
Goes back to XP, maybe Win98se.
I'm kind of an "If it ain't broke" guy.
HTH; with the caveat that I am no expert.
T

Yes Tom, I've definitely thought about going back to the pre X3 image, which is the pre Win update image. What I'd try to do is uninstall Vsampler first, do the Win updates, then install X3 and hope Vsampler reacts ok with the reset and rescan. During my very first X3 install, Vsampler was installed, VST scan crashed on Vsampler, I uninstalled it and hit reset rescan and all was well.
 
After getting no response to my 3rd post in this saga:
VST scan not resetting - Can it be manually reset?
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.
 
Bob Bone gave 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.
 
I've been leary of Win Updates also and never use auto updates, I only do them whenever I think I need them. I noticed Cakewalk recommends doing all the updates including the optional ones. that makes better sense to me, because I've always wondered about whether to do the optional ones.
 
I guess if everyone is doing that then the programmers can be better prepared for problems with the updates and make changes. So I think I'm going to be more on top of the updates, but keep doing image files before I do any. I'm also an "If it ain't broke" guy.

All the VST reset does is clear the registry key that holds the inventory.

If this were my issue I would be on the phone to tech support. Anything that can be accomplished by email/text have already been explored in the various (duplicated!) threads on this issue.