AdamGrossmanLG
I only have 1 device for my Impact LX49+ so nothing for me to do here, oh and I am able to load up any standalone softsynth and it plays using my keyboard just fine.  Just not Sonar (yet the problem can't be Sonar, Sonar simply is never broken).
 

As a test: if you disable ALL devices under Sound, Video, and game controllers, EXCEPT Impact LX49+ and Realtek High Definition Audio, does the problem go away?

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. 

Base 57
Please forgive me if I missed where you have already answered this, but have you tried deleting the TTSSeq.ini file?

I did not try this, but it seems like a very simple file:
 
[Options]
PumpDataMsec=250
UseAlias=1
[MIDI Input Devices]
0=Impact LX49+
1=MIDIIN2 (Impact LX49+)
MaxInPort=1
[MIDI Output Devices]
0=Impact LX49+
MaxOutPort=0
[MIDI Echo Devices]
MaxEchoPort=-1
 
The reason I did not try this, is because I shouldn't have to delete a file every time to get my keyboard to work (especially this happens on many versions of Sonar (dating back to X1) and follows me from computer to computer.
 
I also did not see any reason given to delete this file.   I *assume* also it will remove my control surface info as the MIDI Device will no longer be here?  Not sure there though, also think it is highly unlikely this will resolve the issue, AND even if it does, the answer here is to delete the file every time?
 
Also I did not delete the file as Anderton assured me its not a Sonar issue.  This is a Sonar file, not an OS file.
 
If it helps with the troubleshooting I will be glad to try it though.  I just didn't know what the end game here was.

Anderton

AdamGrossmanLG
 

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

yes I did. The bat file opens the device manager.

 
You also have to specify the showing of hidden devices after running the bat file. 
 

Either way, why would Sonar be the only app that won't accept MIDI input?

 
Maybe it's aware of more MIDI devices than other apps and therefore ties up those ports...I don't know what's weird about your system.
 
All I know for sure is I've used dozens of MIDI controllers over the years, probably close to 50, and SONAR has recognized every single one unless there was an issue with the MIDI port limit or a driver written so that the controller had to be used with a specific port. In the former case, I deleted the ghosted MIDI devices. With the latter, if I didn't remember which MIDI port I had used originally, I had to de-install and re-install the driver.
 

I did "show hidden devices"
 
I followed the article 100%.  It is pretty fool-proof anyway, not much to mess up here.
 
To add, Sonar DOES recognize it.  When I power on the device, I get that message:  The above audio/MIDI device was connected to your system. Do you want Sonar to add this device now?  Yes/No".


So Sonar IS recognizing it, but I *think* it might be listening to a cached port instead of the current port.  This is only speculation.   I seem to remember a post a long time ago, back in 2009 or so actually about the caching of USB ports, and how it was recommended to not use a USB hub (which I do not).
 
I am not sure what kind of caching is going on here, but I think its a problem somewhere along those lines.
 
This issue has followed me through 4 different DAW desktops, different controllers and dating back to at least X1, maybe prior.

To add..
 
USB Selective Suspend Setting:  Disabled  (I've tried enabled too)
 
 
 

DrLumen
 

The other setting is in the Device Manager under the USB controllers. Right click on the various hubs and select Properties, then go to the tab for Power Management and you will see a check box for "Allow Computer To Turn Off The Device To Save Power". Uncheck it. There may be several hubs listed so you will want to look at them all.




I am unchecking these right now. I will report back here with the results.
 
Thank You!

Delete the TTSSeq. When you reopen SONAR It will build a new one. You will have to fix all of your friendly names if you use them. You will only need to do this once. It may not fix the problem. Then again it may.
 
Years ago I had a problem very similar to yours. Back then Cake had phone support. Delete that file was the first thing they told me to do. It worked.
 
If you are nervous about deleting it, just rename it.
 
YMMV

Could you not rename the file, or move it elsewhere, then if it doesn't help rebuilding a new one just either revert the name the original file or copy it back from where you stored it, thus not loosing anything, or does it not work like that? Just thinking aloud, similar procedure works fine in a lot of other situations.

Sorry Matron, I edited my post while you were making your suggestion. 
 
You were quick.
 

OK, well let me try these new power settings first.  I would like to pinpoint what fixes it. I will try this and see how this works.
 
By the way, having to delete a file = bug.  FYI.  I was told this is not a bug, so I didn't go down this route.