I did the same recently, and found there is a fix for that by temporarily downgrading to Kontakt 5.6.6, adding all your NI libraries, upgrade back up to the newest Kontakt, open Native Access and it automatically authorizes all your NI libraries. A pain in the ass, and it shouldn’t be necessary but it only takes 10 minutes and that’s a lot better than having to re-download everything. I’m on a Mac though.Frankly, NI need a bit of a kick in the pants - they seem to have become complacent.
The ridiculous situation where you have to re-download all your NI libraries again if you have to re-install your software or move to a new computer has been known for months and nothing has been done.
I recently moved to a new windows laptop, and the installer can't even install products on Windows 10 by itself, and had to do them one by one manually.
Simple workflow stuff like being able to group collections of libraries to make the library window manageable can't be that much of a programming mega job.
Some of their latest updates seem to have made things more awkward rather than better.
I am happy to see Spitfire's new engine - and trialing it through labs instruments is an inspired idea. I wish them all the best with it.
Now about the new SF engine, I don’t think its a bad thing to give Kontakt some competition, but the one thing Kontakt has going for it is years and years of refinement and bug fixes, and a scripting language that lets devs do amazing things - and at the end of the day, isn’t that what we all want: Effeciency, stability, capability and Kontakt has all that. I’m slightly worried, but will withhold judgement til we see how it works.
One essential feature that I cant find anything in manual about is the ability to purge samples, and load the ones you need in on the fly. I do hope they will add this, for those of us on resource challenged systems, that’s a pretty essential thing.