Korg microKEY-25 installed on Win7 but 'not connected' as MIDI device

[Nantonos]

I just got a Korg microKEY-25 for use as a portable, travel-freindly keyboard. It installed and worked fine on my Win XP laptop.

Now back home, I installed it on my Win7-64 desktop. The driver installed fine, it shows up in the device manager:


and the correct \Korg driver is being used:


but MIDI software like my DAW (Studio One 2), MIDI-OX, Korg's own Korg Control Editor, all report that the device is not connected.


The lights come on and the octave buttons light up as expected. I have tried different USB cables, and connecting to different USB ports on the computer. Suggestions?

[screagh]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hi,
Did you get any response yet???

I had the same problem so I wrote to Korg Support for help. They said I had hit the 10 device limit in my Windows Registry. They sent instructions in a PDF file which I'm going to copy below... (be sure you backup registry Device32 keys first per microsoft instruction reference, also included below).

It worked OK for me on Win7. For each Korg Legecy software synth (M1, etc.) I had to go into System>Preferences>MIDI Settings Tab and select the microKEY-25 1 keyboard as the MIDI In Device 1 to get the software to recognize the device. All of them are working now.



Punch In
TECH BENCH
Fixing Windows XP MIDI
Port Problems
by Craig Anderton

So there I was, reviewing a Yamaha Motif XS6, which
has all kinds of cool MIDI options. I downloaded the USB
MIDI driver and installed it; its little applet booted up, and it
showed up as a fully functioning MIDI device . . . except no
sequencer could see it. Say what? Turned out I was a victim
of the dreaded Windows XP/NT/2000 MIDI device driver
limitation problem.

These operating systems can install a maximum of
ten MIDI device drivers; after that, they fall down and say
"no más!" And it's not hard to use them up if you have lots of devices.

For example, if you install a USB MIDI
device driver while it's plugged into one USB port, then
plug it into a different USB port and install the driver
again, you now have a duplicate driver and have used up
two MIDI device drivers. The same will happen if the
interface is on a PCI card, and you change its slot. The
solution: Go into the registry, hunt down duplicate driver
entries, and delete them.

RME has an excellent FAQ on this subject by Matthias
Carstens at http://www.rmeaudio (http://www.rmeaudio).
de/en_support_techinfo.php?page=content/support/e
n_support_faq_10entryd. However, it's written more for
intermediate users, so we'll deal with the issue on a more
basic level. Ready? Let's fix it.

DEALING WITH THE REGISTRY
The Windows registry is a scary place for the neophyte, but
we won't be doing anything too drastic. Still, it's a good idea
to back up your registry in case you commit some egregious
error, as messing up the registry could screw up your
computer big-time (so don't blame us). Refer to
Microsoft's instructions for registry backup at http://windows.microsoft.com/en-US/wind ... e-registry (http://windows.microsoft.com/en-US/windows7/Back-up-the-registry).

(Incidentally, if you don't want to edit the registry,
M-Audio offers a "MIDI Fix" utility at http://www.maudio (http://www.maudio).
com/index.php?do=support.drivers&k=driver&s=8
&o=Windows+XP&f=84. This clears out previouslyinstalled
MIDI devices, as described in a text file included
with the utility, but you will have to reinstall the deleted
drivers manually.)

1. Go Start > Run and type Regedit.
2. Locate the HKEY_LOCAL_MACHINE key and click on the
+ sign to its left to expand it.
3. Go down and open the tree as follows: Software >
Microsoft > Windows NT > Current Version.
4. Under Current Version, click on the Drivers32 key. A list
of sub-keys will show up in the right pane (Fig. 1); locate
the Midi sub-keys (Midi, Midi1, Midi2 . . . Midi9).
5. At this point, you have two options. Either one involves
deleting a MIDI sub-key by right-clicking on the key
name and choosing Delete. One option is to delete each
Midi sub-key (Midi - Midi9), thereby guaranteeing you've
deleted any duplicates, and re-install any necessary
device drivers from scratch. The other option is to verify
which keys are duplicates, and delete the duplicates. If
you delete a "wrong" driver key, worst case is that you'll
need to re-install the driver for that device (if that forces
you to check the net for the latest drivers, that might
actually be a good thing!).
6. In Fig. 1, note how there are two entries for usbkt1x1.dll
(both are circled in red). To verify that these are duplicates,
type Ctrl+F to call up the Find function, and type
in (for example) usbkt1x1.dll. Keep hitting F3 to find all
occurrences of usbkt1x1.dll.
7. Once you get out of the Drivers32 key, you'll find individual
instances where the drivers occur, with information in the
right pane (Fig. 2). This example shows that Midi6 represents
the driver for the M-Audio USB Keystation. However,
it turns out Midi1 also shows an M-Audio USB Keystation
driver with the same characteristics — clearly a duplicate.
8. After verifying the duplicate, return to the Drivers32 key
and delete either one of the duplicate sub-keys. You've
now freed up a MIDI device driver.

In my situation, after deleting two duplicates there was plenty
of room for the Yamaha Motif XS6, and all four of its ports
appeared. So next time you try to install a MIDI driver and
nothing shows up . . . check your registry!

<End of article by Craig Anderton>

Good Luck!!!