How to block KB5077181 from installing on Windows 11

[DevonB]

The February security update has a bug that will prevent MIDI ports from initializing if your interface initializes them after boot. I use the iConnectivity MioXL with rtpMIDI, which 100% does break my setup. I did uninstall the update, but in Microsoft's infinite wisdom, it forces you to install it AGAIN anyway. I now paused updates for 5 weeks, and hope the 'fix' is supposed to be out end of March. Anyone know how to stop patches from being installed permanently so I don't have to keep going through this on Windows 11 25H2?

Devon

[BertKoor]

Hey Google, How to block KB5077181 from installing on Windows 11?

https://www.guidingtech.com/how-to-stop ... nstalling/

[DevonB]

Hey Google, tell Bertkoor this tool no longer works on Windows 11 25H2, and the tool is deprecated as well.

I know you've been very helpful to me and many others on here for PC stuff, so just giving you a hard time.

This tool no longer works. I had read previously it no longer works, but I gave it a try anyway. (I've already had the update installed, I just uninstalled it now for the second time, I have updates paused until April 12th, and this Security hotfix does not come up in the list of updates I can hide with this tool.) So I'm looking for other 'trusted' solutions. Not too pleased with this forced security update when it clearly breaks my machine. Why they have to include the MIDI 2.0 update that's been in the works for years with a security update is baffling.

Devon

Hey Google, How to block KB5077181 from installing on Windows 11?

https://www.guidingtech.com/how-to-stop ... nstalling/

[DevonB]

Going to leave this here in case someone else runs into exactly what I did, and the whole reason I posted -

Aha, further searching found why the method you posted wasn't working; if you have Updates Paused, it will NOT find KB's that had previously been removed. You HAVE to unpause updates in order for it to find the security update, no matter what method you use. You need to be REAL quick though.

Here's what finally worked for me -

• Be ready to run the app wushowhide.diagcab
  Unpause the updates in Settings / Windows Update (this AUTOMATICALLY starts the install of the update! Ack!!!)
  Run wushowhide.diagcab, and Hide it immediately.

Mine got stuck at 4% install, and eventually failed, and is now on the hide list. From what I'm also reading, this method still doesn't always work on everyone's system, which is also what I had read.

Devon

[BertKoor]

Afaik the article I linked to contained various alt solutions.

[stefani ss]

Are you running Windows 11 Pro by any chance?
If you are, you can use the Group Policy Editor (gpedit.msc) to stop the automatic updates.
Go to: Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update -> Manage end user experience, and then configure the automatic updates exactly how you want them (like notifying you before downloading/installing).

[Psychlist1972]

Preview fixes for rtpMIDI, loopMIDI, loopBE and also for inMusic (AKAI, RANE, m-audio, etc.) drivers are available on our Discord server

https://aka.ms/mididiscord

Pete
Microsoft

[fateamenabletochange]

I had problems with my old Korg MS-20 controller, so used the Korg Uninstall Tool which sure enough showed it having a port number higher than 0 - 10. Deleted some lower, I thought, redundant entries to force the Korg to a lower number and had all my midi disappear from Reapers midi in/out list, including the RME Interface ports. Yikes.

Uninstalled all the relevant drivers.
Vi-control net had a thread with a link to a SDK Runtime and Tools package, installed and ran midifixreg from a Terminal window.
https://aka.ms/MidiServicesLatestSdkRun ... _Directx64

All good again.

[Jim Roseberry]

Scenarios like this (PC and Mac) are why you should have Automatic Updates disabled.
If you want a smoother end-user experience, be a late adopter of OS updates.
This gives the industry a chance to find/resolve issues... and you don't have to beta-test.

[Pictus]

The February security update has a bug that will prevent MIDI ports from initializing if your interface initializes them after boot.(...)

Check https://vi-control.net/community/thread ... ar.170478/

[Pictus]

...

[Psychlist1972]

I had problems with my old Korg MS-20 controller, so used the Korg Uninstall Tool which sure enough showed it having a port number higher than 0 - 10. Deleted some lower, I thought, redundant entries to force the Korg to a lower number and had all my midi disappear from Reapers midi in/out list, including the RME Interface ports. Yikes.

Uninstalled all the relevant drivers.
Vi-control net had a thread with a link to a SDK Runtime and Tools package, installed and ran midifixreg from a Terminal window.
https://aka.ms/MidiServicesLatestSdkRun ... _Directx64

All good again.

Support is on https://aka.ms/mididiscord . Please be sure to fully read the #start-here post that invite lands you on.

Those Korg driver installers/uninstallers hose MIDI on Windows, as they always have. I have a tool that can fix that once you completely and fully uninstall the driver from Windows. (Instructions on the Discord server). As of this moment, there's a newer version than the one in the link above, which fixes both the 32 bit app and the 64 bit app locations.

Korg's post instructing users to no longer use their USB drivers:
https://www.korg.com/us/news/2026/0312/

Pete
Microsoft

[fateamenabletochange]

Thanks very much Pete.