Fixing Korg USB Midi driver issues caused by the Windows 10 May 2019 Update
HTML-код
- Опубликовано: 14 окт 2024
- UPDATED 2023: • Fixing Korg USB Midi d...
UPDATED 2022 version of this video
• Fixing Korg USB Midi d...
UPDATE: Korg have new drivers
thedigitallife...
The Windows 10 May 2019 Update breaks Korg’s USB drivers causing DAWs not to be able to work with Korg devices. 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.
One solution is to completely uninstall the Korg drivers but if you don’t want to do that there is a fix.
In this video I walk you through the steps to fix the Korg driver issue. I have also written a blog post explaining how to fix it step by step.
Yess thank you. I upgraded from my old Kontrol49 to a NI Komplete Kontrol MK2 keyboard. When I plugged in my old Kontrol 49 to make sure it all works before selling it, it wouldn't show up in my list of MIDI devices. Went through this step by step and now it's up and running perfectly.
I chanced upon this video after spending all day trying to investigate why my Korg Microkey midi keyboard had stopped working after installing the Microsoft Spring Update yesterday. Your succinct solution worked perfectly, first time. Many thanks..., you've helped solve the problem I was having.
All the best, Rob.
Well damn, here it is 2021 and I was having this problem. I had gotten my nanokontrol studio to work as a mixer with Premiere before but after not using it some months I got nothing, the pc would not recognize the nanokontrol at all. I looked at literally every video and forum on the internet and tried everything all day until I came to this video. One tip off was that the Korg will only work in the first 10 midi inputs. I don’t know what sort of sorcery you’re doing because I never, ever would’ve been able to figure this out except for this video. This is truly a lifesaver since I’m doing a mix for a client tomorrow and without this I would have had no fader controls. Thank you thank you thank you for putting this video out, you deserve a medal.
Glad it helped you :) I know how frustrating it can be when its not working so I thought it may help others.
@@IanDixonTDL I seriously looked everywhere. Someone on a forum said your video helped them. The instructions for the nano are so bad and I’ve noticed different versions tell you to do different things. It’s totally trial and error anyway, but your solution saved the day!
Thank you for this. It is sad that Microsoft and Korg have to make things so difficult so that you have to search the internet for solutions and watch RUclips videos. Again thank you for posting this very helpful video.
Thanks a lot Ian !!! I love it when following such geeky instructions having no clue what I'm doing and the issue has just magically disappeared.
I have to say that I`m happy that the world still has people with good attitudes! Thanks for sharing!!!
Even with the latest drivers I still had to do this whole process to get Cubase to recognize my nanoKontrol2. I never would've figured this out. Thank you!
this man is the best, i´ll personally fight the people who had thumbed down this video
You are the man! Even with the new version of KORG drivers for W10 I wasn't able to make my Korg M50 work as a MIDI controller. Now is solved thanks to you.
You, sir, are GODDAMN SAINT! Now my Taktile 49 is back in action. Excellent pace and demonstration of the steps. Also, you're currently the top Google result for
korg usb midi driver windows 10 2019 not working". Cheers!
I'm using an ancient Kontrol49 and it wasn't showing up at all in the uninstall tool. After following your steps and adding the relevant string values to both NT folders i got it working. Both ports are showing up in the utility as "corrupted" but it works. Thanks!
Problem solved!
The updated driver from Korg still not working for me, this solution was the trick. Thank you so much!
You are a saint. Was tearing my hair out trying to fix this and yours was the only advice that worked!
Mate, you're a lifesaver. Thank you so so much for putting this extremely useful video up here. I wouldn't have had the foggiest what to do without it.
You're very welcome!
Thank you for taking the time to share this! Got it to work! One change, Drivers32 had midi1 through midi 9 already assigned, so i set the value data to the korg driver on midi 9 as it was assigned to something I don't use anymore. Now my daw recognizes it.
Glad it helped!
What do I do when I already have 1-9 assigned and still use all of them?
"THANK YOU" is not enough... I was about to install whole Windows again, fortunately I watched this video... I appreciate this effort 👍👏👏👏
Thank you so much for the fix! You'd think Korg would at least be on top of this, but even the updated driver failed to fix this. None of that matters, however, because it seems you've helped many others with this problem as well :)
Yup, driver update still fails to resolve this issue in 2022.
Holy crap, you are a life saver. Literally searched for hours to find the solution, which is this video. Thank you. When I look at the Uninstall utility the midi ports have moved to the right places, but the names are prefixed by the word "corrupt". I can still play the keyboard though.... unless that is because the system defaults to using the standard driver rather than the korg driver... hmmm
Well done Ian. I've problem solved the 10 midi device limit in the past to get my Korg Nano Kontrol 2 working but this time it had me completely stumped. Thanks for getting me out of a fix.
Glad I could help!
Dude, you saved my Korg Nanopad from the trash. Literally. Thanks man.
Glad I could help
Thanks a bunch! This fixed my issue too. And thanks to Korg too for thinking every musician has only one device connected.
Hi, in case this solution doesn't work for you. Just try rollback windows 10 to it's previous compilation. WORKED PERFECT for me. :D
thanks for the guide. I just got a wavestate and it came with 1.04 firmware installed, just the process of updating the firmware is a challenge in itself
10/10 THANK YOU!! My Korg KP3+ wasn't get recognized in Ableton and now it is!! Easy Peasy.
Glad it helps!
I REALLY Appreciate you taking the time to do this. I went through it last year when migrating to a new PC and couldn't remember how to do it. At time 4:14 in the video, the string value (AKA Driver Name) that you say you copied before I cannot find in the video. The driver/driver name I downloaded from Korg is "Drv Tools(115_r41e)". Is that the correct NAME to use as the STRING VALUE in the WindowsNT/Current Version Registry Entry?
As I'm playing with the Windows Registry, the most sensitive, delicate thing ever put in an Operating System, I just want to make sure I'm not about to crash my entire system. Thank you again for taking the time to do this.
Sincerely,
Bill
Im also stuck, do let me know if you figure it out.
You're a hero. Such an easy fix.
One thing worth mentioning is that "midi1", "midi2", etc. might already be present. You can just replace the value found there.
This is so much to have to do , Never had any other issues like this w any of my other boards. I love my kronos 2 but this has me almost thinking of selling it to swap for something more modern easy to link & setup. The new windows updates you have to do this for.
Dude, you're awesome, i wasn't able to get my nanokontrol 2 to work even thought now there's a korg midi driver that's supposed to work with may 10 2019 windows 10 update, now that's in the past thanks to you!
Glad I could help!
Thank you so much. This literally saved me for a gig this weekend. You're a life saver!
Great video! Will this fix work in windows 11? I'm so frustrated with these korg drivers!
Absolutely brilliant! I know this video is a few years old now but....I mean...absolutely brilliant, cheers!
Also what if you already have a midi1 - midi9 ? I tried to do 0 & 10 that did not work & I don't want to change the already midi1 to the korg driver do I? Will that not mess up something from my other boards? At the moment 1-9 are controlled by wdmaud.drv it says
I have the same situation. Anyone got an idea?
this helped my DAW recognize my Korg device when it wouldn't otherwise. THANK YOU
You absolute legend, this was really clear and easy to follow and fixed the problem perfectly. Thank you!
Only vid that has actually resolved the issue (in my case, at least). Would've been nice to have found it 3 years ago
Damn this NanoPad has been lying in my drawer for at least 8 years since it hasn't been able to connect. And now finding this video fixed it. Thanks a lot!!
Thank you very much. I was having a huge problem with my korg nanokey2. I even bought a new cable, but it wasn't that. I downloaded the drivers again but couldn't fix the problem. Your video saved my life. A huge thanks from Sao Paulo - Brazil.
i am crying! you can't imagine the good you've made to me! you saved me A LOT! thanks!
Thanks!
@@IanDixonTDL what happens if midi 2 does not show up
Absolute legend! Thanks so much for this! I needed my nanoKontrol for a church service in two days and I was freaking out when I couldn't figure out why it wouldn't work. Almost brought a new one haha
Thank you so much! Haven't been able to get any work done all week because I was trying to figure out this problem. Your solution worked like a charm!
Thanks so much for this. I just hit this problem with the latest Win10 update and my Korg Odyssey, and this fixed it (I had to edit the midi1 entry, since all the entries 1-10 were already in the registry), but it worked.
Glad it helped
Hello, I'm from the future. Korg is still up to their midi nonsense. You and your video have saved the world. Thank you!!!
Glad I could help!
Dude, you are THE BEST!!! Many thanks from across the pond. It worked perfectly. Cheers :)
And used this instructions again to find and reconnect my drum machines driver, Ian you are a savior, thanks for sharing.
Thank you so much! I was going crazy trying to get it to work after the Windows 10 update.
Great one! But what if all midi entries from 1 to 9 are already taken by other devices I have? 😔 Help!
Thank you, Thank you, Thank you! You solved the problem and I would never have figured it out myself. I cannot thank you enough!
This fix worked perfectly for my Kross2, I just used the one midi1 :)
Life saver! My KORG devices were in MIDI 23 and MIDI 24. This fixed it.
thank you very much. Worked on Korg Microkey Air 37. Madness that Korg only can work on midi between midi1-midi10. Also Windows should be ashamed for causing this issue on a update
still useful today, man i thought i was truly doomed, thank you so much!
Yo, I was skeptical, not gonna lie, but it worked perfectly! Thank you man!
1903 messed up so many things for audio production. Latency is the biggest showstopper still, and since even gamers are affected, one would guess that a fix is coming soon. But it's already 2 months. Unbelievable. Anyways, you did an amazing job, though I have no idea how you found the culprits. It's like typing the right lottery numbers in the registry for me :) But it worked.
I find myself watching this video every six months. Thank you.
Amazing that this problem still exists....I have watched this video three times a year since it was released.
Thank you VERY much, that works for me! Anyway, Korg - please update your driver....
This fixes the problem with the midi port being under 10 but it still doesn't work for me, neither system updater nor librarian. Updater says "Midi out port is not exist : minilogue xd" and librarian says "failed to open the midi port".
Man, I can't thank you enough. Yours is the for real only method that works.
Glad it helps!
I am from Hong Kong and my KORG B2 wont use with my pc for Kontakt, now it works, Brillant Ian, thank you so much.
Glad I could help!
The problem is that now of Mai 2021 after several new WIN10 Updates since the publishing of this video nothing seem to work to make the Korg Wavestate work with the Sound Librarian or even connect! I can not even record using USB Midi in Music Maker due to "missing driver" and "device not connected" and can´t use the Librarian! Nobody seems to write about that problem though. Why is that? Everyone using a Mac or old Win OS?
Great Stuff, this also applies to the new october 20h2 update. Thank you very much works perfectly!!
Thank you very much. Saving in korg playlist. (Happy to pay someone well to do this.)
Hi All. I was just made aware of this (I work in Windows, on MIDI and other things). It doesn't have anything specifically to do with the May update. But it looks like maybe Korg is using the DirectMusic API (which was deprecated, and does have 10 "slots" in the registry). Outside of that, there is no limit to the number of devices you can have attached to a PC.
What happens here is when a device connects, it uses a slot. Then if you disconnect it and plug into another USB port, if the device doesn't have a USB serial number, it looks like a new device, and takes another slot. This is probably happening as part of update as devices are re-enumerated.
I'll talk with Korg.
I found that the latest Korg drivers work much better than I when I originally posted the video
@@IanDixonTDL Are you running into a 10 device slot limit, still?
I was, but after installing the new Korg drivers everything is working on 1809.
@@IanDixonTDL Thanks Ian. So you reverted back to 1809 from 1903 as well?
I had the problem after going to 1809 after reverting back to 1803 and installing the new driver I went to 1809 > 1903 without any issues.
Thank you sir ! For me there is last one problem, everytime I shutdown the Minilogue I need to recreate all those things in the regedit, so to be more simple I just exported a .reg file, then everytime I start to music I launch it. Anhyway thanks again, I was buying the Minilogue for two reason, one for the sound and the other one because is not so expensive and you can control Omnisphere very well with it ! It was so frustrating to search forever how it's works, but you save my life !
That is a strange one, Windows must be re-creating the USB each time.
You are a legend in my book for this ! Thanks so much
Thanks for this solution. My Korg keyboard works again after following the instructions from the video and the written instructions you also provided.
You saved my life, again!! (after windows updates). Thank you so much, you are the real mvp!
Glad it helped!
Brillant, man! I had an issue with Korg SQ-1. And I just deleted its whole driver folder in reg and it helped!
Glad it helped
After 4 years i still coming back! Thanks a lot! Don't know why korg doesnt fix this
I found you can use the built-in Windows drivers and ditch the korg drivers
Thanks, not sure if a new windows update has made this problem happen again was using nanokey 2 happily then it suddenly stopped working. This fixed it.
Absolutely brilliant! THANK YOU THANK YOU THANK YOU!!!!! This was killing my studio day
This worked great to get my Korg Kross 2 communicating with the Win10 editor. Thank you so much for making this vid!
Glad it helped!
Not all heroes wear capes! Thanks you, I would never ever figure that out
Nice one Ian.
Your fix has got me the most results so far.
I've got it so my DAW can now see my nanoKontrol2 in both Machine Control/Mix Mode and CC Mode
BUT
The KORG KONTROL Editor cannot see it.
It says that the nanoKontrol2 in not connected ...
That means that I cannot send my own CC settings to it.
CC control of Plugin parameters is why I got it in the first place ...
Why such a leading company as KORG can't update the software for the products it sells is beyond me.
But thanks Ian for bringing me This far.
Diving back in to see if reinstalling the Korg Kontrol Editor will make the connection now that this Alias busuness is in place.
Nope.
I tried reinstalling the Editor with All the other USB MIDI devices unplugged but the nanoKontrol2 still doesn't show as 'connected' in the Editor.
I've emailed Korg, I wonder if they have a fix ...
I wonder if they'll reply ...
Apparently I don't really Need Korg Kontrol Editor as Studio One can remap all the CCs coming in from nK2.
It does mean I have remove whichever instance I'm NOT using from the External Controllers list though.
Then reinstantiate it whenever I want to change to the other ...
Could be worse ...
Naughty Korg for not keeping their software up to date though.
If you have 32 bits applications like Prologue or Minilogue sound librarian, don't forget to duplicate the fix in the WOW6432node key in the registry.
Good point!
@@IanDixonTDL Hi could you explain this step in detail please? I can get one of my minilogue entries to move to slot 1 but there is another that refuses to move from slot 14...
@@sihaz1969 I have written it down in case that helps thedigitallifestyle.com/w/index.php/2019/04/23/fixing-korg-usb-midi-driver-issues-in-windows-10-may-2019-update/
I did just that, and now I have my midi keyboard working in the notation program again.
Many thx for this! :-)
Fantastic! Why can't /won't Korg sort this out?! Anyway, well done, much appreciated.
Easier if you make a batch for us to download.
Also I can't find the Korg mdi driver uninstall utility.
A link for download will be apreciated.
End of 2020, latest Version of Cubase, Windows and the Korg Driver => still an issue. Thanks for helping me fix this :)
Very useful. thank you. Just a supplementary question, what happens to all the other drivers? I have more than 10 devices, will they still work? TIA
yes, its only Korg devices that have the 10 channel limitation
@@IanDixonTDL Aah, OK. I didn't want to lose other (more important) things by doing your registry "hack".
Hello Ian, 1 final, I hope, question. Do we carry out your procedure with the Korg stuff connected or not connected?
Thank you for the video! I just wonder what will happen to all the other non-Korg entries in the list? I think I need them all, don't I? Will they simply shift up, and work as they did before? Or will some of them not be detected by my DAW anymore in case they shift beyond #9?
Edit: so I wanted to try this, but I already have midi1 - midi9 in my registry...
They should shift down and still work
@@IanDixonTDL Thanks Ian.
This video gave me enough clues to get my microKey 25 up and running again - thank you
When i open Driver32 there are already midi1 to midi9 available with the wdmaud.drv as a data. ?? Do i remove them or replace the existing midi1 with KORGUM64.DRV
I got the same problem. Did you find a solution?
When i went into the uninstall utility for the korg, it showed that the korg was connected but damaged so i removed it. as for the midi channels i removed them. I think the fact that i had the automap installed before it filled out all the channels so i uninstalled it, reinstalled the korg first then automap later and seems to work now.
@@bja2317w got same problem,midi 2 connected,midi 3 corruoted
Worked like a charm! Thank you Mr. Dixon you are a genius!
Worked brilliantly! Thanks!
It's September 2021 and this tutorial just saved my bacon. Thank you so much. And also, holy hell I'm pissed at korg at making me go through this....
Thank you Ian I did not have to go digging about in the registry (thankfully) but when I opened the uninstall app I found 2 instances o thr Nano Kontrol drivers installed on different ports.
Uninstalled one and my daw recognized the Kontrol2.
It can be problematic around updates but I am getting better at solving the issues thanks to you.
Cheers.
Colin.
Have thrown the towel in on this, it has stopped working again.
Spent way too long trying to get it working.
I do not know who is at fault Korg or MS but it is not mind numbing hassle trying to get it functioning yet again.
This is not the first time I have had thee issues but it is certainly the last I am off to find something a bit more reliable and less time consuming.
Any recommendations?
Thanks for your help.
I would say Korg need to make their devices work on more than the first 10 channels. Did you get the latest driver?
@@IanDixonTDL I got the latest driver but the editor kept saying that it couldn't open the port.
I am using Studio one and it works fine in Mackie mode controlling volume and transport but I wanted it to run cc data for my VIs.
Needed something reliable so I bought a Subzero mini control and it works straight out of the box.
Shame the Korg is so fragile when we have software updates.
Just wanted to say thanks for the help getting my Korg Krome keyboard working after a Windows 10 update
Worked for me for my NanoControl2 and Kronos X. Thanks much, good job!
Thanks a lot for this! Working for Electribe 2s.
I have no words to thank you.
Thanks a lot.
THANK YOU THANK YOU THANK YOU!!!!!!!!!!!!!!!!!!! Korg still doesn't have an answer to the issue and I forwarded the tech support this video. Thanks again Ian!!!
Good move!
Two months trying to fix this. THANK U SO MUCH
Glad it helps. What version of the Korg drivers are you using?
@@IanDixonTDL I was using r49 and now im using r20, just to try to fix this. But the problem was at the midi port as you explain in the video. I use padKontrol and when i connect my Arturia Keylab, sometimes crash everything and i have to do the regedit thing again i dont know why
Btw, thanks for sharing this solution, im using FL20 and it works very well!!
THANK YOU SOOOO MUCH ALSO AFTER ALL OF THIS; IF STILL NO WORK ADD THIS STRING AS WELL (*Credits to JIM On Korg App Message Boards )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. Make sure to copy same driver in string details like video stated. THANK YOU SO MUCH AGAIN. 😭😭😭 Korg PadKontrol Back
This was vital to me as well.
@@varnishyourboard yeah before it didnt stay when the computer got turned off
Does this work for the Korg Wavestate too? Can’t connect it with the Korg Updater and the Korg Sound Librarian
it should do
Even after doing this the same way, it didn't figure right. Like at 5:08 where I should be looking at the identical file, right? But I don't even have up to the "0021 and 22" files as shown here in the video at the marked time. Also, afterwards, at first, the computer recognized the Kronos and the driver. But I used this process so I could hopefully do the subsystem firmware update, which I am overdue for anyway. But either way, doing that with the "606" update, when I go to do the update, I get and error message: "MIDI out port is not KORG MIDI-DRIVER: KL Virtual Out-8".
I'm very confused and bewildered by it all. If I can't do any of this, I can't have the computer recognizing the Kronos with the Nanopad2 and Nanopad key connected to it, or use Korg Kontrol Editor, Kronos editor or Karma Kronos What do I do next?
kudos from Brazil. Man you saved my life. Thanks!
Works perfectly and very easy to follow. Thank you, thank you!!!
I set up midi1 per your instructions. That allowed the Kronos to show up as both an input device and an output device in Cakewalk. I can play MIDI out to the Kronos now.
However, when I play the Kronos keyboard, Cakewalk doesn't receive any MIDI, despite being set to Kronos Omni. I tried Kronos MIDI ch 1 and that doesn't work either.
Is this why you put a midi2 entry? One port for send and one for receive? Or have I configured my keyboard wrong? I assume Kronos sends keyboard performance out on MIDI chan 1. If I turn Local Off, I hear nothing, and if I record in Cakewalk, no notes are recorded.
I didn't have any problems installing my Yamaha Montage drivers, nor my Yamaha Motif XS drivers. What's with Korg that their driver installations are broken?
It worked for my minilogue! thanks a lot for the tutorial!
You're welcome!
First of all, thanks for uploading this video. Has anyone had this problem with Korg PA600? I'm still trying to figure out why my PC recognizes my keyboard (it's even listed on audio devices with the name "KORG PA600") but I can't use it as an MIDI input device on Cubase
Hi Ian, I have a question. What's the best way to record a video with winmr? A few updates ago the view port was smooth and now it's choppy and 1903 didn't change this. The record function output video is really choppy with the view port on or off while trying to record, but I think haven't tried putting it in 60hz mode while recording yet. I have a 2700x and rtx2070. I feel like it's a MS software issue they need to fix with an update.
I have only used the built in recording in WMR. I wonder if a video driver is causing the issue?
@@IanDixonTDL I have updated the video driver a few times I think since I noticed the view port is choppy.... it's a software thing for sure... the view port used to be really smooth
the only other way of recording a smooth video that comes to mind would be an hdmi splitter and a recorder of the headset signal and then editing that so it's not sbs video
Is the recording bad if you record from WMR menu?
@@IanDixonTDL yes that's where I record from I mean it looks as choppy as the viewport.... but even that shouldn't be choppy... it didn't used to be