Can't Load Updated Session Guitar Libraries

Kanoa · 2025-08-15T04:23:51+00:00

There was an error rendering this rich post.

I saw the news today that updates were available for all past Session Guitar Libraries, so I updated all available. Now Picked Acoustic, Electric Sunburst, Strummed Acoustic, Strummed Acoustic 2, Picked Nylon, Electric Vintage Guitars are not loading. Instead I get:

Your version of Kontakt is too old to load this file,

which was saved with Kontakt v8.4.0.000.

Please update to the latest version of Kontakt!

Is there a way or a link to go back and get previous versions of the above guitar libraries?

Find more posts tagged with

Strummed Acoustic

Kontakt 7

Kontakt 8

Comments

mykejb

They should be available to download from your user account here - https://www.native-instruments.com/en/account/downloads/

Always check the required version on library updates as Native Access offers you stuff that you might not be able to use !!

LostInFoundation

https://community.native-instruments.com/discussion/47220/cant-load-updated-session-guitar-libraries

You could also just update Kontakt, if you don’t have anything against it.

Or is it causing issues?

Kanoa

Thank you mykejb, I was able to go back to the previous version of the libraries and the files are all working for me again!

I did not know that Kontakt allows for updates to libraries that will not work within your current kontakt setup, now I know!

mattrixx

Yes, it's a bit strange. You need to look at therelease notes to get any sort of warning.

laradario

Hi,

I’ve run into a similar issue before. Sometimes the libraries don’t load because the paths in the software aren’t updated after an update. A few things that helped me:

Rescan the library folder in Kontakt or the Native Access app.
Check folder permissions to make sure the software can read/write the updated files.
Restart Native Access and your DAW after updating, just to make sure the changes take effect.

If that doesn’t work, sometimes reinstalling the specific library or repairing it via Native Access resolves the issue. Hope this helps!

Quick links

Unanswered questions