why is kontakt missing the GUI and playing no sound after relocating content?

hi all. i relocated all my content to a new external ssd and then repaired everything via NA, then batch resaved.

when i opened a project / session in logic im working on a lot of the kontakt instances looked like this and didnt play any sound.

i tried deleting the .db3 files and library cache files in application support but it didnt help.

any ideas why this happens and how to fix it?

Screenshot 2026-01-15 at 12.54.46 (2).png

Find more posts tagged with

Native Access 2

Kontakt 8

Accepted answers

All comments

PoorFellow

https://community.native-instruments.com/discussion/49685/why-is-kontakt-missing-the-gui-and-playing-no-sound-after-relocating-content

Most pertinent question would be does that also happen if you make a new project from scratch ?

Be sure to be using latest version of Native Access for your OS .

Else then check the ALL NI apps including NTKDaemon and DAW must have full disk access. : How to Enable Full Disk Access on macOS

And when using Sequoia then N.I. apps and DAW must be added to the Local Network (Ref.: How to grant audio apps access to your local network on macOS 15 Sequoia)

mykejb

The first thing check is to run Kontakt standalone and see if the same problem occurs. If that works ok then move onto a new Logic project to see what happens there.

Is it just some of the instances that don't load correctly or all of them. If it's just some that don't load do they have anything in common?

apricotandpearjam

hi all, thanks for replying.

it seems that the issue is just for player instruments / custom imported content / libraries which aren't licensed and downloaded via NA.

if i load those patches again whether in logic or kontakt standalone they open fine.

its just for patches that were loaded into a project before i moved the content.

what ive observed is that if i try and point to a folder or file for one of the missing libraries kontakt searches and searches and cant find anything, even when its directed to the correct folder.

i think its a bug with the way kontakt is 'looking for' or 'sees' the missing files and GUI elements.

HERE are 3 screen recordings showing that kontakt cant find the files, me loading them fine in a separate instance and what the GUI issue looks like.

ive reported it but in the meantime does anyone know of a fix?

Vocalpoint

https://community.native-instruments.com/discussion/comment/254237#Comment_254237

"its just for patches that were loaded into a project before i moved the content."

Clearly something in your session/patches/metadata/something was saved with "pathing" in the old sessions and now - after the move - this message is totally logical. It is looking to some outdated info and not finding it.

What or where this stale data might be stored in a Logic project file is beyond me (not a user) - but something is telling Logic to look in the wrong place.

apricotandpearjam

thanks for your reply.

i can’t see how logic would be the reason for this

surely kontakt is unable to relink the data.

one of the videos i posted show me trying to relink the aaron venture infinite brass and you can see that kontakt cannot see the missing data.

PoorFellow

https://community.native-instruments.com/discussion/comment/254237#Comment_254237

it seems that the issue is just for player instruments / custom imported content / libraries which aren't licensed and downloaded via NA.

if i load those patches again whether in logic or kontakt standalone they open fine.

its just for patches that were loaded into a project before i moved the content.

what ive observed is that if i try and point to a folder or file for one of the missing libraries kontakt searches and searches and cant find anything, even when its directed to the correct folder.

i think its a bug with the way kontakt is 'looking for' or 'sees' the missing files and GUI elements.

i tried deleting the .db3 files and library cache files in application support but it didnt help.

Personally then I do not think that it is a real bug as such in Kontakt.

This sounds to me as something being moved while not being properly redirected all over the board (Kontakt or DAW) and as if something takes precedence over the other.

I don't know enough about Kontakt and it's registering information , but this makes me think of pages like this. (How to Add Non-Player Libraries to Kontakt 7/8's Browser) How are all of this third party "not N.A. libraries" registered in Kontakt ? I don't know if there is something to re-scan or re-save or whatever , or if this is a matter of DAW info vs Kontakt info

I think that I will have to ask an 'expert' (🙂) : @Jeremy_NI , does any of this help you get an idea that could help ?

Vocalpoint

https://community.native-instruments.com/discussion/comment/254259#Comment_254259

Also noticed that you do favor a lot of Batch Resaving as well?

That will for sure hard stamp paths INTO the actual Kontakt *.nki and related files.

And then if you move an instrument after this process - failure is guaranteed.

apricotandpearjam

batch resaving makes no difference.

the issue has to be with the way kontakt is coded to find missing files from custom imported content.

has to be a bug.

@Jeremy_NI ?

Vocalpoint

https://community.native-instruments.com/discussion/comment/254302#Comment_254302

You should take a moment to watch this:

Kontakt's Batch Resave Explained

Specifically the :42 - :45 second mark….

And then watch what happens at the 1:22 - 1:25 mark.

Jeremy_NI

@apricotandpearjam Sorry if I missed the information here but these blurry graphics can appear when a wrong audio driver is selected in the Kontakt standalone application. Also double check full disk access for Kontakt and your DAW.

Can you check what driver is selected there? Is it a Coreaudio driver? Just to be sure, from the description and the investigation you did already I doubt this would be at play here.

If that has no effect, I'll get in touch with you by email to make a proper bug report, I'll ask you a small project where you can recreate the issue, including one of these custom imprted instruments so we can try a repro.

Quick links

Unanswered questions