MIDI Remote does not start – no scripts, no lower zone tab, Mapping Assistant won't open

Cubase Pro 16.0.5 on Windows 11 Pro 25H2 (build 26200). MIDI Remote does not start at all.

- Settings > External Devices > MIDI Remote Scripts is completely empty, including factory scripts.

- There is no MIDI Remote tab in the lower zone. It is not listed in Set up Tabs, and Show All is greyed out.

- The MIDI Remote Mapping Assistant does not open.

- MIDI ports show as Active under Settings > MIDI > Ports, but their Usage column is blank.

- Cubase 16 never updates Documents\Steinberg\Cubase\MIDI Remote. When I renamed that folder, Cubase 16 did not recreate it.

Cubase 15.0.30 on the same PC works normally with the same scripts.

Already tried, with no change:

- Restarting Cubase 16 and restarting Windows

- Reinstalling Cubase 16

- Switching MIDI Technology between Windows MME and Windows MIDI Services

- Safe Start with program preferences disabled

- Starting with the MIDI Remote folder renamed

- Closing the application that provides my virtual MIDI ports

Windows MIDI Services 1.0.17-rc.4.25 is installed. Is there a known cause or fix?

Me too! Damn annoying, I’ve spent all day trying to fix it with no success.

Upon reinstalling C16, it doesn’t create the MIDI Remote folder in Documents. Therefore it isn’t communicating with that folder for the remote scripts and won’t see any of them, even the Public scripts.

Looks like a classic case of not testing C16 properly before releasing it. Hopefully there’ll be a quick update/fix soon!

That is old, and you should uninstall it (and any other older Windows MIDI Services packages) via Windows Settings > Apps > Installed Apps. The latest releases are at Releases · microsoft/MIDI · GitHub and include the new transports like BLE MIDI, Network, etc.

That won’t cause any of the issues you’re experiencing, however.

Pete
Microsoft

Update: thanks Pete, I’ve uninstalled the old package and installed Windows MIDI Services Tools 0.99.96-preview.13. As you expected, it didn’t fix this. Cubase 16 still shows no MIDI Remote scripts, and Cubase 15 still works.

So far I’ve also tried reinstalling Cubase 16, Safe Start with preferences disabled, both MIDI Technology settings, and closing the app behind my virtual MIDI ports. None of it changed anything.

Andy, it looks like we’re seeing the same thing: Cubase 16 doesn’t create or update the MIDI Remote folder in Documents. Mine is the same after renaming the folder, so it seems MIDI Remote isn’t starting at all.

@Steinberg, can you confirm whether this is a known issue in 16.0.5, and whether a fix or workaround is available? I’ve also opened a support ticket.

I’m not Steinberg, and I see that several others are having issues on this, but, FWIW (and I know it’s no consolation), this can’t be a Cubase 16.0.5-wide issue. I’m not having any problem with its recognizing my MIDI Remote (custom settings for my Roland A-800PRO). I’m on Windows 11 26H2, and updated from Cubase 15 to 16.

My External Devices/Devices tab shows:

And the MIDI Remote Devices tab shows a whole bunch of entries:

I only have the one MIDI Remote device, so the others are all ones that got populated by either something carried forward from C15 or, perhaps more likely, the new Steinberg Activation Manager, which is the new way Cubase 16 provides MIDI Remote scripts (so they don’t have to wait for a Cubase update to do that). (I do remember receiving a nag prompt when starting C16 that indicated I should start the Activation Manager.)

If you haven’t already done it, you might try updating Activation Manager. It looks like the version on mine is 1.10.0.1489 (bottom of the Settings dialog).

Same issue here. only on my pc that runs windows 10 but it works perfectly on my new pc system running Window 1. strange

Yep…ME TOO!

Tried everything everyone has suggested here. Everything is just very flaky right now. Can’t even consistently use my controllers.

Tried all flavors of midi protocols/service/whatevertheheckyoucallthem

One strange thing I noticed is similar to what you mentioned where external devices are listed, but not connected to a port. E.G. my xtouch one barely functioning. no buttons work, but the display will follow the songs position and time.

The devices will show up in the tracks midi input yet nothing will trigger. Yet in Cubase midi settings > ports, NO devices will be listed.

From the all the new windows midi tools perspective, everything is functioning fine. Love the new sysex tool I used to update my xtouch one tonight.

Please just fix it quick Steinberg.

It looks like there is an issue with Remote Devices and changing MIDI Technology. I have to delete my Remote Device every time I change MIDI Technology, and there is no way to reassign MIDI ports (greyed out) unless I remove and re-add the device. I am not sure if this is a bug or not, but it looks like it to me.

That sounds like a different issue. You should start a new thread and mark it as an issue so Steinberg sees it.

Pete
Microsoft

Thanks. If you get a chance, the Windows MIDI Patchbay has a lot to offer to work around all sorts of interesting situations in and out of a DAW. And, if you want a control surface on a tablet, or a floating toolbar on your main PC, Windows MIDI Glass can do that.

It sounds like the main issue in this thread is probably not a Windows MIDI Issue. I’ll keep track of the thread in case something else crops up, but I recommend reporting to Steinberg and marking this as an issue here.

Pete
Microsoft

got the probleme .. reinstal a brand new activation manager.. all is good :slight_smile: