Sign In:     

Forum: VirtualDJ Technical Support

Topic: New windows kb5079473 same MIDI problems
Hi, after installing the windows 11 update kb4079473 the midi connection has many problems again.

VirtualDJ run, plug in controller, VDJ don’t find MIDI of the controller.
VirtualDJ start after plug in the controller, it works
Plug out the controller and VDJ is running, VDJ complete freeze.
 
Posted 5 days ago @ 7:37 pm
 Best Answer Der MIDI 2 Windows FIX by DJ RUHMER ist fertig und wurde bereits auf mehreren Rechnern erfolgreich getestet.

Hintergrund:
Mit dem Preview-Update vom 29.01.2026 hat Microsoft die neuen Windows MIDI Services eingeführt. Dazu gehören unter anderem MIDI 1.0 / MIDI 2.0, Shared Ports, Loopback, App-to-App-MIDI sowie weitere Performance- und Systemänderungen.
Warum traten die Probleme ausgerechnet am vergangenen Wochenende so massiv auf?
Am 10.03.2026 wurde das kumulative Sicherheitsupdate KB5079473 verteilt. Dieses übernimmt Inhalte und Änderungen aus vorherigen Updates und hat das Thema damit auf vielen Systemen gleichzeitig relevant gemacht.
Viele DJs und Musiker waren dann wenige Tage später mit frisch aktualisierten Rechnern im Live-Einsatz – genau dort wurden die Probleme mit bestimmten Controllern und Treibern sichtbar indem sie die Verbindung zwischen DJ Software und Controller oder Akai Geräten verloren.
Ich habe deshalb ein kleines Tool erstellt, das dabei hilft, die betroffenen Updates zu erkennen und – sofern möglich – wieder zu entfernen bzw. den passenden Weg zur Bereinigung zu finden.
Wichtig:
Die Nutzung erfolgt auf eigene Verantwortung, da jede Windows-, Treiber- und Controller-Konfiguration unterschiedlich ist.
Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X
Hinweis:
Je nach Windows-Einstellung kann beim Download oder Start die Meldung erscheinen, dass die Datei aus einer unbekannten Quelle stammt.
Wenn ihr selbst betroffen seid oder Kollegen kennt, die aktuell Probleme mit Rane- oder anderen Controllern haben, dürft ihr den Link gern weitergeben.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The MIDI 2 Windows FIX by DJ RUHMER is now finished and has already been successfully tested on multiple systems.

Background:
With the preview update released on January 29, 2026, Microsoft introduced the new Windows MIDI Services. This included MIDI 1.0 / MIDI 2.0, shared MIDI ports, loopback, app-to-app MIDI, as well as additional performance changes and bug fixes.

Why did so many problems suddenly appear last weekend?

On March 10, 2026, Microsoft released the cumulative security update KB5079473. This update carried forward content and changes from previous updates and effectively pushed the issue onto many more systems at once.
A few days later, DJs and musicians went out on gigs with freshly updated laptops — and that is when the controller and driver problems became very obvious.

To help with this, I created a small tool that can detect the affected Windows updates and, where possible, help remove them or guide users through the cleanup process.

Important:
Use this tool at your own risk, since every Windows, driver, and controller setup is different.

Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X

Please note:
Depending on your Windows settings, you may see a warning that the file comes from an unknown source.

If you are affected yourself, or know DJs / musicians currently having problems with Rane or other controllers, feel free to share the link.
[ selected best answer by DennYo Beats on Tue 17 Mar 26 @ 9:48 am ]
 
This works fine, but I comes the next cumulative update kb5079473. And the problems are back.
Stop update windows os not the best option of long time.

Windows updates are cumulative. The next update include the previous update.

Big problems have users with a new windows installation. You can’t go back to the February update.
 
I'm with you brother but pausing windows updates is the only option until Microsoft and InMusic fix their problems. Microsoft came out and said that fixing the MIDI 2.0 won't help us because the InMusic drivers are partially the problem. They are not class compliant. Rane and Denon (InMusic) will have to come out with new drivers to help us. It sucks but we are caught between Microsoft and InMusic. What I'd like to see is Microsoft give us the ability to return to the previous MIDI AND still be able to update Windows. Rane (InMusic) support has been silent on this so far. Updates from MS are cumulative and that is why we must pause until they get this sorted out.
 
Drei understand this. I hope I can help an other guy. He installed Windows clean and use Denon. He has much trouble. :(

By the way my writing problems on the first post was with the Reloop Mixtour.
Reloop drivers have also problems.
 
Yeah, even though that update is not a "preview", they stuck the same MIDI breaking nonsense that the other preview updates had. Luckily I still had a restore point that had my Hercules workarounds in it. ALL windows updates are now paused on my machine until Microsoft puts out a MIDI version that takes care of this.

Busting on Microsoft is kind of a cliche', so I usually don't do it. But this issue was a real doozy. People have suffered significant financial losses from having to cancel gigs. Lord knows how many of those gigs were wedding receptions.
 
I have a Denon MC7000 and had this problem. Since EA BUILD 9209 (2026-03-01), it also works with the latest Windows 11 Pro
Version 25H2 Build 26200.8037 Windows Feature Experience Pack 1000.26100.300.0
 
I use my old, trusty Hercules RMX at home for streaming because it physically takes up no space. I haven't had a club gig in a month, so I haven't had my Traktor S4 MK3 connected to see if that's affected.
 
Der MIDI 2 Windows FIX by DJ RUHMER ist fertig und wurde bereits auf mehreren Rechnern erfolgreich getestet.

Hintergrund:
Mit dem Preview-Update vom 29.01.2026 hat Microsoft die neuen Windows MIDI Services eingeführt. Dazu gehören unter anderem MIDI 1.0 / MIDI 2.0, Shared Ports, Loopback, App-to-App-MIDI sowie weitere Performance- und Systemänderungen.
Warum traten die Probleme ausgerechnet am vergangenen Wochenende so massiv auf?
Am 10.03.2026 wurde das kumulative Sicherheitsupdate KB5079473 verteilt. Dieses übernimmt Inhalte und Änderungen aus vorherigen Updates und hat das Thema damit auf vielen Systemen gleichzeitig relevant gemacht.
Viele DJs und Musiker waren dann wenige Tage später mit frisch aktualisierten Rechnern im Live-Einsatz – genau dort wurden die Probleme mit bestimmten Controllern und Treibern sichtbar indem sie die Verbindung zwischen DJ Software und Controller oder Akai Geräten verloren.
Ich habe deshalb ein kleines Tool erstellt, das dabei hilft, die betroffenen Updates zu erkennen und – sofern möglich – wieder zu entfernen bzw. den passenden Weg zur Bereinigung zu finden.
Wichtig:
Die Nutzung erfolgt auf eigene Verantwortung, da jede Windows-, Treiber- und Controller-Konfiguration unterschiedlich ist.
Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X
Hinweis:
Je nach Windows-Einstellung kann beim Download oder Start die Meldung erscheinen, dass die Datei aus einer unbekannten Quelle stammt.
Wenn ihr selbst betroffen seid oder Kollegen kennt, die aktuell Probleme mit Rane- oder anderen Controllern haben, dürft ihr den Link gern weitergeben.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The MIDI 2 Windows FIX by DJ RUHMER is now finished and has already been successfully tested on multiple systems.

Background:
With the preview update released on January 29, 2026, Microsoft introduced the new Windows MIDI Services. This included MIDI 1.0 / MIDI 2.0, shared MIDI ports, loopback, app-to-app MIDI, as well as additional performance changes and bug fixes.

Why did so many problems suddenly appear last weekend?

On March 10, 2026, Microsoft released the cumulative security update KB5079473. This update carried forward content and changes from previous updates and effectively pushed the issue onto many more systems at once.
A few days later, DJs and musicians went out on gigs with freshly updated laptops — and that is when the controller and driver problems became very obvious.

To help with this, I created a small tool that can detect the affected Windows updates and, where possible, help remove them or guide users through the cleanup process.

Important:
Use this tool at your own risk, since every Windows, driver, and controller setup is different.

Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X

Please note:
Depending on your Windows settings, you may see a warning that the file comes from an unknown source.

If you are affected yourself, or know DJs / musicians currently having problems with Rane or other controllers, feel free to share the link.
 
 Selected as best answer
DJ Ruhmer wrote :
Der MIDI 2 Windows FIX by DJ RUHMER ist fertig und wurde bereits auf mehreren Rechnern erfolgreich getestet.

Hintergrund:
Mit dem Preview-Update vom 29.01.2026 hat Microsoft die neuen Windows MIDI Services eingeführt. Dazu gehören unter anderem MIDI 1.0 / MIDI 2.0, Shared Ports, Loopback, App-to-App-MIDI sowie weitere Performance- und Systemänderungen.
Warum traten die Probleme ausgerechnet am vergangenen Wochenende so massiv auf?
Am 10.03.2026 wurde das kumulative Sicherheitsupdate KB5079473 verteilt. Dieses übernimmt Inhalte und Änderungen aus vorherigen Updates und hat das Thema damit auf vielen Systemen gleichzeitig relevant gemacht.
Viele DJs und Musiker waren dann wenige Tage später mit frisch aktualisierten Rechnern im Live-Einsatz – genau dort wurden die Probleme mit bestimmten Controllern und Treibern sichtbar indem sie die Verbindung zwischen DJ Software und Controller oder Akai Geräten verloren.
Ich habe deshalb ein kleines Tool erstellt, das dabei hilft, die betroffenen Updates zu erkennen und – sofern möglich – wieder zu entfernen bzw. den passenden Weg zur Bereinigung zu finden.
Wichtig:
Die Nutzung erfolgt auf eigene Verantwortung, da jede Windows-, Treiber- und Controller-Konfiguration unterschiedlich ist.
Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X
Hinweis:
Je nach Windows-Einstellung kann beim Download oder Start die Meldung erscheinen, dass die Datei aus einer unbekannten Quelle stammt.
Wenn ihr selbst betroffen seid oder Kollegen kennt, die aktuell Probleme mit Rane- oder anderen Controllern haben, dürft ihr den Link gern weitergeben.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The MIDI 2 Windows FIX by DJ RUHMER is now finished and has already been successfully tested on multiple systems.

Background:
With the preview update released on January 29, 2026, Microsoft introduced the new Windows MIDI Services. This included MIDI 1.0 / MIDI 2.0, shared MIDI ports, loopback, app-to-app MIDI, as well as additional performance changes and bug fixes.



Why did so many problems suddenly appear last weekend?

On March 10, 2026, Microsoft released the cumulative security update KB5079473. This update carried forward content and changes from previous updates and effectively pushed the issue onto many more systems at once.
A few days later, DJs and musicians went out on gigs with freshly updated laptops — and that is when the controller and driver problems became very obvious.

To help with this, I created a small tool that can detect the affected Windows updates and, where possible, help remove them or guide users through the cleanup process.

Important:
Use this tool at your own risk, since every Windows, driver, and controller setup is different.

Download:
https://cloud.ruhmer.net/index.php/s/FAnXZbbe4TfFo9X

Please note:
Depending on your Windows settings, you may see a warning that the file comes from an unknown source.

If you are affected yourself, or know DJs / musicians currently having problems with Rane or other controllers, feel free to share the link.


its not in english. How can we choose what to do
 
its not in english. how can we choose what to press
 
“I will create an English version tomorrow.”
 
/!\ As we can't verify what this tool really does and contains, Atomix Productions can't be responsible for its use.
 
DennYo Beats wrote :
This works fine, but I comes the next cumulative update kb5079473. And the problems are back.
Stop update windows os not the best option of long time.

Windows updates are cumulative. The next update include the previous update.

Big problems have users with a new windows installation. You can’t go back to the February update.


I try to re install win 11 but now vdj go to crash..
 
DJ Ruhmer wrote :
“I will create an English version tomorrow.”


Thx! Since my native language is Dutch, I mostly understood and thus used the tool just now, will test with my Rane One Mk1 tomorrow to check if it worked.
 
Before I post this, 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.

1. 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
2. I extracted this to c:\vive, but you can extract it to wherever you like.
3. After you extract ViVeTool, navigate to its directory and open a Power Shell terminal in it.
4. The command is:
.\ViVeTool.exe /disable /id:58988972


5. 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.
TY Pete for the heads up!
 
djcel wrote :
/!\ As we can't verify what this tool really does and contains, Atomix Productions can't be responsible for its use.


Tool description / clarification

This tool is not a patch for VirtualDJ, Serato, or any controller firmware.
It is a small Windows utility designed specifically to help users identify and remove certain Windows updates related to the recent MIDI 2 / Windows MIDI Services rollout, where compatible removal is still possible.

What the tool does:

checks the local Windows update history

checks installed hotfixes

checks relevant package information via Windows servicing tools

compares that information against known MIDI-related update chains

offers removal of detected updates where Windows still allows deinstallation

provides guidance for Windows Recovery / “Uninstall latest quality update” if normal removal is no longer possible

can optionally help users disable Windows Update temporarily to avoid reinstalling the same problematic updates immediately

What the tool does not do:

it does not modify VirtualDJ

it does not modify Serato

it does not patch drivers

it does not flash controller firmware

it does not inject code into DJ software

it does not change audio routing inside DJ applications

it does not claim to “fix” the underlying inMusic driver compatibility issue itself

Its purpose is only to help affected users identify the Windows updates involved in the issue and, where still possible, roll them back at their own risk.

The tool is intended as an emergency support utility for users affected by the current Windows MIDI / inMusic controller conflict — not as a modification of DJ software.

Here is a slightly shorter version for a forum reply:

This tool does not modify VirtualDJ or any DJ software.
It is only a Windows-side utility that checks installed Windows updates, identifies known MIDI-related update chains, and offers rollback where Windows still allows it.

It does not patch drivers, firmware, or VirtualDJ itself.
Its only purpose is to help affected users deal with the recent Windows MIDI / inMusic update issue.
 
Anybody problems in combination with the Pioneer FLX-10 controller??
 
The FLX-10 does not appear to be affected. Seems most Pioneer controllers are not affected
 
Due to popular demand, a tool is now also available in English. Additionally, there is a video explaining why the problems exist, since when they have been occurring, and what the proposed solution looks like. The tool is demonstrated and explained, and the link to the tool can be found in the first comment below the video.
https://www.youtube.com/watch?v=jOsw30YBCWk