3.5.0 hangs no matter what plugin it is

TeeJay2075
TeeJay2075 Member Posts: 4 Newcomer
in Komplete Kontrol
Komplete Kontrol.log.zip

I have this problem where Komplete Kontrol Software hangs on opening while scaning plugins I have tried all the suggestions on the community and still does not work it hapens both on standalone and in daw as plugin

Tagged:

Answers

  • Jeremy_NI
    Jeremy_NI Administrator, Customer Care Posts: 14,752 admin

    @TeeJay2075 It looks like this scan log points at some things being scanned that are definitely not audio plugins. Please check your VST2 and VST3 folders for any dll files that are not audio plug-ins.

  • JesterMgee
    JesterMgee Member Posts: 3,316 Expert

    Post a screenshot of your Preferences > Plugins > Locations screen

  • kloanman
    kloanman Member Posts: 7 Newcomer

    Hi all, I'm having the same issue, just updated to 15 and not really used Komplete Kontrol for a while after moving and just now resetting everything up.

    It starts up and scans all plugins,,, gets to last plugin scans that one and just hangs there.

    tried uninstalling and deleting the KK folder in the app data local folder, then re installed and tried again but did exactly the same just hangs. I have my S61 mk2 keyboard setup and just shows the the midi dims on the screen nothing else.

  • kloanman
    kloanman Member Posts: 7 Newcomer

    Have seem some people are downloading and running a previous version of 3.2.1 who are having the same issues.

    Is that the best temporary fix for the minute ? I'm currently running 3.5 and having no joy with it loading.?

    loaded up maschine 3 with no issues?

    As the program isn't loading I can not get into preferences Jason to find the plugin in locations, will they not be default after a fresh install ?

  • Jeremy_NI
    Jeremy_NI Administrator, Customer Care Posts: 14,752 admin
    edited June 18

    @kloanman Just replied to the other thread you created with the same object.

  • JesterMgee
    JesterMgee Member Posts: 3,316 Expert
    edited 12:02AM
    https://community.native-instruments.com/discussion/comment/231082#Comment_231082

    On a default install yeah should be default unless you have installed KK at all in the past or even updated (which you do say you updated in another thread), the settings are carried over so unless it is stated this is a brand new install it is not known if this is the case so any information to clarify is always welcome. However, it will point out exactly what locations are set even as default so you can then simply focus in those locations. Just FYI, in your other thread with a log it shows non default locations being scanned:

    C:\Program Files\VstPlugins\
    C:\Program Files\Steinberg\VSTPlugins\

    also the 32bit location which is no longer supported by KK and should be removed (I think KK ads this by default but I always remove everything except the VST3 path and my main VST2 path):

    C:\Program Files\Native Instruments\VSTPlugins 32 bit\A

    You do have a few plugins failing the scan which could mean these are problematic so may be an idea to check these and update them:

    Scanning plugin AVOX CHOIR failed with result code -1073740791, error code { .value = 0, .category = system, .message = The operation completed successfully } and message ""
    Scanning plugin Ultra Analog VA-2 failed with result code -1073741819, error code { .value = 0, .category = system, .message = The operation completed successfully } and message ""
    Scanning plugin     Solina failed with result code -1073741510, error code { .value = 0, .category = system, .message = The operation completed successfully } and message "*** Queue destroyed without being stopped ***
    [ERROR] Scanning of plugin C:\Program Files\Common Files\VST3\    WaveShell1-VST3 15.0_x64.vst3 with name failed because not valid information could be obtained
    [ERROR] Scanning of plugin C:\Program Files\Orion\VSTPlugins\    DUNE 2.dll with name failed because not valid information could be obtained

    On the previous v2 of KK you could press the ESC key when the loading splash screen displays to cancel the scanning and go straight into the KK software. Not sure if this is still possible in the latest v3 KK (should be if it was designed by someone with sanity) but was an important function to allow easy changes to the scanning paths in the case where a user has multiple locations where VSTs are, more applicable back when VST2 was a thing and people had a mess of plugins scattered around their system. If you can bypass the initial scan then you can go into the plugin locations tab and select one location and click rescan to try and rescan again from within the software.

    The request for that screenshot was for the OP and Jeremy's note that in that case it seemed to be hanging on files not related to VST's at all and I have seen some silly things over the years such as people just setting their c:\ drive as a VST location so KK has to scan every .dll file on your system which is ultimately going to cause a problem.

    However I have seen far more reports of this issue just in the last few months than I have for years before so it seems more an issue with how the plugin scanner works these days which is why I just cannot use KK V3, have never had an issue with KK V2 in this regard and I have well over 600 plugins over VST2 and VST3 without a single scan issue

Back To Top

Categories