Hi, Michelle.  Although you have already tried direct connections to USB ports, I would advise against using a hub.  Most manufactures (and users) state the same.  (Don't know about M-audio stuff, but I personally don't trust or use 'em.)
 
Kind regards,
 
Living Room Rocker

ok, I tried removing MidiOx, no change. 
 
I've tested my keyboards on my spare computer,  they both worked fine together.  I kinda figured they did, or else why would M-Audio have released drivers for this to work in the first place.
 
So I'm back to wondering what is going on with my computer that they do not function.

So the problem is somewhere within MIDI drivers of your Win7 64bit Pro (can be broader than M-Audio driver).
 
Do you by chance see something in the event log?
 
You can try this:
https://social.technet.microsoft.com/Forums/windows/en-US/c0988c75-da44-4295-b1f8-a6f384ce4b91/usb-midi-not-working-in-windows-7-pro-64bit?forum=w7itprohardware
 
In the part of removing midi1,midi2... and checking that UpperFilters is there.
 
I have "skipped" Win7, so I do not have big experience with that particular version. I hope someone else can give you helpful tips what to check as next.
 
Edit: In Win8 I can see under {4d36e96c-e325-11ce-bfc1-08002be10318} entries for all devices. I think Drivers/midi/wdmaud.drv Alias property should be unique.

@ azslow... as far as I can tell by following your link, reading the information there, and checking my registry, the upperfilters and ksthunk values are correct and not missing.  slightly different problems, but best to be thorough!  thanks for digging that up.

I think I found something!  but I don't know what to do about it....  and frustrating that I looked at this a few times before and somehow it wasn't registering on me.
 
I told it to Update the driver, then Browse my computer for Driver Software then Let me pick...  I chose the driver and it installs the right one.  Correcting itself!  BUT  if I fix the Axiom25 the Air49 get's the driver too.  I go and fix the Air49 and it works, but adds it back to the Axiom25, nasty cycle ensues...  like I say, not sure what to do about it now.  Even tho I can see the issue more clearly. 
 

I am not aware of the M-audio driver installation, but perhaps this might have something to do with it...  When you install the driver(s), are both keyboards connected to your PC?
 
Kind regards,
 
Living Room Rocker

I tried disconnecting the one that was working right, installing the new driver on the other.  and the other way around.  And if I try to fix it with the keyboard unplugged it doesn't take and still shows both drivers...  this is the same thing it's been doing all along, I've only discovered a new way to view the problem, and an easier way to install the correct driver for one of them at a time... 

Woot!   got it!  /happydance
 
I just hope the next few days doesn't find me back here saying I only thought I had it.
 
So...  the uninstallers for the Axiom drivers weren't deleting the actual drivers from Windows/System32/Drivers... neither, does it seem, that device manager was removing them when I answered Yes to removing the drivers when uninstalling the device.  So, I uninstalled the devices in Device Manager and checked for hidden devices, then uninstalled the drivers from Add Remove Programs and then deleted the drivers manually from the drivers path... so what's working now is my Air49 with Drivers from M-Audio installed (and they have to be installed to prevent an unknown device (which I assume is Hypercontrol)), and no drivers from M-Audio installed for the 25, even tho M-Audio said I needed them for this to work...  pfft...  anyhow...
 
Yay!
 
Thanks everyone for helping, I really appreciate it, if it wasn't for you all I probly would have given up a week ago.
 

I have been manually checking that things uninstalled get deleted or not for so long it didn't occur to me to suggest you check to make sure.
 
YAY!!!!!!!!!!

You ARE a trooper for hanging in there for all of this.
 
Crappy uninstallers drive me Nuts!
 
Bob Bone