USB MIDI Keyboard input not working

I just completed a new DAW build and am currently installing SONAR Platinum, associated extras and 3rd-party plugins. See my signature line below for the specs of the new DAW. I'm currently working on stand-alone versions of synths and synths in instrument tracks. MIDI input isn't working for any of these most of the time but it sometimes does. Right now, it's not working at all.
 
I have a AKAI MPK49. It shows up reliably in Device Manager (DM) under Sound, video and game controllers and when I remove/insert the USB connector into the back of the MPK49, it's line in DM goes away and comes back. I've uninstalled and reinstalled it in DM and I've tried to update drivers. According to DM I have the latest drivers and the device is working properly.
 
I've tried several google searches finding nothing useful except a video that stated that there are only 10 MIDI ports available in Windows 10. That could be the problem because when I started SONAR once in this process, a dialog box indicating that there were no MIDI ports available for the (3) MPK49 MIDI inputs. That doesn't happen now. All 3 MPK49 MIDI inputs are listed in the stand alone versions of the synths and in the MIDI Device list for SONAR.
 
In the video the instructor used a KORG app to display all connected MIDI devices and select the active ones. I don't think I have and haven't found such an app. Can someone help me troubleshoot and correct this problem? 
 
Thanks.

riversw88, thanks. I read Craig's article and created the batch file and followed Craig's instructions. The Akai MPK49 is shown as one of the active (not grayed out) Sound, video and game controllers. I also found and deleted 5 grayed out Microsoft Streaming devices and the Microsoft Trusted Audio Drivers and tried the keyboard again with a stand alone synth (AAS GS-2) but still no luck. The Audio Setup for GS-2 shows all three of the MPK49's MIDI inputs selected. I can play the GS-2 by clicking notes on the GS-2's displayed keyboard. There must be something else and I'm feeling pretty stupid at this point since I must be overlooking something.
 
I also fired up MIDI-OX. It show the three MPK49 MIDI inputs but  I couldn't figure out what to do with MIDI-OX.
 
Thanks again.
Bill

abacab
The best thing to use MIDI-OX for is the MIDI monitor.  It shows exactly what data that you are sending from the controller.  No guessing required! 
 
1. It's the best way to troubleshoot MIDI connectivity issues.  If your keyboard, cables, or ports are messed up, you should be able to spot that quickly.
 
2. Otherwise, if that part is good and you are getting what you need into the computer reliably, then you can focus on setting up the ports in your other software.

Ok. It works. When I press a a key [C4 for example] MIDI-OX displays the on and off messages. I'd been using another program [Vyzex MPK49] which is tailored to managing MPK49 presets for that function. I think the MPK49 is working and Windows is receiving inputs from it. Vyzex and MIDI-OX see the inputs but SONAR and the standalone synths don't.

On a lark I moved the MPK49 USB 2.0 connection to the spare USB 2.0 port on the DAW back panel. Now it works. I viewed hidden devices in Device Manager and there was a grayed out MPK49 which I uninstalled and a new one for the new port. Also all the grayed out ports that I'd previously uninstalled were back. When I tried the keyboard in SONAR and stand-alone synths it worked. I don't know why but it did. So I switched it back to the original USB 2.0 port. It still works and all the grayed out connections are gone. Looks like Windows Device Manager is seeing ghost, but they are gone for now. I don't know what the problem is, but it seems to be something in Windows 10. Here's a screenshot I took earlier showing the grayed out ports that are now gone. https://www.dropbox.com/s/d18mqks9o58xsr9/Hidden%20Sound%20Devices%20170621.png?dl=0
 
 Here's a screenshot showing that there are no longer any ghost Sound, video and game controllers which I'm guessing is the normal situation. https://www.dropbox.com/s...7PEWQjwBkkBSkmNma?dl=0

Glad you got it sorted!  The mysteries of Windows 10, LOL!!!

Hi.
 
Down in the device manager for usb ports...did you go into the Preferences of USB ports and deselect "Let windows turn off this Port"...?
 
Part of power management tweaking , is said to stop this sort of off and on...issue.
 
Windows waits for ports to be engaged with a Plug into usb, then it sorts the driver.
 
if always on..and always connected...when you turn on your device MPK49...if booted into windows, should engage the usb port...and not go off at all, if that selection is set to not allow win to turn off.
 
If booting up OS with MPK49 on...It should be detected...also .?
 
So check that...Windows might be set to turn off your usb ports, to save power, if it believes it is not in use.
 
Now this awareness of the OS and usb ports/devices...is not perfect...
 
Some devices seemingly need to be (worked around)..and some work when turned on before boot, and some might need to be turned on after boot up of the OS and all services and drivers loaded.
 
Perhaps something liken is with you?
 
Just thinking out loud.
 
Cheers.
 
 
 

I don't mean to hijack this thread but I am having the same problem with my Alesis Q49 USB midi controller.  It was working just days ago and now not. It shows up in device manager, it seems to be sending midi messages to windows but Cakewalk does not seem to respond to them.
I did notice that it says the drivers were "migrated" on 6/17/2017?  Was this a Windows 10 update?

reginaldStjohn
Midi OX won't even open my USB Keyboard input. It says "Out of memory"
 

If you cannot open your keyboard driver in MIDI-OX, then you most likely have Windows issues ...
 
http://www.alesis.com/classcompliant
 

What does "class compliant" mean?

---

A class compliant device is one that does not require an extra driver from Alesis to connect to your *Windows computer, Macintosh computer, or iOS device. A class compliant device uses drivers that are written by Microsoft or Apple, and come pre-installed on the computer.
*Windows (98SE and up) is required for class compliant support.

OK. then start your own thread, post your details, and see what suggestions you get that can help to to solve your issue.  Piggybacking on another post is confusing for all involved, and will not speed up your problem solving.  There are many differences in system configuration, devices, etc., that can sound similar to yours, but it is always best to begin from a baseline with your specific config.