KORG USB-MIDI Driver can not be used with Driver error on Windows 10. KORG app October 06, 2020 21:35 Follow Please use the latest Windows 10 KORG USB-MIDI Driver. Facebook Twitter LinkedIn Comments Michael Leary August 01, 2018 20:21 driver fails for N1 in Win 10 Comment actions Permalink José Antonio Valladares January 27, 2019 20:02 En Windows 10, no me funcionaban correctamente los controladores MIDI de Korg. Concretamente con el pedal Korg Pandora y el Nanokontrol2, la última actualización de Windows 10 no me los reconocía, con anteriores SO como Windows 7 no tenía problemas, incluso utilicé en Windows 10 una máquina virtual con Windows 7 para utilizar el pedal Korg Pandora. El problema era mío, tenía los puertos MIDI del 1 al 10 ocupados por controladores corruptos de antiguas instalaciones y Windows 10 me instalaba los dispositivos en puertos como el 17, 19,... y en esos puertos no me reconocía los dispositivos Korg. SOLUCIÓN: 1) Instalé la última actualización de controladores MIDI USB de Korg para Windows 10. 2) Utilicé el instalador de dispositivos que incluye, y obviamente aunque me instalaba pe. el Nanokontrol2, después no lo reconocía. 3) Al ejecutar el programa de desinstalación incluido en el paquete de controladores, me di cuenta que los puertos MIDI del 1 al 10 tenían controladores corruptos de anteriores instalaciones y el Nanokontrol2 lo había instalado en el puerto 17. NOTA: PARA QUE FUNCIONEN LOS DISPOSITIVOS KORG, TIENEN QUE ESTAR INSTALADOS EN LOS PUERTOS DEL 1 AL 10. 4) Desinstalé todos los controladores corruptos que había en los puertos MIDI del 1 al 10, también el puerto 17 del Nanokontrol2, y reinicié el ordenador. 5) Con el programa instalar dispositivo, instalé el Nanokontrol2 que me lo puso en el puerto MIDI 1, y después el pedal Pandora, este me lo puso en el puerto 2. Reinicié el ordenador y al utilizar el software tanto del Nanokontrol2 como del pedal Pandora los reconoció y funcionaron bien, sin ningún problema. Espero que sirva mi experiencia a los usuarios de Korg dado que en un principio creía que los controladores no eran compatibles con la última actualización de Windows 10 y el problema era quitar antes los controladores corruptos de antiguas instalaciones que no dejaban instalar los dispositivos en los puertos MIDI del 1 al 10. Otra cosa en la configuración de los controladores para 32, 64 bits ó ambos, yo elijo "ambos" dado que hay software que va a 32 bits. Un saludo. Edited by José Antonio Valladares January 29, 2019 07:58 Comment actions Permalink Corrado Casoli February 01, 2019 10:03 I own a Korg Minilogue. I tried a lot of times to update it with its kmupdate exe file but my pc said that there is no MIDI port or any MIDI device. I unistalled and installed again the latest version of USB-MIDI driver from the Korg site but it doesn't work. Can anybody pls help me? I have Windows 10. Hope to hear and solve my problem. Thx. Corrado Comment actions Permalink José Antonio Valladares February 01, 2019 10:34 In Windows 10, Korg MIDI controllers did not work properly for me. Specifically with the Korg Pandora stomp and the Nanokontrol2, the last Windows 10 update did not recognize me, with previous OS as Windows 7 had no problems, I even used a Windows 7 virtual machine with Windows 7 to use the Korg Pandora stomp. The problem was mine, I had the MIDI ports from 1 to 10 occupied by corrupt controllers of old installations and Windows 10 installed the devices in ports like 17, 19, ... and in those ports I did not recognize the Korg devices. SOLUTION: 1) I installed the latest Korg USB MIDI driver update for Windows 10. 2) I used the device installer that it includes, and obviously even though I installed it. the Nanokontrol2, later I did not recognize it. 3) When executing the uninstall program included in the driver package, I noticed that the MIDI ports from 1 to 10 had corrupt drivers from previous installations and the Nanokontrol2 had installed it on port 17. NOTE: TO WORK THE DEVICES KORG, THEY MUST BE INSTALLED IN PORTS 1 TO 10. 4) I uninstalled all the corrupt drivers that were in the MIDI ports from 1 to 10, also the port 17 of the Nanokontrol2, and I restarted the computer. 5) With the program install device, I installed the Nanokontrol2 that I put it in the MIDI port 1, and then the Pandora stomp, this put it in port 2. I restarted the computer and using the software of both the Nanokontrol2 and the Pandora stomp recognized them and they worked well, without any problem. I hope that my experience will serve Korg users because at first I thought that the drivers were not compatible with the last update of Windows 10 and the problem was to remove the corrupt drivers from old installations that did not allow to install the devices in the ports. MIDI from 1 to 10. Another thing in the configuration of the drivers for 32, 64 bits or both, I choose "both" since there is software that goes to 32 bits. A greeting. Comment actions Permalink Wittawat Keawcharoen December 22, 2019 14:59 Hi, My MicroKey2 61 MIDI device cannot be found when I use Reason. However, it seems to work just fine with other piano program, in my case it is Everyone Piano I tried updating to the latest Driver from this thread but this doesn't solve my problem. Could you please help? Comment actions Permalink José Antonio Valladares December 22, 2019 21:19 Hi, With the uninstall application, remove the failed installations you have on ports 1..10, and install the MicroKey again, if Reason does not recognize you, you will have to configure the DAW. Comment actions Permalink Wittawat Keawcharoen December 22, 2019 21:22 Hi, Thanks, I found exactly that. I fixed it by editing the Registry, I think the link explaining it is somewhere around here. Comment actions Permalink Steve Athey January 07, 2020 01:44 Hi I am having some similar issues that are not related to the windows 10 update. I have found one reference to editing the registry that has not solved my issues. All my Korg devices are within the 1st 3 midi entries The only midi Entry greater than midi9 is Bome Virtual midi port on midi10 (I think this is associated with Komplete OR my Komplete Kontrol). My installed devices are Korg Triton Extreme, NanoKontrol 2, and the minilogue. All are working fine as midi devices in Cubase 9.5. As far as I am aware I am using the latest Korg drivers but they may not be installed correctly? I think the main problem is that they show in "korg midi driver uninstall utility" as being corrupted. midi0: Corrupted (Korg Triton Extreme) midi1: Corrupted (Korg nanoKONTROL2) midi2: Corrupted (Korg minilogue xd) I have tried uninstalling these and reinstalling the drivers. I have also removed non korg devices that I did not recognise Any ideas how to fix these corrupted entries? Or just to get the sound librarian to work. Thanks in advance Steve Comment actions Permalink Marco Ruiz July 01, 2020 02:07 Steve, i have the same problem, any solution please Comment actions Permalink Corrado Carena July 03, 2020 21:32 Hi Marco and Steve, I had the same problem : Corrupted (Korg minilogue) and could not use the Sound Librarian software. Than I discovered my Minilogue was not updated with the last system (2.0), so i did uploaded (https://www.youtube.com/watch?v=pS0JhMmjeb4), and then EVERYTHING WAS FINE AND WORKING !!! the minilogue was recognised by the Sound Librarian ! hope this is useful for you ! Corrado Edited by Corrado Carena July 03, 2020 21:32 Comment actions Permalink krishna kumar July 16, 2020 07:40 Hi, I too am facing a "Corrupted Driver" issue. Am connecting G1 Digital Piano to the PC (Windows 10, latest update 1909). When I install latest driver (.35), the piano gets connected to midi1, but shows as "corrupted". When I install earlier driver version (.20, .21), the piano gets properly connected. But to midi12! Hence not recognised by the DAW. The slots midi0 to midi9 are empty, in midi10 and midi11, Realtek Audio interface is connected. In above case, I also tried to set Alias in Registry to midi1. It does show the piano against midi1 but as "corrupted". Am not able to figure out where is the issue. Request your help. Many thanks. Comment actions Permalink KT July 26, 2020 13:54 Hi Krishna, I'm having the same problem as you - "corrupted" installs with the latest driver, after the most recent Win 10 update. Everything worked fine before. Did you manage to resolve it? Comment actions Permalink Zuzu injian August 19, 2020 03:11 so i just got my midi usb cable and plugged it into my korg triton elite. I go into my daw and it detects the cable but no noise even though i turned off local control on the keyboard but then went into the korg midi uninstaller and it was there in spot 10. I then did as i saw in a video and went into the registry to move the midi up to the first spot (also there was nothing in the other spots and no matter what i did i couldnt get it into the first spot). as far as i can tell i got it to the first spot but it doesnt show up as the keyboard or as korg but shows up as corrupt usb. I am looking for an answer because no matter what i did i could not get it to make a sound in the daw. I also have the latest korg drivers. Pls help Comment actions Permalink krishna kumar August 19, 2020 03:58 Hi KT, No i could not find a solution. Purchased an audio interface and connecting through that! Comment actions Permalink Koz Myk October 05, 2020 22:34 Do Korg ever respond to these Forum questions? I see a lot of people with problems but no replies from Korg themselves? Do they perhaps email the persons posting directly ? I bought a Korg nanoKontrol2 for some extra knobulation with in my DAWs. I wasted two working days trying to get it to function in any way at all. Win10 i7 3770K 4.2 GHz 32GM RAM - DAWs - Studio One, Ableton Live, Cakewalk (don't laugh). Of all the DAWs Studio One is the only one that actually sees that the nanoKontrol2 is actually there But it sees no MIDI ports to Send and Recieve with. Win10 Device Manager sees that it is there and reports that it is functioning properly, which it plainly Is Not. I've tried installing, uninstalling , reinstalling using the DrvTools(115_r38e).exe download. I wondered if a roll-back were possible but the download page does not appear to link to older driver versions even though it lists them ... Comment actions Permalink Koz Myk October 06, 2020 21:35 PARTIAL SUCCESS After following instructions from this user made YouTube video and editing the Registry to add 'Alias' entries for Driver locations; I have managed to get the nanoKontrol2 to operate in DAW Mode with Studio One. Nice one Ian Dixon. 👍 https://www.youtube.com/watch?v=18SLcnbqwaI However, I need it to operated in CC Mode if it is to perform the function for which it was purchased. I now note that it DOES send CC data when set to CC Mode, But the KORG KONTROL EDITOR does Not see it as being connected so I cannot select which CC's are being sent. I've put in a request to Korg Tech Support UK . Hopefully they may come up with a solution. As a DAW controller it is working quite nicely; except that the Next/Prev Track buttons don't appear to be having an effect in Studio One.(The DAW Preset is the same for Studio One as for Cubase) , Next test - Ableton Live But without the Editor functioning properly I can't get the CC use out of it that I bought it for ... Comment actions Permalink Please sign in to leave a comment.