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.

mettelus
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 PP, not SONAR.

so you just don't use kontakt? seems like ni contact is in order

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
 
 
 
 
 

Thanks for the plug, scook.  Now I HAVE to get the OP issues fixed.  :)
 
I completely agree with scook's advice - which would be to try to find a way to get X3 past these VST scan issues, and his approach is a good one - please for the moment, move the Kontakt 5 dll's to a different folder that is not going to end up getting referenced by the Sonar X3 VST scan, and then try to launch Sonar X3 and I would again at that point try doing an explicit Rest, followed by a full Scan.
 
It would be good to get you to where X3 can run, even if Kontakt 5 is temporarily not present, and then we can try to work out what sorts of things are going on with your system that would prevent Kontakt 5 from being scanned.
 
I DO have a question: you indicated that you did launch Kontakt 5 in stand-alone mode, and that it worked.  Is it possible you paunched a 32-bit version of it, rather than the 64-bit version of it (Kontakt 5)?
 
I am just grasping here - wondering if perhaps the 64-bit version needs to also be run in stand-alone mode, to complete its authorization process.
 
Might be worth a shot - double-check the properties of the Kontakt 5 and make sure it is running 64-bit in stand alone.
 
Bob Bone
 

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.

MR22b
Thanks for the reply,
 
I have tried a check disk and a full reset and rescan, I did it in my last version of Sonar so it didn't mess the new one up, and it's still exactly the same. />

Hi
 
Sorry I am confused about what your "last version of Sonar" means. You should do a reset and then the rescan at least in X3E (which you may have already done).
 
Thanks..

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.