I am scratching my head on this one, for the moment, but I will keep digging to see if I can help.
 
I have a quick question - in your initial post you mentioned a workaround involving you having to "split the track".  What did you mean by that - was it going to a Simple Instrument Track?
 
I myself almost never use Simple Instrument Tracks with Kontakt, because I normally have multiple instruments loaded into a single instance of Kontakt.  If indeed you are/were using Kontakt's Session Horns Pro and a Simple Instrument Track, I would like to know if you would still have this issue if you set the project to use a separate audio and a separate midi track instead.
 
Bob Bone

Please read through this thread: http://forum.cakewalk.com/FindPost/3050451
 
Perhaps there is info there that might apply.
 
Bob Bone
 

robert_e_bone
 I am scratching my head on this one, for the moment, but I will keep digging to see if I can help.
 
I have a quick question - in your initial post you mentioned a workaround involving you having to "split the track".  What did you mean by that - was it going to a Simple Instrument Track?
 
I myself almost never use Simple Instrument Tracks with Kontakt, because I normally have multiple instruments loaded into a single instance of Kontakt.  If indeed you are/were using Kontakt's Session Horns Pro and a Simple Instrument Track, I would like to know if you would still have this issue if you set the project to use a separate audio and a separate midi track instead.
 
Bob Bone

 
Yes, running it as simple instrument...just midi. I did go through the process of having 1-16 outputs set up for Kontact, but I found that after putting several modules on there - in theory great - it was using to much of the first core of my CPU. Some forum members suggested just running individual instances of Kontact, which apparently puts less strain on that first core? Anyway, splitting the instrument gives me an audio to record the midi to. I then move that audio to an audio track and delete Session Pro Horns, thus freeing up resources. It's a workaround. NI have suggested uninstalling via Microsoft Fit It and then reinstalling, so I'm currently trying that. That's their best solution at the moment. If that fails, then in their communique, they state that I should contact Microsoft Support as the problem is probably rooted in Windows System - hope not as I don't like my chances of getting support from Microsoft based on past experience.

Fabio Rubato
 Anyway, splitting the instrument gives me an audio to record the midi to. I then move that audio to an audio track and delete Session Pro Horns, thus freeing up resources. It's a workaround. 

I'm not sure what you mean by "splitting the instrument" and "move that audio."
Have you tried bouncing the Kontact output to an audio track?  Or freezing the Kontakt (this will render as temporary audio and free up resources by not engaging the synth)?

Slugbaby

Fabio Rubato
 Anyway, splitting the instrument gives me an audio to record the midi to. I then move that audio to an audio track and delete Session Pro Horns, thus freeing up resources. It's a workaround. 

I'm not sure what you mean by "splitting the instrument" and "move that audio."
Have you tried bouncing the Kontact output to an audio track?  Or freezing the Kontakt (this will render as temporary audio and free up resources by not engaging the synth)?

If you right-click on the instrument's midi track, there's an option to split the instrument, which gives you the midi and an associated audio track. I can just record the midi then onto this. I can then take the recorded track into another audio track and delete the instrument. 
 
Yes, normally I would just freeze the track, but on this occasion, the frozen track did not have any audio sound, which was weird...that's never happened before when freezing. 
 
Anyway, NI suggested uninstalling and re-installing using Microsoft's 'fix it' tool, so I'll test it to see whether this has addressed the issue.
 
Thanks