Windows 10: Windows driver issue with Akai MPK49 Midi controller - Code 28

Hi,

I'm trying to get my Akai MPK49 midi controller working with Windows 10. The controller was working on my system around 6 months ago but for some reason, it's no longer being recognized correctly by Windows.

The device is class compliant, so it should work with drivers that Windows 10 already has and does not require 3rd party drivers.

When I go to the device manager, instead of appearing under Sound, video and game controllers, it appears under Other devices with a (!) symbol next to it. Here's a screenshot:





When I go to the Properties I see this:





I've been in contact with the manufacturer of the device and they've helped me troubleshoot the issue as best they can, but it seems as if this is a Windows problem and not at all a problem with the device. I have tested the device with another computer running Windows 10 and it works perfectly. You can read the thread here to see some of the things I've already tried: Akai MPK49 not working anymore on Windows 10 / FL Studio



Any ideas?

I've put about 8 hours into trying to fix this *Sad The last resort is reformatting and reinstalling Windows, and I really don't want to do that.

Thanks!
Aaron

:)

 

Windows 10 Midi Keyboard not working

I have an akai lpk25 midi keyboard and until recently it worked fine on windows 10 Pro. Now without reason no response from it in FL Studio 11 or Ableton live 9. Windows is fully updated, both DAWs recognize the device being there and it also appears correctly
in the device manager.

Not a hardware problem as using all the same but with a win 7, Ubuntu, and Win 10 Pro from January of this year, (without current updates obviously), everything works fine, so I believe that an update somewhere along the line has fubard the midi controllers.

Note that with current updates akai's own editor will not recognize the device, the only semi fix that i have found is uninstalling the drivers windows provides, restarting and plugging it in with a DAW running give a momentary amount of response, (seconds),
but then back to nothing

 

USB device could not be migrated

Hi Everyone,

USB device migration fail notice seems to be a universal problem looking at the various mentions from others.

I've got an AKAI Midimix usb midi control surface that's failing.

I know it's not the device - I got a new replacement when it first occured - same issue. AKAI say their driver is compliant.

Running on Win10 64bit and looking at the device manager I see...

Device USB\VID_09E8&PID_0031&MI_01\7&1ef6baf4&1&0001 could not be migrated.

Last Device Instance Id: USB\VID_09E8&PID_0031&MI_01\6&375CB17&0&0001

Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}

Location Path:

Migration Rank: 0xF00000000000F102

Present: false

Status: 0xC0000451

Can anyone offer advice on how to resolve this?

Thanks for your help.

Alan McC

 

The latest Windows 10 update solved my problem!
I think it was a corrupted Windows file perhaps.