Fixing Korg USB Midi driver issues in Windows 10 May 2019 Update

Fixing Korg USB Midi driver issues in Windows 10 May 2019 Update

Over the weekend I discovered an issue with the Windows 10 May 2019 Update and the Korg USB MIDI drivers. The drivers enable Korg devices to talk to Windows over MIDI via a USB connect for products like the Korg Kronos, microKey and other devices. I have a Korg Minilogue synthesizer, which connects to a PC via USB. Once connected your music apps can communicate with the Korg device, it is also used by the Korg sound editor tool. There are many other Korg devices use the same driver and on the 1809 version of Windows 10 everything worked fine.

UPDATE: 30/05/2019 Korg say their driver is not compatible with the May 2019 Update.  If you have already updated you should follow my fix.

UPDATE: 11/06/2019 I have recorded a YouTube video showing how to do this.

After updated to the Windows 10 May 2019 Update (1903) my music and Korg apps would not communicate with the synths anymore. The drivers were all working fine and after a lot of searching and digging around in the registry I found the issue and have a fix. This fix will also work with previous version of Windows where you have the same problem.

The root of the problem is that Korg USB Midi driver will only work on the first 10 channels in Windows 10 (not to be confused with midi channels) so if Windows allocates the Korg device to a channel above 9 nothing will work with it.

To check your Korg midi setup run the Uninstall Korg USB Midi Device app (this will be installed as part of the Korg drivers and will not actually un-install the driver if you cancel it).

After updating, it looked like this: with the Korg devices on channel 12 and 13 with channel 1 to 9 not used.

So to get it working you have to do some changes in the registry to get the Korg devices below channel 9, and then the drivers will work.

The first part is to allocate an alias to the Korg driver. In the 1809 update of Windows 10 the alias values where already there but after the update they had been removed.

Open up Regedit and navigate to:


You need to find a class with a name of Media so search for a value of “MEDIA” (Control – F).

Once you have found that expand the node and you will see a list of numbers starting with 0000. One of more of them will be the Korg setting.

Find the first one that has the DriverDesc matching your device, which in my case is KORG minilogue. Expand the node down to the bottom item, which will be KORGUM64.DRV (make a note of this value). Select the node and then you will need to create a new string value.

Right click on the node and select New/String value.

The name should be Alias with the data midi1 for the first device, midi2 for the second and so on. (thanks to Andy for the clarification)

Do this for all your Korg devices in the class. Note, even though I have just the one Korg Minilogue connected there were two device sections for it.

With that bit completed for all your Korg devices you need to go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

Then add a new string value with the name of midi1 and the value data of the driver you allocated to midi1, which in my case is KORGUM64.DRV. Repeat this for each device you added in the previous section.

Now when you run the Uninstall Korg USB-MIDI Device app you should get something like the following:

As you can see, the Minilogue is running on channel 1 and 2. So now, I can use midi with the synth via my music apps.

I added midi3 for my Korg Radias and everything is working as it should be.

I do not know why the alias values are removed during the Windows 10 May 2019 Update (1903), but this fixed my setup. As always when using regedit please take care!

Here is my YouTube video:

Here is a list of devices this solution should work with (taken from Korg’s website):

microKORG XL+
MS-20 mini
Pa300 Brazilian Edition
Pa300 Chinese Edition
Pa300 Indian Edition
Pa300 Indonesia Edition
Pa300 Iran Edition
Pa300 Peru Edition
Pa300 Romania Edition
Pa300 Serbia Edition
Pa300 Turkey Edition
Pa300 Vietnam Edition
SV-1 Black
Pa300 Bulgarian Edition
minilogue xd
KRONOS (2011)(sold out)
KRONOS Platinum(sold out)
KRONOS X(sold out)
KROSS 1(sold out)
M3(sold out)
M3 XPanded(sold out)
M50(sold out)
microKORG XL(sold out)
microSAMPLER(sold out)
microSTATION(sold out)
microX(sold out)
MP10Pro(sold out)
Pa1X(sold out)
Pa1X Pro(sold out)
Pa1X Pro Elite(sold out)
Pa2X Pro(sold out)
Pa3X(sold out)
Pa3X Le(sold out)
Pa500(sold out)
Pa500 MUSIKANT(sold out)
Pa500 ORIENTAL(sold out)
Pa588(sold out)
Pa800(sold out)
Pa900(sold out)
PS60(sold out)
R3(sold out)
RK-100S(sold out)
TR(sold out)
TRITON Extreme(sold out)
X50(sold out)

electribe sampler
KAOSS PAD KP3(sold out)
MS-20 Kit(sold out)
MS-20M Kit + SQ-1(sold out)

microKEY Air
nanoKEY Studio
nanoKONTROL Studio
K-Series(sold out)
KONTROL49(sold out)
microKONTROL(sold out)
nanoKEY(sold out)
nanoKONTROL(sold out)
nanoPAD(sold out)
TRITON taktile(sold out)

KORG Kontrol Editor

C-520(sold out)
C-720(sold out)
HAVIAN 30(sold out)

KORG Hybrid Pianos

KS-320(sold out)
KS-520(sold out)

D3200(sold out)
D888(sold out)

PX5D(sold out)



17 thoughts on “Fixing Korg USB Midi driver issues in Windows 10 May 2019 Update

  1. This has proven invaluable to me for my Korg Minilogue and MS-20 Mini. Thanks so much.

    For clarity you could change:
    “The name will should be midi1 for the first device, midi2 for the second and so on.”

    “The name should be Alias with the data midi1 for the first device, midi2 for the second and so on.”

      1. I do not understand how to add an entry for “midi2”. In folder KORGUM64.DRV, you can only add 1 entry with name “Alias” (having value “midi1”). How do you add a second entry for “midi2”?

        1. There will be a branch for each device, so for me there was 021 for the Radias and 022 for the Minilogue.
          So you add the alias part for each korg device you can in the control sub key
          If used Find to find any keys with the Driver of KORGUM64.DRV

          1. Thanks for the quick response. I only have 1 Korg device, the Korg Kronos. When I first ran the Korg MIDI driver Uninstall Utility, I found “Standard Driver [KRONOS] ” as “midi10” and “KORG KRONOS ” as “midi11”. After trying various registry changes, only the first one still shows up as “midi10” (the second is gone). I tried what you suggested and only found my original entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\0014\Drivers\midi\KORGUM64.DRV (with Name “Alias” and Data “midi1”. Doing the search, I found another entry under HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\PnP\CurrentControlSet\Control\DeviceMigration\Devices\USB\VID_0944&PID_0203&MI_03\7&377af7d&0&0003\Driver\Drivers\midi\KORGUM64.DRV which has an entry for “Alias” and “midi1”.This was the only other entry for KORGUM64.DRV, and the second one is not a Class as the first one is. Based on what I just found I do not see how to add the second (midi2) I have tried uninstalls and reinstalls but with no progress. Do you have any suggestions?

  2. To fix 32 bits applications like the Minilogue sound librarian, it is also necessary to duplicate midi stuff () in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 with “KORGUM64.DRV” value.

  3. Had the same problem, did the fix, KORG now on number 1 and 2 in the MIDI device list. But the two Korg devices still do not show up in Ableton Live or Midiox?! What did I miss?

  4. I dont understand this at all. When you say:

    “Open up Regedit and navigate to:


    You need to find a class with a name of Media so search for a value of “MEDIA” (Control – F).”

    Several items show up on the list but NONE OF THEM have anything to do with Korg. What you show on the screenshot looks nothing like what I see. This is with Windows 10, same exact setup as yours. Its like you skipped a few vital steps here because Im not seeing anything related to Korg on my end.

  5. Hi there,

    Great article!
    My solution was just totally uninstall KORG drivers, first from device manager, then program, reconnect hardware and use win generic drivers! (of course editor won’t work, but i don’t use it). Simple solution for people who are not familiar with registry and are willing to wait KORG fix!!

  6. I followed the procedure, but the alias now shows up in the Korg Uninstall utility as “Corrupted (KORGUM64.SYS”. It also still shows on midi13 as KORG nanoKONTROL2 as it did before.

    Any ideas ?

  7. hello there, ive did exactly what you tell but there is no results, my minilogue is now above 10, (placed in 2), i can use it on ableton but the librarian doesn’t recognise it.

Leave a Reply to Andy Milligan Cancel reply

Your email address will not be published. Required fields are marked *