Win 10 Kontakt 6 Fatal Errors when Installing Libraries

Hi.
I have just upgraded from Kontakt 4 to Kontakt 6 on Windows 10, latest version.
The application itself is working successfully. However, I'm unable to install any of the accompanying libraries. I get "Fatal Error. Can't open ..... etc" to my C:/User:/ Public .... directory on every attempt.
I have no idea why this should happening and repeated attempts are costing me a fortune in broadband fees down here in rural NZ. Is it possible the files names are too long?
Any advice greatly appreciated.

Many thanks, David

BTW, is it me or has the search function vanished in K6?

 

You are correct about the database/search. NI is aware of the issue and I am hoping we will hear something definitive from them soon.

Regarding the fatal error, unfortunately, I have no ideas. Take screenshots of the exact error and try NI's tech support. (Or other users on the forum may have an idea.)

 

Hi David
Thanks for your reply. I have subsequently figured a solution by trial and error. I located the ISO images and extracted them to a directory manually. I then installed from there to my sample drive and lo and behold!
I'd still love to no why their installation process failed. All I can think is that the file names exceed the Windows limit (however unlikely that may be).

Yes, I already miss the search function. I have a library of hundreds of self-made files going back to the Mirage days that I still use a daily and have no idea where they are on the drive. (That probably says more about me than NI). So yes, please bring back the search.

Thanks, David

 

Before installing a NI library (not 3rd party ones) via Native Access, go to NA preferences and change the Content folder to where you like the library/libraries to be located. The errors you got sound like the folder that was supposed to contain the libraries didn't have write access.

 

Hi EvilDragon

Thanks for the reply. Yes, it could be a permissions issue. I have since installed by extracting from the ISO files and installing manually. I trust that that renders the same results as the automated install?

Thanks, David

 

It wouldn't make any sense if it were otherwise

 

Might not help, but what we did on Win10/64, was reinstall Native Access 'as admin' and then when running it we launch it as 'admin' ... and this works. Including with the latest Win10 December updates. Seems to help with bizarro Windows permission issues. We did have a permission issue with something else being updated the other day, and funnily enough -- I think it was iLok -- the Windows maintenance thing launched and "fixed it." Sheesh. God I love my Macs.