USB/MIDI Issues with KB5074105

Question

USB/MIDI Issues with KB5074105

Ethan Ornelas 0

I am currently having USB and MIDI issues with the KB5074105 update. Previously I was able to connect multiple different MIDI devices to RekordBox, Serato, AKAI, Ableton Live, and other music apps. Now all these apps do not recognize ANY of the MIDI devices. After reading other users issues, I attempted to uninstall the update through the Updates tab in the settings, and through the command prompt with no success. Is there any workaround for MIDI devices or to uninstall the update?

Jamie Fox 15 Reputation points

2026-03-09T09:06:10.91+00:00

Serato or VDJ are not the issue here. The specific update that is the root of it all is KB5074105. This update introduced MIDI 2.0 and that is causing severe issues with InMusic USB drivers. The solution I have found that works consistently is to uninstall updates KB5074105, KB5077181 & KB5077241. Then you pause all windows updates so they don’t reinstall. This discussion & solution has been known to VDJ users for a while. Apparently, Microsoft (Pete Brown) is working on a fix with InMusic and MIDI 2.0. The fix is supposed to be out later this month (or longer for the InMusic driver fix)

Also, The InMusic USB driver IS an issue as well. The driver InMusic uses is ‘Audio+MIDI’ and now that Microsoft is updating MIDI 2.0, the Rane driver is just not up to the task and a bit outdated. The total solution is for InMusic to modernize their driver AND for Microsoft to fix their buggy MIDI 2.0 driver. AKAI is a InMusic product and its driver is conflicting with the new MIDI 2.0.

2 answers

Your answer

Jamie Fox 15 Reputation points

2026-03-09T09:06:10.91+00:00

Serato or VDJ are not the issue here. The specific update that is the root of it all is KB5074105. This update introduced MIDI 2.0 and that is causing severe issues with InMusic USB drivers. The solution I have found that works consistently is to uninstall updates KB5074105, KB5077181 & KB5077241. Then you pause all windows updates so they don’t reinstall. This discussion & solution has been known to VDJ users for a while. Apparently, Microsoft (Pete Brown) is working on a fix with InMusic and MIDI 2.0. The fix is supposed to be out later this month (or longer for the InMusic driver fix)

Also, The InMusic USB driver IS an issue as well. The driver InMusic uses is ‘Audio+MIDI’ and now that Microsoft is updating MIDI 2.0, the Rane driver is just not up to the task and a bit outdated. The total solution is for InMusic to modernize their driver AND for Microsoft to fix their buggy MIDI 2.0 driver. AKAI is a InMusic product and its driver is conflicting with the new MIDI 2.0.

Answer 1

Apostolos Polymenakos 0

In my case, I get duplicate entries for my DJ controller in djay Pro. I don't have KB5074105 but I do have KB5077181 installed. Unfortunately, it's more than 10 days since this update was installed and there's no way to uninstall it now.
I have tried this pre-release fix https://github.com/microsoft/MIDI/releases/tag/winrt-midi1-timestamp-fix but it didn't fix my problem.

Any ideas?

Jamie Fox 15 Reputation points

2026-03-22T19:28:08.68+00:00

There is another way. KB5077181 IS the problem. Basically you'll have to go back to the old MIDI stack. This is done with ViVeTool. I will kind of re-post the procedure that I pisted at Rane and VDJ...

I will say MS does not support this officially nor is it a guarantee that it will continue to work after updates over time, so use at your own risk.

you will need ViVeTool to do this and disable the MIDI 2.0 feature by itself. Found here: https://github.com/thebookisclosed/ViVe/releases/download/v0.3.3/ViVeTool-v0.3.3.zip

I extracted this to c:\vive, but you can extract it to wherever you like.

After you extract ViVeTool, navigate to its directory and open a Power Shell terminal (as admin) in it.

The command is: .\ViVeTool.exe /disable /id:58988972

Restart your machine.

This worked as expected on my machine. Not the exact fix I wanted but at least I won’t have to pause updates until InMusic addresses the problem on their end. This will disable the MIDI 2.0 feature alone. Hope it helps.

The video describing this can be found here: https://www.youtube.com/watch?v=iuu5eXQIoOg&t=148s Look at time index 2:30.

Just FYI… I got a lot of the info from Pete Brown’s MIDI 2.0 Discord group. I just put into a procedure that could be understood more clearly. The issue for the Rane Four is that its drivers are audio+MIDI. After testing against my Rane Four, the second method in the #start-here part of Pete’s Discord group does not work. That method involves uninstalling the Rane Four drivers and using the in-box windows MIDI drivers with KB5077181 re-enabled. Without the Rane drivers, the Rane audio devices do not show at all. I can also confirm that the only KB that had the MIDI 2.0 is KB5077181.

So, where does that leave us? I can confirm that the ViVeTool method works well but for how long it will is the mystery. Let’s hope Rane (InMusic) quickly comes up with a firmware or drivers that fixes this. I know Pete is in touch with InMusic about this very issue. I would imagine the new firmware and/or driver they make will be class-compliant with windows new MIDI. I have read that MS may blacklist the InMusic drivers if they don’t fix them. So, yea, they’ll fix them soon.

Lastly, Pete Brown nor Microsoft cannot and will not officially support this method (ViVeTool). As such, he will not answer questions concerning this. I am thankful he did publish the info he did anyway. He realized there was a problem and helped us. I, however, will answer what I can about this and my research.
Apostolos Polymenakos 0 Reputation points

2026-03-23T16:10:54.61+00:00

First of all, thanks a million for your response! And I totally understand the disclaimers.

I tried what you suggested above, restarted but it didn't fix it in my case. Quering with the ViVeTool I can see id:58988972 is disabled but my issue is not fixed.

My controller is a Hercules Inpulse 500 which uses a specific Hercules ASIO driver. I guess it is also audio+MIDI. Shouldn't Hercules also provide an updated driver to support MIDI 2.0?
Jamie Fox 15 Reputation points

2026-03-24T00:44:39.1033333+00:00

I read that today one VDJ user has a Hercules MK2 and the ViVeTool worked on it. Before the ViVeTool method, we disabled 3 Windows 11 updates to make our controllers work. Those were KB5077181, KB5074105 and KB5077241. I have learned that the ViVeTool method disables ONLY the MIDI 2.0 feature and not all of KB5077181. There may be other features in those updates that are interfering with your controller drivers. Also, if you can uninstall all of those updates, be sure to pause windows updates or they will reinstall themselves automatically. The 'duplicate entries' is a sure sign that you have the new MIDI 2.0/1.0 service on your system... Simply stopping the new MIDI 2.0 service does not work (I already tried that). Use this MIDI tool from Microsoft to be sure that service is not running on your machine. You can get that here: https://github.com/microsoft/MIDI/releases/download/enablement-checker/midicheckservice_x64.zip

Also, if that does not work then ask Pete Brown (MS software engineer on MIDI 2.0) in his Discord group found here: https://discord.com/channels/980245825202552942/980255706655645736

He's the one who helped me out with the ViVeTool suggestion so I may pass it on to others. He is very responsive to questions and genuinely wants to help. You also may find that there is another workaround for your controller in this group.
Apostolos Polymenakos 0 Reputation points

2026-03-24T08:37:15.97+00:00

Unfortunately it is now way past the 10 days that Microsoft allows for uninstalling updates, so there's no way for me to uninstall KB5077181.
However, using the midicheckservice tool that you shared, it says that wdmaud2.drv is not in the registry and "The new Windows MIDI Services stack is not functional on this PC". So I'm beginning to think that my issue may not be related to the new MIDI 2.0 services but to djay Pro software instead.

Anyway, thanks again for your input, it was helpful.
Jamie Fox 15 Reputation points

2026-03-24T12:59:02.3366667+00:00

No problem. Yes, Djay pro could be the issue... I've never used that software. If you have either Virtual DJ or Serato, you can test that theory. You had mentioned the Hercules driver is audio+midi. Makes wonder just how old these drivers really are. At any rate these new MIDI issues will cause these manufacturers to finally update them to be class complient. I look to see driver updates to be in the second half of the year. This will cause DJ softwares to update to accommodate these new drivers.

Answer 2

KB5074105 is not mentioned in the available context, so only general, supported USB/MIDI troubleshooting steps and known MIDI-related fixes from earlier Windows versions can be provided.

For USB/MIDI devices suddenly not being recognized by multiple apps after an update, the supported approaches are:

Re-run Windows Update to re-detect drivers
After a major or cumulative Windows update, some device drivers may fail to migrate correctly. Running Windows Update again can reinstall missing or incompatible drivers:
- Open Settings → Windows Update.
- Check for updates and install everything offered (especially driver and optional updates).
- Restart and test MIDI devices again.
Reinstall the audio/MIDI device drivers
If devices disappeared or stopped working, reinstalling the driver stack can restore functionality:
- Open Device Manager.
- Under “Sound, video and game controllers” and “Audio inputs and outputs” (and any vendor-specific MIDI entries), right‑click each affected device and choose Uninstall device.
- Disconnect the USB/MIDI hardware, restart Windows, then reconnect so Windows or the vendor installer can re-add the drivers.
Check for vendor driver/firmware updates
For RekordBox/Serato/AKAI/Ableton controllers and interfaces, install the latest Windows 11–compatible drivers and firmware from each vendor. This is required if the Windows update changed USB/MIDI behavior and the vendor has released compatibility fixes.
Apply known MIDI-related hotfixes (older systems only)
If any affected machines are actually running Windows 7/8/8.1 or Windows Server versions listed in the context, there are specific MIDI fixes:
- For USB 2.0 audio devices with MIDI out that stop working or whose MIDI ports disappear, install the usbaudio.sys hotfix that raises the MIDI packet size limit from 256 to 512 bytes.
- For Windows 8 where midiInGetNumDevs and related MIDI APIs return incorrect device counts after hot‑plugging USB MIDI devices, install update rollup 2862768.
- For Windows 8.1/Windows 7 where MIDI sound is intermittently lost over USB‑to‑MIDI cables, install the relevant hotfix/update (e.g., update rollup 2919394 for Windows 8.1/Server 2012 R2, or the Windows 7/Server 2008 R2 hotfix).
If uninstalling the update fails
When Settings and command‑line removal of a specific update fail, supported options are:
- Ensure all dependent updates are removed in the correct order (if applicable) and that the update is not superseded and locked in the current build.
- Use System Restore (if a restore point exists from before KB5074105) to roll back the system state, which also removes the update and its driver changes.
- If none of the above works and MIDI remains unusable, back up data and perform an in‑place repair install or reset of Windows, then reinstall apps and drivers, and test MIDI before reapplying optional updates.
Temporary workarounds
While investigating or waiting for a fix:
- Test MIDI devices on another Windows machine that has not yet installed KB5074105 to confirm the hardware is working.
- If available, use a different connection path (e.g., a different USB port, powered USB hub, or a different USB‑to‑MIDI interface) to see if the driver stack enumerates differently.

If the problem is a regression specifically introduced by KB5074105 on Windows 11 and persists after driver reinstalls and Windows Update, the next step is to report it via Feedback Hub with full repro details (devices, DAWs, and exact build) so it can be addressed in a subsequent cumulative update.

References:

Share via

USB/MIDI Issues with KB5074105

2 answers

Your answer