It very well could be a bug, a lot of people will discount it from being a bug because it does affect everyone or even the majority, but only a few, it still could be a bug, a bug that is triggered specifically by an individuals personal configuration, that's the way I look at it as apposed to the knee jerk "It's not a bug because I am not seeing it" types of responses anyway. I don't think that just because something only affects a few immediately rules out it being a bug. I could be wrong, but . . . 

Cactus Music
Ya I noticed that too, I don't get all those Microsoft devices under Audio,  the HD Video audio ( that should be disabled anyhow) and  the on board.. so what's with all that ? I'd certainly zap them. 
 
But that said, we are talking MIDI not audio, I fail to see why a audio driver would have anything to do with a midi driver. As I said earlier, the problem most likely is the MIDI driver, Midi drivers are sort of like audio drivers and just like we all recommend using good audio drivers,, I also beleieve you need a good midi driver. Sonar is picky. 
A simple test would be for you to borrow a Roland or Yamaha controller and see what happens. And as I said, don't let W10 install a generic driver if your controller has a proper driver posted or on DVD. 

 
Yup, I hear ya!  It could be this thing or that thing over there. Poking around at one thing at a time may seem productive, but at the same time it leaves too many variables roaming around unaccounted for.
 
So I have learned over several decades of working with computers, that usually the quickest method of isolating a problem is to strip it down to as few components as absolutely necessary to operate, get it working again, then add back one thing at a time until it breaks again.  That usually always works, unless multiple things are causing the original problem.  That always isolate a single point of failure.

Matron Landslide
It very well could be a bug

 
Well of course it very well could be, and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question. The problem with assuming something is wrong with SONAR is that if you become invested in proving that, if something isn't wrong with SONAR you won't find where the problem really lies. It's like the people who have a problem and so they re-install Windows and re-install SONAR...then find out updating their audio interface driver was the correct solution.
 

Anderton

Matron Landslide
It very well could be a bug

 
Well of course it very well could be, and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question. The problem with assuming something is wrong with SONAR is that if you become invested in proving that, if something isn't wrong with SONAR you won't find where the problem really lies. It's like the people who have a problem and so they re-install Windows and re-install SONAR...then find out updating their audio interface driver was the correct solution.
 

 
But Mr. Anderton -
 
If the MIDI keyboard is able to send data to standalone softsynths and also Reason 9, and the only issue here is receiving data in Sonar... wouldn't it be logical to say MOST LIKELY it is something with Sonar?  Sonar needs Windows to reboot somehow.
 
Personally, I have no steak in the matter, I don't care who's bug it is if its even a bug at all.   I would just like to get to the bottom of it.

Anyway, it might be several days or even a week or two as this problem doesn't always present itself, so stay tuned, I will report here if the power management settings helped.  If not TTSeq is next.

AdamGrossmanLG
But Mr. Anderton -
 
If the MIDI keyboard is able to send data to standalone softsynths and also Reason 9, and the only issue here is receiving data in Sonar... wouldn't it be logical to say MOST LIKELY it is something with Sonar?

And if it's only happening for you, wouldn't it be logical to say it's MOST LIKELY something specific to your system or installation? Seriously, if SONAR didn't recognize MIDI input devices, this forum would be lit up like a Christmas tree.
 
You want to believe it's something with SONAR. Fine, maybe it is and I realize that's your go-to. But if it isn't, you're wasting your time and everyone trying to help you in this thread. I bet if I was sitting in front of your computer I'd have this solved in under 30 minutes. But I'm not.

Anderton

AdamGrossmanLG
But Mr. Anderton -
 
If the MIDI keyboard is able to send data to standalone softsynths and also Reason 9, and the only issue here is receiving data in Sonar... wouldn't it be logical to say MOST LIKELY it is something with Sonar?

And if it's only happening for you, wouldn't it be logical to say it's MOST LIKELY something specific to your system or installation? Seriously, if SONAR didn't recognize MIDI input devices, this forum would be lit up like a Christmas tree.
 
You want to believe it's something with SONAR. Fine, maybe it is and I realize that's your go-to. But if it isn't, you're wasting your time and everyone trying to help you in this thread. I bet if I was sitting in front of your computer I'd have this solved in under 30 minutes. But I'm not.

Well it has happened to another user on this post, but still, seems like a rarity I guess, but there's not much the user can be doing here.   

I'd invite you to Teamviewer in, but you can't press my keyboard buttons.  ;)

AndertonIt's like the people who have a problem and so they re-install Windows and re-install SONAR...then find out updating their audio interface driver was the correct solution.

re-installing sonar or windows to fix a problem is recommended far too often around these parts

pwalpwal

AndertonIt's like the people who have a problem and so they re-install Windows and re-install SONAR...then find out updating their audio interface driver was the correct solution.

re-installing sonar or windows to fix a problem is recommended far too often around these parts

this cant be an audio interface problem, I am not using the MIDI on my audio interface, plus I've had this with 3 different audio interfaces now.  Scarlett, Audient and Behringer.

abacab

Cactus Music
Ya I noticed that too, I don't get all those Microsoft devices under Audio,  the HD Video audio ( that should be disabled anyhow) and  the on board.. so what's with all that ? I'd certainly zap them. 
 
But that said, we are talking MIDI not audio, I fail to see why a audio driver would have anything to do with a midi driver. As I said earlier, the problem most likely is the MIDI driver, Midi drivers are sort of like audio drivers and just like we all recommend using good audio drivers,, I also beleieve you need a good midi driver. Sonar is picky. 
A simple test would be for you to borrow a Roland or Yamaha controller and see what happens. And as I said, don't let W10 install a generic driver if your controller has a proper driver posted or on DVD. 

 
Yup, I hear ya!  It could be this thing or that thing over there. Poking around at one thing at a time may seem productive, but at the same time it leaves too many variables roaming around unaccounted for.
 
So I have learned over several decades of working with computers, that usually the quickest method of isolating a problem is to strip it down to as few components as absolutely necessary to operate, get it working again, then add back one thing at a time until it breaks again.  That usually always works, unless multiple things are causing the original problem.  That always isolate a single point of failure.

I think we both agree and at no point has the OP done this. As I said, I don't understand why people obsess about audio drivers when the issue is a midi driver. 

AdamGrossmanLG
Also I did not delete the file as Anderton assured me its not a Sonar issue.

That's not true, and if you can't read what I wrote correctly, it begs the question of whether you can read the solutions that others have offered correctly. For the record, I said:
 
"Well of course it very well could be [a bug], and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question."
 
And:
 
"And if it's only happening for you, wouldn't it be logical to say it's MOST LIKELY something specific to your system or installation?"
 
And:
 
"You want to believe it's something with SONAR. Fine, maybe it is and I realize that's your go-to."
 
Facts are facts. Good luck.