I'm quite happy - I'm not the only one!
It's a pity that it's not reliable reproducible (I have the issue with only 4 Kontakt instances too; only different is the behavior of protected and unprotected librarys. Beside vsl wws I use for second or third woodwinds or 3./4. french-horn westgatestudios-ww which is unprotect.)
Thats why I assumed it has to do with the protection systems. And honestly: vsl daemon and the new vsl protection, protection for Kontakt itself and two different protection systems for third part libs inside Kontakt ("The Trumpet" for example you can find under programms, others need only the nkx.file in the sample folder) and Steinberg protection for HSO (one instance) but I need this one - much protection, but to me it feels more unsecurely, not to say more dangerous. Not to contemplate the fast-paced computertechnology...
Last time, when I was changing from Hyperthreading disabled to enabled, I have had to activate again all Kontakt librarys! The technician of Kontakt support sayed: No worry, the new 6 virtual cores are like a new CPU even like a new machine, so it's normal! What???
I'm not a technician, I don't have the vaguest notion of all this stuff, but it sounds at least as complicated as the score of "sacre".
Ok. The work arounds make it possible to work - as paoling wrote.
But I appreciate all hints and help, cause in the long run it is irksome.
I have contacted the technic support of Kontakt some times ago too. Unfortunately the technician who's answered me didn't have any experience with MIR - he didn't really know it, he never worked with it! [:^)]
I noticed in vi-control forum too, that not much of the composers there are working with MIR yet. (Despite of the little teething troubles: They don't know, what they are slip.) But therefore it will not be so easy to find the reason and a solution for the issues, I'm afraid so.
Assuming the issues are in connection with systems, for comparing my specs down here. Thanks so much for replys and hints for workaround.
Kind regards
Frank