Repository navigation
32 bit apps like MIDI-OX and VSThost and ROLI dashboard may not work after KORG or other registry driver removal/reordering tools are used #943
Description
Third-party tools and driver uninstallers like those designed for KORG products can mess up the registry. The midifixreg tool currently fixes only the location used by 64 bit apps, not the one used by 32 bit apps.
There are many 32 bit apps out there, but these are known to be impacted
- MIDI-OX
- ROLI Dashboard
- Novation Components
- Much older apps like the EDIROL PCR editor
- Korg KARMA and related apps
32 bit registry location:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
64 bit registry location:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
For 32 bit apps to see MIDI ports, the following entries must exist in the 32 bit location
midi REG_SZ wdmaud.drv
midi1 REG_SZ wdmaud2.drv
These can be manually created by right-clicking in the registry location and choosing new->String Value and then modifying the value afterwards (it's a 2-step process: create an empty value, then modify the value to provide the required wdmaud*.drv
The midifixreg tool needs to be updated to also fix this registry location.
Activity
Psychlist1972 commentedon Mar 28, 2026
Updated rc4
midifixregwith the 32 bit registry location in addition to the 64 bit registry location.Psychlist1972 commentedon Mar 29, 2026
Updated midifixreg tools are here, and will also be in the rc4 SDK. These handle both locations (32 bit apps and 64 bit apps locations) in the registry, as well as restoring the
MidisrvTransferCompletevaluecdto the location where you extracted this to..\midifixreg.exeand follow the prompts.Do not just double-click this to run it. You must run it from inside an Administrator command prompt (search "command" and then choose "run as administrator")
midifixreg-2026-03-28-arm64.zip
midifixreg-2026-03-28-x64.zip
tosugawara commentedon Apr 1, 2026
Pete Brown (@Psychlist1972)
I tried to use this updated tool.
But, I don't know why, it seems to have no 'midi' entry on
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32on my PC.I tried to run midifixreg (0328ver.) on my environment.
displayed below after running midifixreg.exe:
Still there was no 'midi' entry.
I manually created 'midi' entry (with no data) and run midifixreg, the registry is fixed successfully.
displayed below after runninng midifixreg.exe:
If there is no 'midi' or 'midi1' entry, should it be created manually first? Does not this tool care for this case?
Psychlist1972 commentedon Apr 1, 2026
Toshihiro Sugawara (@tosugawara) the new version of the midifixreg tool also updates the 32 bit registry location for you, so you don't need to manually add the entry.
I've updated the above comment to make that more clear.
Pete
Microsoft
tosugawara commentedon Apr 2, 2026
Pete Brown (@Psychlist1972)
Thank you for your reply. I understand that the tool of new version cares both 32 bit and 64 bit registry.
As described in my former post, I downloaded "midifixreg-2026-03-28-x64.zip" from DL link in your post, and ran the tool of the version on my environment below:
OS version : Windows 11 Pro 24H2 26100.8037
-> "midi" entry was not added in 32-bit registry.
Then, I also tried to do on another environment at the same condition that there was no "midi" entry in 32-bit registry:
OS version: Windows 11 Pro 25H2 26200.8117
-> "midi" entry was added successfully.
Do you have any idea about the difference between these cases?
By the way, for 64-bit registry, I confirm that it run successfully in any cases.
Psychlist1972 commentedon Apr 4, 2026
Toshihiro Sugawara (@tosugawara) I wouldn't know without understanding what you have installed/uninstalled etc.
I'm also not sure what you mean by ""midi" entry was not added". Are you saying it wasn't present before you ran the tools, or that the tool failed to add it? If the latter, did you try a second time just to make sure you didn't hit something other than "y" when you were prompted to confirm making the change?
Screenshots will help
Pete
Microsoft
Psychlist1972 commentedon Apr 4, 2026
the rc4 midifixreg has both 32 and 64 bit patching, and the rc4 MIDI Settings app also has an option to fix these entries, so marking this fixed in rc4
The underlying issues with third-party tools will still exist, but I expect that to become less of an issue over time, especially now that KORG has released a news story asking customers to stop using their USB drivers on Windows.
Pete
Microsoft
tosugawara commentedon Apr 6, 2026
Pete Brown (@Psychlist1972)
32 bit registry before running midifixreg rc4, there is no "midi" :
after running midifixreg, with typing "y":
32 bit registry after rebooting PC (it is the same status as the first screen shot):
It seems that midifixreg attempted to create "midi" registry and to update value to wdmaud.drv, but no update happened.
=====
32 bit registry with creating "midi" empty entry manually:
after running midifixreg with typing "y":
32 bit registry after rebooting PC:
In the case, it seems that updating is successful.
We also hope so. For users after uninstalling KORG driver but having problems which is caused by our tools, being available to use this "midifixreg" tool is very useful to solve the registry problem easily.
Thanks.
Toshihiro Sugawara
KORG Inc.
Psychlist1972 commentedon Apr 6, 2026
Thanks for the update Toshihiro Sugawara (@tosugawara)
I'm not sure what is causing the
midientry to be removed after a reboot. But now I understand what you were seeing and I will keep an eye out for this. We're also looking at forcing these two entries to the required values automatically on each reboot.The impact of not having a
midientry withwdmaud.drvis that the in-box general MIDI synthesizer will not be available to apps.Pete
Microsoft
Psychlist1972 commentedon Apr 12, 2026
Updated tools and info in Settings app now available.