KORG app Help Center

USB MIDI is not recognized on Windows 10.

Old KORG USB-MIDI driver may not work correctly due to Windows Update.Please use the latest Windows 10 KORG USB-MIDI Driver.

 

[Update on July 30, 2019]

As you may notice, Korg has released a USB-MIDI driver that supports Windows 10 May 2019 Update (V1903) . Please download and install the latest driver.

https://www.korg.com/support/download/product/1/285/

 

 

Was this article helpful?
2 out of 9 found this helpful

Comments

  • Avatar
    Michael Leary

    Cannot get N1 to work with Windows 10

    Comment actions Permalink
  • Avatar
    Dieter Libotton

    Yeah, same here the microkorg won't show in neither ABLETON, neither FL STUDIO, neither RENOISE. I was always happy with my microkorg. I hope KORG fixes this soon! Damn windows updates all the time! They mess up a perfect setup.

    Comment actions Permalink
  • Avatar
    TatuRecords

    i m having problens too. same with monologue and windowns 10. USB Midi Driver is not recognized

    Edited by TatuRecords
    Comment actions Permalink
  • Avatar
    Albert Diaz

    Here too. Windows 10 won't detect my nanokontrol2. There are no other midi devices in use (clean windows install). I'm running the latest korg midi drivers. Windows won't even detect a new device (I tried several usb cables). Please, help

    Comment actions Permalink
  • Avatar
    RG K

    yes it is after a windows update - why fix something when it works perfectly OK ?
    Microsoft repair your mess !!!!!!!!!

    Comment actions Permalink
  • Avatar
    Micah Groom

    My PC wasn't loading up the microkorg either. I was able to dual boot into mac os and got it to work. If you just want to use the microKORG soundeditor, just use mac os, maybe barrow a friends mac if you don't have one.

    Comment actions Permalink
  • Avatar
    aritosteles

    I'm trying to use my Microkey on Windows 10. Setup gives an error message saying it cant find drvtools.msi. The first thing the installer does is to decompress that file, but later it cant find it... I don't know what to do. Is there any workarround for this?

    Comment actions Permalink
  • Avatar
    Bob Dzerk

    I have installed DrvTools_1_15_r25e on Windows 10 Pro 1709 build 16299.785 and then restarted the system. The KORG NanoKONTROL2 shows up in the Device Manager, but is not recognized by MIDI-OX 7.0.2.372, or Ableton Live 9.7.2.

    UPDATE: I have fixed the problem by following the instructions in this YouTube video https://www.youtube.com/watch?v=s9OfwDr8oYQ 

    Edited by Bob Dzerk
    Comment actions Permalink
  • Avatar
    Fils Aime Evens

    hey , guys
    somebody know about korg is50 driver how can i get the driver please

    Comment actions Permalink
  • Avatar
    Mike Wurth

    Bob Dzerk's comment had my fix. Following the instructions in this video was all it took. https://www.youtube.com/watch?v=s9OfwDr8oYQ

    Comment actions Permalink
  • Avatar
    Taras

    Can't use my padKONTROL as of Windows 10 build 18362.116.

    I have tried everything listed in this thread. The Korg apps can see the padKONTROL as a USB device, but no music apps can see it as a MIDI device.

    Comment actions Permalink
  • Avatar
    Peter Nikolas Hust

    So NEITHER my NanoKey 2, or my PadKontrol are being recognized by FL Studio 20. I have tried everything i can think of...I deleted all of the old drivers, etc., tried everything that comes up in a search...for weeks now. I have a cheap Casio Keyboard which i bought from the thrift store...it works no problem. every. single. time.

    so anybody have any ideas??? pretty please!
    thanks

    Comment actions Permalink
  • Avatar
    Peter Nikolas Hust

    ps, i already have followed the steps in the video of the link posted above

    Comment actions Permalink
  • Avatar
    Jim A (Cnuut)

    nanoKONTROL2 -Windows 10 build 18362.116
    Not working,I have tried uninstalling/installing many times.
    :(

    Edited by Jim A (Cnuut)
    Comment actions Permalink
  • Avatar
    Gunther Schumann

    Hi,
    since the Windows 10 Spring 2019 update my MicroKey2 Air Keyboard isn't working.
    Neither in bluetooth nor in USB mode.
    When using bluetooth it can be found but is only listed as "paired" in the windows bluetooth manager not as connected. It doesn't show up under the Korg Control app and is not recognized by any daw. Reinstalling the "DrvTools_1_15_r29e" didn't help. BLE drivers are also not working. Following the fix in the youtube video I can't find the registry entries "midi1" and "midi2" which are supposed to cause the Microkey to be listed on entry 11, thus causing not to be recognized by the Korg Control software. Help, anyone?

    Comment actions Permalink
  • Avatar
    David Helgesen

    this video is the only thing that helped me (not the same as posted over).
    https://youtu.be/18SLcnbqwaI

    Have to change regedit two places, and remember to restart pc after the changes. Then check in Uninstall Korg USB-midi Device software if it's between midi1 to midi10. If not use midi2 or midi3 and so on in regedit.

    This solution works for everybody especially them who have updated to the latest Windows 1903 build

    Edited by David Helgesen
    Comment actions Permalink
  • Avatar
    Paul Fogarty

    spoke to korg, they are doing new drivers.. BUT how I got it working.. uninstall anything they give, with ccleaner etc. .. device manager > sound / controllers etc. right click uninstall drivers... then right click "uninstall device"... unplug the keyboard from usb.. I do run ccleaner again rego scan to clear any rogue entries. when you put it in a USB port again, it should use the windows own driver.. which will work until they get better drivers sorted.

    Comment actions Permalink
  • Avatar
    Phil Marker

    You have to be careful with CCleaner; it can do more damage to your PC. I experienced it myself a couple of times. https://helpdeskgeek.com/free-tools-review/why-you-shouldnt-download-ccleaner-for-windows-anymore/

    Comment actions Permalink
  • Avatar
    Paul Downes

    I have lost my Krome midi functionality also since the latest Win 10 update!! :(

    Comment actions Permalink
  • Avatar
    Jim Friedeck

    Updated to latest Windows 10 version, PadKontrol works, Kronos doesn't.

    Less and less of a Microsoft fan every day.

    Comment actions Permalink
  • Avatar
    David Helgesen

    Again this video fixes the problem after Windows update:
    https://www.youtube.com/watch?v=18SLcnbqwaI&feature=youtu.be

    Comment actions Permalink
  • Avatar
    S a m

    The Korg m50 VST Editor doesnt work anymore :(

    Comment actions Permalink
  • Avatar
    S a m

    Tried doing everything in that video. MIDI worked but the VST didnt It just says (hardware not found)

    Comment actions Permalink
  • Avatar
    Paul Downes

    Sam I have the same with the Krome Editor after following the video....but that's no big issue as I don't use it! :)

    Comment actions Permalink
  • Avatar
    David Helgesen

    Isn't Korg m50 VST Editor a software? If so why do you think that a video that fixes midi issues has the answer to a software error? Start a new thread for that issue

    Comment actions Permalink
  • Avatar
    S a m

    Because it stopped working after the 1903 windows update and says hardware midi not detected. It’s a driver issue

    Comment actions Permalink
  • Avatar
    Peter Nikolas Hust

    HELOOOO? KORG???? ANYBODY HOME?! NO ONES KORG MIDI DEVICES ARE WORKING SINCE THE LAST WINDOWS UPDATE!! PLEASE HELP! Im close to selling two of my korg keyboards because they are useless at the moment...

    Comment actions Permalink
  • Avatar
    Jim A (Cnuut)

    Hi, I had problems with getting my stuff to work following the video, then I found somewhere that you also need to be setting the midi1 (or whatever number) in "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32" after that it worked for me.

    Comment actions Permalink
  • Avatar
    S a m

    Omg it works after that!! Thanks Jim

    Comment actions Permalink
  • Avatar
    Grenat Vibe

    it worked for me either after I added the last string value as Jim said

    Edited by Grenat Vibe
    Comment actions Permalink

Please sign in to leave a comment.