The Windows updates are really important, as software relies on particular things to be present in order to work properly.
 
Please apply all outstanding Windows updates, and keep your system current.
 
Bob Bone
 

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

If the VST reset  clears the registry keys that holds the inventory, then why it it not clearing the Vsampler out of the registry in the Cakewalk VST folder? This is my point, I really don't think reset is working right and as of now no one from Cakewalk has responded to any of these posts.

From what I recall, the only VSampler entries are from an ancient 64bit install. I am assuming this machine is currently running 32bit SONAR. A 32bit installation uses a different part of the the registry. Nothing in a 32bit installation will touch the SONAR 64bit portion of the registry. IOW 32bit VST reset does not clear the 64bit VST Inventory in the registry.

scook
From what I recall, the only VSampler entries are from an ancient 64bit install. I am assuming this machine is currently running 32bit SONAR. A 32bit installation uses a different part of the the registry. Nothing in a 32bit installation will touch the SONAR 64bit portion of the registry. IOW 32bit VST reset does not clear the 64bit VST Inventory in the registry.

I see what you're saying.  You're right I have an ancient 64 bit 8.5 + 8.0 intact. The references to Vsampler in the registry that I thought looked very suspect that reset is not working are these below. As you can see they are (x86), but on closer examination there's references to BitBridge, which 32 bit Sonar doesn't use and Cakewalk VST X64\Inventory.  So what do you think?
 
Instructions for a total removal of X3 only involve removing the keys named X3, not the ones below. 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\VSampler3.dll

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

These entries are all related to 64bit installations, see post #21
 
These entries are shared with all 64bit versions installed so would not be part of cleaning up a specific version of SONAR.
 
Manually deleting data from the hard drive does not affect the registry also post #21
 
To make these entries go away either manually delete them from the registry or run a 64bit VST reset and rescan. This is not going to do anything for 32bit SONAR because 32bit SONAR is not aware these registry entries exist.
 

scook
These entries are all related to 64bit installations, see post #21
 
These entries are shared with all 64bit versions installed so would not be part of cleaning up a specific version of SONAR.
 
Manually deleting data from the hard drive does not affect the registry also post #21
 
To make these entries go away either manually delete them from the registry or run a 64bit VST reset and rescan. This is not going to do anything for 32bit SONAR because 32bit SONAR is not aware these registry entries exist.
 

good point. It just deepens the mystery of why is VST scan crashing on a non-existant pluggin - Vsampler? I have a dual boot Win 7 computer, so I just did another search on that HD where VST scan in X3 is misbehaving and there are no files named vsampler, so VST scan is either getting that pluggin name from deep within a file or the registry.
 
There were actually more registry entries with Vsampler, but I thought those were the likely ones that VST scan was crashing on. It's possible I missed the real culprit. It'll be interesting to see what tech support says. I'll update this thread when this gets solved.
 
Thanks for your interest and excellent help,

Did a cake person chip in yet?

lawp
Did a cake person chip in yet?

Not on any of my related 3 posts, but I finally sent this to tech support about 24 hours ago. They said it's usually within 2 days and I saw a Cake Tech here say they've been swamped. So in the mean time I'm using a previous install that so far is working since I'm using onboard sound for Win Media etc.

I just did a remote session with support yesterday. They could not get the VST reset (in X3e) to clear the registry so they had to delete the Inventory key from within regedit. The Inventory key was then rebuilt after X3e did a full scan.
 
Not suggesting that anyone just do this unless they are totally comfortable and have an backup image or at least export a copy of the registry. I still have issues here with plugs not registering and have been working for several hours on it. The VST reset on my machine seems inconsistent as sometimes it works and sometimes it don't...

rtucker55
I just did a remote session with support yesterday. They could not get the VST reset (in X3e) to clear the registry so they had to delete the Inventory key from within regedit. The Inventory key was then rebuilt after X3e did a full scan.
 
Not suggesting that anyone just do this unless they are totally comfortable and have an backup image or at least export a copy of the registry. I still have issues here with plugs not registering and have been working for several hours on it. The VST reset on my machine seems inconsistent as sometimes it works and sometimes it don't...

 
Man that sounds exactly like what I need to do, because mine clearly is not resetting. But I agree I should wait until tech support instructs me. I saw the inventory key for 64 bit, but if I found the one for 32 bit, I didn't copy and paste it into my post. I'm glad they're on top of a solution for this. T
 
hanks for your post it's clear that VST scan has some bugs and they're aware of them. I bet the next update has this fixed. By the way are you running X3 as 32 bit also? I plan on going to 64 bit in the near future, but I want to first get 32 bit solid.