Installation failed: Invalid location.

Ralf Rottmann · 2023-11-11T22:02:46+00:00

There was an error rendering this rich post.

Running Native Access 3.7.0 on latest mac OS (14.0).

Installing newly purchased Sounds works fine.

Updating ANY of the existing ones (57 updates pending) yields a: "Installation failed: Invalid location." error.

I have previously chosen a new Content Location and the new products get installed exactly there. However, when trying to Repair -- Reinstall ANY of the previously existing one, Native Access comes up with the above error. I've checked System Preferences and given Full Disk Access to Native Access and all of its required daemons.

Any ideas? (Option to Uninstall existing packages is greyed out.)

Find more posts tagged with

Accepted answers

J3uddha

I fixed my issue by deleting the .plist files for my missing libraries. On a mac, you can find them in Macintosh HD -> Library -> Preferences -> com.native-instruments.[library-name].plist.

For example: com.native-instruments.Battery 4.plist

This should remove the "broken installation" icon and allow you to do a fresh reinstall of that library.

All comments

Milos

Ralf, try to make your own custom folder for plugins and then go to the File Management to change some plugins to that folder you created.

Hope it helps.

J3uddha

I fixed my issue by deleting the .plist files for my missing libraries. On a mac, you can find them in Macintosh HD -> Library -> Preferences -> com.native-instruments.[library-name].plist.

For example: com.native-instruments.Battery 4.plist

This should remove the "broken installation" icon and allow you to do a fresh reinstall of that library.

martin cuter

https://community.native-instruments.com/discussion/comment/108768#Comment_108768

Thank you very much!!

it solved my problem, probabily cause i used to have cracked k.player 7

Billy D

I uninstalled Native Access 2, and reinstalled and older version. I was able to install all the programs that weren't installing. The one program that still didn't install I found the download folder where it was located and I unzipped the file and installed it myself. That's how I got around the file location error. Then you can go ahead and reinstall Native Access 2.

passerby

i had the same problem with 'the Grandeur' and 3 others.

The standard content location path had been C:\Users\Public\Documents\...

there I had all the folders like 'action strikes' and 'scarbee pre-bass' for example.

I also had the folders of the libraries that i couldn't install, but those, for example, were not named 'the Grandeur' but 'the Grandeur library'. For some reason NA didn't create a new 'correctly named' folder and only displayed the error massage.

so I just deleted these 4 empty folders and then the installation worked without problems.

Mic3 Drip

Komplete start is a bundle if you download the packages separately this will happen when you download the pack same for any other bundles if you download the bundle first title run like normal

Menno Monet

What is so strange is that today (September 7th 2024) I ran into the same problem. Never had any trouble installing Komplete in the past. Lucky for me I had an older Native Access installation file on hand. Deleted the latest version, and all works fine again with the old one.

Side note: The reason for installing all my Komplete plugins onto a freshly installed OS was that everything went to ****** when I updated Native Access and some of my plugins. Within Cubase I could not touch a VST that did not cause a complete system crash. Literally every NI VST within caused my system to crash. Several hours trouble shooting led nowhere, so the only thing I could think of was a complete refresh of everything.

Back to the strange thing: WHY THE HELL did nobody from NI fix this issue? There a serval threads on this topic on this forum (and other fora) and there is not even a reply from an NI official (not that I have seen anyway). The first thread here is from November 2023. Nobody bothered to fix this it seems? Feels very strange to me.

rokiracune

I'm on a Mac M3 iMac. Switching to the Intel version of Native Access loved this issue for me.

rokiracune

Switching to the Intel version of Native Access solved this issue for me.

Quick links

Unanswered questions