Delete and clean up "used" MIDI ports/channels

Often, old virtual MIDI cables (e.g., from uninstalled programs) remain and "use up" ports that are no longer needed.
Here's how to clean them up properly:

1. Delete old virtual MIDI ports

CoolSoft VirtualMIDISynth: Open the configurator → "MIDI Devices" → remove unused ones.
https://coolsoft.altervista.org/en/virtualmidisynth

MIDI-OX / MIDI Yoke: Under "MIDI Devices", deactivate the ports or uninstall the entire tool.
www.midiox.com

2. Remove hidden / "ghost" MIDI ports (very important!)

Many ports remain in Windows after uninstallation but are simply invisible.
Method A – With MIDI-OX (easiest option)
Download and start MIDI-OX.
Menu → “Options” → “MIDI Devices”.
Switch to “Show all devices including disabled/ghost” (or similar).
Select all grayed-out (disabled) and no longer needed ports → “Remove Device”.

 

I'm using Windoze 10. Yeah, I remembered that I originally ditched the SL because of strange behaviour, but I don't remember how I solved it. Anyway, the S61 has no issues with Midiremote, so I'll assume that there's something wrong with the k/b. And yes, I have noticed that once a port is used by one script, it disappears from your menu choices.

 

I hear you, but I've had this computer for almost ten years, so there's zero chance of me doing things in the order you suggest.

 

Thanks, but how do I go back to correct this without uninstalling things? I did notice that there were several midi ports named MIDIIN2, but they had stuff like (SLMKII) or (TAPCO) after them in the name. It's difficult to understand why the behaviour you speak of is allowed to go on, plus that you can't go directly to the surface editor and change the ports.

 

How to solve the infamous Windows 10 MIDI device renaming issue

Every now and then Windows try to be smart where there is absolutely no need. One notable mention is USB device mapping (and naming).

The symptom: You open up a project in your DAW only to discover you MIDI controller changed its name to something like 2 - Badass Controller and you must reassign your device mapping (left alone all your channels inputs)

This behavior is not new, dating back to Windows XP at least.
To me it happened on Windows 10 / Cubase, after I changed my studio desk layout and rewired all devices through a high-speed USB hub. My Novation Impulse 61, previously labeled Impulse, suddenly became 2 - Impulse.

https://medium.com/@stickgrinder/ho...ws-10-midi-device-renaming-issue-9aa793fa9f0a

Say hello to USBDeview

This little freebie by NirSoft is one of those tools you expect to be included in every OS right out of the box. It allows you to list — and manage! — all USB devices Windows encountered, even in the past.

Press enter or click to view image in full size

You can easily spot two Impulse keyboards in the list. One is attached, the other is not.
So without further ado, here is the procedure to fix everything:

• Download USBDeview from the official page (mind to get 32 or 64 bits depending on your OS version).
• Unplug the devices that is causing the problem (in my case it was the Impulse but I decided to also clean the records for the Keystation so I unplugged both).
• Start USBDeview by executing the .exe file in the archive. (Pro tip: running it as Administrator you won’t be bothered by lots of confirmation popups for each device you want to get rid of).
• Identify all the records pertaining to the devices Windows must forget. (Pro tip: clicking on the Description column will order them by name, making things easier).
• Shift-click and select all the occurrences of the device, then right-click and select Uninstall selected device. You may be prompted some confirmations depending on your privileges. Say yes in case.
• When the list has been cleaned up by all offenders, close the tool and restart your PC!
• After a fresh bootstrap, plug you devices back in the port that’s most convenient for you (the new one) et voilà! Rien ne va plus, les jeux sont faits and other out of place french expressions that sounds apt for celebration!

 

Last edited: Dec 6, 2025

I am sure you could do that, and you could follow the advice to use MidiOX or other Midi utility like that. But as long as your Motu 828 is not damaged/malfunctioning like say for instance you bought it used and untested; all of those workarounds are going to cost you time in the long run. If it is a perfectly functioning device, installing it and getting it right from the start will save you headaches in the long run. Which version of Cubase are you using?

This is how I would tackle the problem. My first attempt at a fix would be to remove the devices. Reboot the machine. Reset cubase to default fresh install settings. Then reinstall the audio interface again first and get that setup correctly. When you are satisfied the 828 is working properly, reboot. Then install the Novation remote again after that.

Disconnect both MOTU 828 and Novation controller. Reset Cubase 12 by renaming %APPDATA%\Steinberg\Cubase 12_64 and restart Cubase. Plug in the Motu first, confirm it works, then add the Novation controller after that. Getting the Motu working in Cubase will be a piece of cake, and you might not even need to reinstall the software for it. Once that is done, you have your problem narrowed down to only installing your Novation/script correctly with your Motu already "resident" on the machine.

Maybe a Windows user can confirm that approach before you try it. It's an older device so I would consider rebooting after each major step. Cubase cleaned up and default, reboot. 828 working, reboot. You get the idea. I used the Cubase 12 naming convention so depending on your actual version of Cubase you will have to adjust that one thing.

 

Last edited: Dec 5, 2025

BION, my script is working again, and I have no idea as to why.