X3 VST Scan Stops on Kontakt 5

Hi,
 
I have updated my Kontakt 5 and now when it X3 scans it stops on any Kontakt 5.Dll, even when I uninstalled the updated and went back to the old one it is still stuck on it and won't add the plugin in sonar.
 
I am using X3e on Windows 7 SP1 64 bit
 
Any help would be appreciated,
 
Martin
 

Try running Kontakt in standalone modus first.
 
 
Best,
Klaus

Try...

Running chkdsk on your harddrive.
Also in Sonar do a vst RESET (not just a rescan).

Cheers..

you have duplicates of the kontakt 5 DLLs - all the items with (2) in the name - i'd try removing them before rescanning
hth

It can take quite a while to scan the Kontakt dlls. Even minutes. Perhaps you need to wait for the scan to finish

Then there's obviously a problem.

Thanks, also to note, any Kontakt.DLL file that is in VST folder it seems to hangg on, even if it's my old version which used to work fine, have tried isolatingeach one in the folder on it's own and it hangs on anything to do with Kontakt,
 
Thanks for your help.
 
 

I have seperate installations of sonar on the System so I know it isn't that, Have tried it in X2 and X3.
 
It will run fine as long as I switch off VST Scan, but it just means next time I add plug ins and it goes to scan them it will hang and then remove them

To the best of my recollection, The X3 Cakewalk Plug-In Manager version replaced the X2 version, so once you installed X3, both X2 and X3 began using the same version of the Plug-In Manager.  
 
I am mentioning this because of your comment about having separate installations of Sonar (X2 and X3).  BOTH of those versions now reference the same Plug-In Manager version.
 
Many times, when a plug-in hangs in a VST scan, it is due to that plugin having some kind of error condition - such as not being fully licensed or something like that.  The scanning process queries each plugin, to get back information reported by each plugin, and if a particular plugin issues some kind of unexpected response to the plugin manager, then the plugin manager may well not have a clue as to how to proceed, and it hangs.
 
I cannot tell you that the above is definitive, it is just one possibility.
 
1.  After you got rid of the duplicate dll versions of Kontakt 5, did you do a full RESET and RESCAN?  I was not sure of when you had done this, (was the reset done prior to getting rid of duplicates or after).
 
2.  The condition you are experiencing is certainly something unique to your computer, because there are large numbers of folks, myself included, that use Kontakt 5 within Sonar, and if there was any kind of wide-spread problems like what you are experiencing, many more folks would have posted as such to this forum.  This is actually good news, as it is then something that should be able to be ferreted out and resolved.
 
3.  I am a little confused as to how you came to have the duplicate dll's for Kontakt.  It almost seems like you manually moved things around in your computer.  Please explain, so I better understand how that condition came to be.
 
4.  Is it possible that Kontakt was excluded in the scan?  There is a button to click to show excluded plugins, and I believe if a plugin has been excluded there is some sort of indication there as to why it was excluded.
 
Bob Bone
 
 
 

robert_e_bone
To the best of my recollection, The X3 Cakewalk Plug-In Manager version replaced the X2 version, so once you installed X3, both X2 and X3 began using the same version of the Plug-In Manager.  
 

This is correct. All 32bit installs share a 32bit version of vstscan.exe and all 64bit share a 64bit version of vstscan.exe The same is true about the VST inventory in the registry. The same is true with the Plug-in Manager but this is really an issue about the VST scanner. The Plug-in Manager is a separate tool.

I have never seen this in SONAR, but know this occurs inside Adobe Premiere Pro (identical to the issues stated here). To resolve this in PP, you do in fact need to make a VST blacklist file, and NI products are the most likely ones to be put there. Those three dlls are in my blacklist file but because of Premiere Pro, not SONAR.
 
Here is a link to that post I made previously. Again, I reiterate this is not an issue within SONAR.

Thank you for all the replies,
 
1.  After you got rid of the duplicate dll versions of Kontakt 5, did you do a full RESET and RESCAN?  I was not sure of when you had done this, (was the reset done prior to getting rid of duplicates or after).
 
I have tried getting rid of them and then scanning.
 
3.  I am a little confused as to how you came to have the duplicate dll's for Kontakt.  It almost seems like you manually moved things around in your computer.  Please explain, so I better understand how that condition came to be.
 
To be honest I'm not exactly sure but I had loads of problems years ago with Kontakt in 64bit and I remember moving DLL's around then, this was a long time ago though and it's always run fine with those in.
 
I don't think it's excluding Kontakt as it scans loads of plugins and only stops when it arrives at that one.
 
Is there a way of simply telling Sonar to not bother scanning Kontakt at all? As without scanning the plug in is there and works fine, it's only when scanning that Sonar removes them all. So if I could bypass the scan it would all be fine.
 
Thanks again
 
 
 
 
 

any time Bob
I have resorted to moving unruly plug-ins out of the scan path before, only to add them back in after a scan completed. After adding them back they were picked up and everything worked. Does not happen often but it has happened before.

Uninstall Kontakt and remove all dlls.  Also download Windows Install Clean Up utility.   There reason why those dlls are there they were either moved or they were not over written by the NI installer.
 I often have problems with the recent NI installers.  Often I get an update failed and have to use the Window Install utility.