Kontakt won't open as standalone not on a Cubase

Captain_N

Hi there, I have a major issue that Kontakt won't even start, not as a standalone and not in Cubase. It quotes a 'Kernelbase' problem when opened in Cubase 13. I just did a full re-set to my computer so both software are new installations from today. Yet it won't work. Please advise ASAp.

kontakt crash.png

Screenshot 2024-05-13 201749.png

Jeremy_NI

Have you tried these steps? Kontakt Crashes

PoorFellow

https://community.native-instruments.com/discussion/30691/kontakt-wont-open-as-standalone-not-on-a-cubase

What is your Kontakt version ? and what is the installation path for Kontakt app and Kontakt plugin/NI plugins ?

And what is your computer type and OS version (PC and Windows 11 is suggested by your profile) ?

Captain_N

Thank you for your help! I've tried all the Kontakt Crashes 'solutions' as the article suggested, but nothing helps. It still crashes even when it's Kontakt as a standalone. I haven't even logged any plug-ins / 3rd party libraries, it just crashes when it starts up - the same thing in Cubase when opened as an instrument. This is Kontakt 6. Do you think Kontakt 7 will remedy this? I'm using PC and Windows 11 - the latest update was yesterday (as part of the Kontakt Crashes suggestions, I did the latest update to Windows).

PoorFellow

https://community.native-instruments.com/discussion/comment/153918#Comment_153918

What you are experiencing to me appear as a bit unusual.

And the screenshots placed indicates some enhanced use of 'One drive' , are you sure that you have not setup it all in a way that will somehow block for the functionality of the apps ? (N.I: and Steinberg)

And what is the installation path for Kontakt app and Kontakt plugin/NI plugins ?

Jeremy_NI

@PoorFellow Well spotted!

@Captain_N Kontakt, and other music applications do not sit well with not physical drives, please use a hardware drive and do not sync folders used for Kontakt to a cloud service.

Captain_N

Hey guys. Thanks for the thought, but it's actually stored on a hard tive in the composer (SSD actually). Only the crash log is posted into that 'One Drive' thing, but even the 'One Drive' is on the c drive (SSD). I checked the installation path and location, the application is installed on the C drive SSD. I uninstalled and re-installed Kontakt serveral times both on the C drive and the D Drive (also SSD) to try out and see if it was a drive issue: it is not. It still crashes upon opening the application, whether as a Standalone or Cubase. Any further thoughts?

PoorFellow

https://community.native-instruments.com/discussion/comment/154805#Comment_154805

Sorry , all I can suggest is that you contact N.I. Kontakt Support

Jeremy_NI

@Captain_N OneDrive is not a real drive but it can be synced to physical drives and that's where the problem can be, my colleagues should be able to help you out.

Captain_N

Hey there, thanks for your help and suggestions. I formatted the entire computer (C /system drive initialized entirely). I re-installed Native Instruments and Kontakt 6.8.0, but the same problem still occurs. I followed all the 'KONTAKT CRASHES' potential solutions, and nothing again made it work; the same message appeared again.

I then removed Kontakt and re-installed it making sure that the files don't go remotely close to that 'One Drive' thing - the Download Location is now D: Native Instruments Libraries Download, Application Location- C: Program Files/Native Instruments, Content-Location is at D: Native Instruments Content-Location, VST locations 32 and 64 are at the default - C:/Program FDiles/Native Instruments/VSTPlugins 32 Bit and C:/Program FDiles/Native Instruments/VSTPlugins 64 Bit.

It still doesn't work, - so this shows that the 'One Drive' - isn't the issue- only the log dmp file seems to go there, but no part of Kontakt is installed there

Windows 11 is up to date. I tried again with the 'Kontakt Crashes' steps, but nothing helped. Will submit a ticket to the support and report back.

Thanks again for trying to help out!

Jeremy_NI

@Captain_N As we said already, please get in touch with our dedicated support.