This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 68%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZD%3C/text%3E%3C/svg%3E)
As a developer, I am working on a .Net project, which is a music listening development application. The first compromise I had to make is that the NAudio and DryWetMidi packages are only handled by Visual Studio with WPF 6.0.
The other, more critical, is a Windows 11 system issue. To create the Midi connection, I use the free software LoopMidi and LoopBe1, which are the only two software available in this category, and I also tried my tests with Bome Midi Translator, which is paid. I did my tests with two VSTs, the Korg M1 VST and the Korg Wavestation VST.
The problem is that the Windows 11 security packages not only disable the operation of midiLoops, but also make it impossible for the above VSTs to function normally. The above applications probably use Virtual drivers, and their operation will be blocked with the update.
wusa /uninstall /kb:5074105
After removing the latest security package, the loops and VSTs started working properly.
wusa /uninstall /kb:5077181
What is the solution, because I had to stop additional Windows 11 updates to make the above VSTs and drivers work properly?
My problem is that it seems that only these midi tools can be used worldwide: LoopMidi and LoopBe1,
Midi-OX. There are other paid applications, but they also work poorly. There is no paid MidiLoop type software that would solve my problem.
If you send the following SysEx "B0 20 04 C0 05" with Midi-OX, which would switch to 5 LSB bank and 6 instrument, to the VSTs in question, it will send an error message with insufficient memory if the security update in question is installed.
My final request would be :
Which paid application would solve this problem of mine? I would like to ask for an example from AI?
Unfortunately, I can't accept AI's answer because the update still blocks it, so the loopMidi virtual driver is not visible on the midi input, midi output page, in this case I would have to go back to Windows 10, which I can do until October of this year, or I can wait months, maybe years for a loopMidi driver update. The final solution might be to find an official, paid software that would solve the problem, but I don't know which one would be for Windows, although I asked the search robot AI, but I didn't get a specific answer to this question. So I would need a midi server driver, which Apple probably has? .. or you could give an answer to this solution? No?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 20%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPB%3C/text%3E%3C/svg%3E)
Hi Zsolt.
I don't know what's going on with the VSTs, as the update should not impact those. If you have more details there, please share.
However, for MIDI, we have some known issues with loopMIDI and loopBE if you have the new Windows MIDI Services stack enabled. It's not that it disables them, it's that they need to be started before the MIDI service has started, and also before any MIDI-using apps have been started. This is a bug.
Known issues and workarounds:
Pete
Microsoft
Hi ! Thank you for your answer, very kind.
I found what you described earlier, I applied the method with the following batch file:
start "" "./loopMidi.exe"
net stop midisrv
net start midisrv
In this case, servive has already set the midi input and output, and midiLoop has become visible, but if I send the native byte array with midi-OX to change the bank or card in the case of the above VSTs, it still sends an error message referring to the limits of the memory buffer, no matter how I set a larger memory stream to send. In Fruity Loops DAW, the arrival of the midi message is visible with an orange flash, so it has been sent, but probably it does not send sounds even when pressing the keys of the keyboard, if I remember correctly.
I would recommend Midi-OX for testing because I want to make a similar VS .NET C# application for myself. So I could do bank or card and instrument switching with the buttons on my Midi Keyboard in VSTs.
Please test the problem with the above byte code! Thank you!
MIDI-OX does indeed throw that error. However, PocketMIDI happily sends it. It may be because that's not actually SysEx, and MIDI-OX is treating that differently? It's also possible we have a bug in the 32-bit port of the service interface (MIDI-OX is a 32-bit app, pocket MIDI is a 64 bit app)
Pocket MIDI sending the message.
You did let Windows MIDI Services enable itself on your PC, right, without using any third-party tools like the vive tool?
I think Midi Service is already running by default, although as far as I know, it is not a midi connection server. Thank you, I will accept your answer tomorrow, once I have tested it. Thanks, Zsolt
Hi! Thank you very much for the answer, I solved my problem. You can start loopMidi with the batch file I provided above if it gets stuck at boot. This will start loopMidi, it probably runs differently because of the activated Midi Services. I was able to interpret the sent SysEx message with the Pocket Midi application, in my own program I have to formulate the forwarding of the midi message a little differently (outputDevice?.sendEvent(new midiEvents).. ). My VS .Net C# program is now fully functional, all that remains is to connect the midi keyboard. Thank you, Zsolt.
The issue you are experiencing with the MIDI loops and VSTs being blocked by Windows 11 security updates is likely related to the way Microsoft manages driver security and compatibility. When security updates are applied, they may include a blocklist for vulnerable drivers, which can inadvertently affect virtual drivers used by applications like LoopMidi and LoopBe1.
To resolve this issue while still keeping your system secure, consider the following steps:
Unfortunately, uninstalling security updates is not a sustainable solution, as it exposes your system to potential vulnerabilities. It's best to find a way to keep your system updated while ensuring that your development tools function correctly.
References:
