Startup crashes with Cubase 15, recent Win11 update

C15 working great last night, upon opening C15 today- immediate freeze with Hub and also when trying to directly open a .cpr file, also noted a few very recent Win11 updates that were done, and tried to roll back the one that says 26H2, but still with freezes.

Here’s a recent dmp file…

Cubase 15.0.30 64bit 2026.10.11 17.20.35.194-freezedump.dmp (1.2 MB)

I’d appreciate any help-

Thanks…

-Steveau

I had copilot investigate this. Reply below


Thanks for the dump. This one is MIDI. It isn’t the Hub or your project.

While Cubase was starting, it closed one of its MIDI outputs and asked the Windows MIDI service to close it. The service never answered, so Cubase froze. Your PC had only been on for two minutes, so whatever causes this is already there right after a restart. Nothing in the dump ties it to the Windows update.

The dump doesn’t say which device that output belongs to. These would help:

  1. What MIDI gear do you have connected, and how: straight to the PC, through a USB hub, or through the Fireface? The only MIDI port name in the dump is “RME ARC”. Is that an ARC USB, and where is it plugged in? Any inMusic (AKAI, m-audio, RANE, etc.) devices? Are you using any of those inexpensive 3-fader boxes sold on eBay and similar?
  2. Unplug your USB MIDI devices and the power to any USB hubs, then restart the PC and start Cubase. If it starts, close it, plug one thing back in, and start Cubase again. Keep going until it freezes. The last thing you plugged in is the one we want to hear about. If it still freezes with everything unplugged, try once more with the Fireface switched off too. Another Cubase user with this same freeze fixed it by turning his USB hub off and back on.
  3. If it freezes again, before you restart: open Task Manager as administrator, go to Details, right-click midisrv.exe, and select Create memory dump file. Zip it and share it with OneDrive or similar. That file shows what the MIDI service is stuck on.
  4. The MIDI Diagnostics Report lists devices Windows marks as having a problem: Windows MIDI Troubleshooting and Repair - Windows MIDI Services

That midisrv dump will really help others, but if you need Cubase working right away, you can switch Windows back to the older MIDI system: How to change the API mode - Windows MIDI Services . You’d lose sharing a MIDI device between apps, the built-in loopbacks, Network MIDI 2.0 and Bluetooth LE MIDI. That option needs Windows fully up to date, so you’d have to put back the update you rolled back first.


Pete
Microsoft

Thanks Pete for that useful info!

While I am curious about which MIDI device could be the culprit and will try to track it down, I am also leaning towards just reverting to the previous MIDI Win setup so I can keep on playing. (If it ain’t broke…)

If it’s one of those eBay 3-fader boxes, they also hang Cubase under the old MIDI stack as well.

Knowing which devices you have connected would help. Thanks.

Pete
Microsoft

I have been using a Deersync- M-Brio, 4 fader, 2 knob Midi controller. ($250 range), but that does indeed seem to be the exact problem.
So if it worked before the update, I can roll back the MIDI 2 update (as detailed in your previous post) and still use it?

Thanks.

I don’t have experience with that specific device. And I just read its manual and it doesn’t say anything about not working as a MIDI Out in a DAW. It doesn’t look like the same class of device that has the problem, but here’s one thing you can try if you’d like:

In Cubase Studio Setup, disable the device’s MIDI Output and see if Cubase starts up correctly. If it has already locked once since the last reboot, you may need to reboot again first.

Why? This is the specific issue I’ve run into with a whole bunch of devices. The folks creating these essentially ship tutorial code, sometimes with a paper note. When Cubase starts up and sends it a MIDI Identity Request, the device hangs because it doesn’t process incoming messages.

The only other devices known to hang the MIDI Service (and apps under the old API) are inMusic devices using their own drivers. That happens when you unplug the device after it has been opened for input. The problem is less visible in the old stack because it’s restricted to the one process, but it’s still there.

Pete
Microsoft

Sorry, we were typing at the same time.

If it’s that same problem, and turning off the MIDI Outut doesn’t fix it, then it also happens under the old MIDI stack and switching won’t help.

Any issue related to the new stack would likely have been visible going back to January when Windows MIDI Services was first rolled out.

Any chance you can do the midisrv dump capture before you move to the old stack? The instructions for capturing the dump are Step 3 in the post above from earlier. Instructions for how to move to the older API mode, which requires you to repair your Windows install since you uninstalled updates, is after Step 4 above.

To repair your Windows install go to Windows Settings > System > Recovery > Fix problems using Windows Update (keep files and settings). It’ll take a half hour or more usually.

Pete
Microsoft

OK, I opened up C15 and went to Studio setup and plugged in my Midi fader-immediate Cubase freeze. I did a midisrv dump retrieval right after, (obviously there’s no way to change the output settings of the midi fader because of the instant freeze).

midisrv dump file

Thanks. Analyzing it now. I’ll respond once there’s an answer to what is going on.

So it sounds like you don’t even get a chance to turn off the MIDI Out to it.

Pete
Microsoft

Yes, it’s the same problem. You would see the same thing on Windows 10 or older Windows 11.

Not sure how this ever worked on your PC. You said a recent Windows Update triggered this, but this is an issue that has been there for a very long time.

It declares a MIDI In and a MIDI Out, but only implements one of them.

It calls itself “Mb4fa MIDI Controll”, cut off exactly like that.

The M-Brio doesn’t respond to anything sent to it. It just hangs when anything sends it a MIDI message. It’s the same issue as with other hobby controllers that ship what is essentially the tutorial code, except they’re charging you full billing for this.

They don’t have their own USB vendor identifier, so the device just shows up as STMicroelectronics. We can’t just put in a rule to block MIDI out for those because it would block every single device that uses that identifier.

We have a workaround coming in Windows for these broken implementations. But it’s not going to show up in the near future. It’s also not ideal: We leak Windows kernel resources for the device to help avoid the service getting blocked.

On startup, when Cubase sees a new MIDI device, it sends a short SysEx Identity Request to the device, and waits on the response. However, the send itself never returns because the device just hangs there forever on a kernel call.

Deersync needs to offer updated firmware to fix this bug in their device. If you have any sort of support contact there, this is the issue to show them: [TODO]: Default CircuitPython install (and Arduino usbmidi setup) advertises non-functional MIDI endpoints which lock the service until unplugged · Issue #1084 · microsoft/MIDI · GitHub or feel free to give them my email address pmbrown@microsoft.com

Aside: the dump shows that the MIDI port was opened at 7:55am, but the dump is from 12:15pm. Did you open Cubase earlier in the day as well? If so, that’s when the midisrv hang happened.

Edit: I reached out via their contact form, but that rarely pans out. TBD.
Edit2: Their contact form doesn’t actually work properly. Stays stuck on a little popup and never submits, so no go there.
Edit3: emailed them instead. Not sure how I missed that big email address in the footer.

Pete
Microsoft

Yes, I played with it in the early morning and didn’t get to send the midi dump until later on.

So I guess I’ll be stuck with using an older non usb midi cc fader I can dig out of storage, for now-

Thank you for your help.

You had mentioned this was after a Windows update and it worked fine before that.

I’m still really confused by this, as there’s nothing relevant that has changed in MIDI since the beginning of the year.

Were you using this MIDI fader before the night before you had the Cubase hang?

Pete
Microsoft

Yes, I had been using this fader unit successfully until that day it started freezing C15-

Thanks. Very strange. I’ll do some testing on it, as if it’s the expected problem, that would have happened all year. It makes no sense it would be a recent development.

I bought one. It arrived today. I had to take it apart because even the cable they supplied didn’t fit into the USB port on the device well enough to stay connected, because the USB-C connection was sunken in too far. There’s no real play in the clear screws that hold the device into the enclosure, so they are likely all like this. When I could get their supplied USB cable to stay in, it never showed UI on the device. The manual makes that sound normal, but that’s not how it will work on Windows. With a proper USB connection, and no MIDI apps open, the UI comes fully alive.

Although they don’t make a big deal of it, they do show in the manual that you should have this only as a MIDI Input, so I’m about certain it’s the usual hobby-class device problem given that it reports both MIDI in and MIDI out.

Just to be super clear, that problem has been hanging Cubase for the past several years.

Although the partial USB-C physical connection gives me pause, because if yours doesn’t have a positive “snap” when you push in the cable, you could see some weird issues due to it coming and going over the bus. (In fact, it if disconnects and reconnects after Cubase sends its identity request, that could potentially clear the lock in Cubase, masking the problem)

Pete
Microsoft

The mystery deepens.

The loose connection is a real problem (I reassembled mine so the plug can fit a bit better, but it still doesn’t snap in like it should), but so far, it doesn’t seem to have any problem with messages being sent to it, like the Cubase startup SysEx Identity Request.

I had earlier assumed you were on 24h2 or 25h2 Windows 11, without actually checking that. Before the 26h2 update, do you recall which version of Windows you were on?

Also, do you plug this into a laptop (or back-of-the motherboard) connection directly, or into a hub?

Finally, when the Brio is locked up in Cubase, does the screen on the brio still update when you move the faders?

Pete
Microsoft

The info above requested in the previous post will help, if you have a moment.

Finished looking at this. It’s almost certainly hardware related, but hard to be more specific. With my own version, we managed to get one ERROR_CRC by lightly pressing the USB cable on the device, due to the bad connection they have. ERROR_CRC is a USB stack error reserved for very low-level transfer failures.

Copilot took a deeper run through the dmp from earlier and found that the driver had thrown an ERROR_CRC from the device. Given this repros for you each time, it seems unlikely that the loose connection would be the cause so a bad cable is another possibility. That ERROR_CRC comes from a USB hardware failure. The first message Cubase sends after you plug it in fails with a USB error, and after that nothing can be sent to it until it’s unplugged.

You could try a different cable or USB port. Folks never want to try other cables, but they are a very common cause of issues. The underlying issue here is somewhere between the usb midi driver and the device (USB stack driver, any hub, the cable, the actual port, the device, the device’s firmware)


Now, to get you unblocked, you can hand-edit your Port Setup.xml in %APPDATA%\Steinberg\Cubase 15_64 to add a “Hidden” value. This is the same as unchecking the box in the UI, but you can’t get to that because Cubase freezes.

Before editing the file, completely close down every Cubase process. If it was hanging at all previously, make sure you kill it. Reboot if unsure.

From my PC, this is the before. I’m using the default Windows MIDI here, but this will look different if you’re using WinRT MIDI or something else.

      <item>
         <string name="ID" value="O|Windows MIDI|Mb4fa MIDI Controll"/>
         <string name="Type" value="midi"/>
         <string name="Subtype" value="system"/>
      </item>
      <item>
         <string name="ID" value="I|Windows MIDI|Mb4fa MIDI Controll"/>
         <string name="Type" value="midi"/>
         <string name="Subtype" value="system"/>
      </item>

this is the after. Notice that Hidden is added to the O (Output) port

      <item>
         <string name="ID" value="O|Windows MIDI|Mb4fa MIDI Controll"/>
         <string name="Type" value="midi"/>
         <string name="Subtype" value="system"/>
         <int name="Hidden" value="1"/>
      </item>
      <item>
         <string name="ID" value="I|Windows MIDI|Mb4fa MIDI Controll"/>
         <string name="Type" value="midi"/>
         <string name="Subtype" value="system"/>
      </item>

You’re hand-editing a file that Cubase reads and writes, so be careful with it. You probably want to make a backup copy of it before you edit.

Also, if Cubase never saw the Brio beyond the crash, you will need to add those lines. However, you said it was previously working with Cubase, so I assume the lines will be in the file.

Pete
Microsoft

Pete, I can’t believe you bought one of these to help me debug, are you running for tech man of the year, or something? I truly appreciate your time and thoroughness!

Yes the usbC connection had been a minor inconvenience, I had hot glued the connection, which seemed to be fine for months until I recently needed to take it out of the system for testing. Then I tried another cable and just pared down the plastic sleeve with a utility knife enough to make a positive connection, which seemed to work and powered on and the freezing situation returned.

I see where I’ve been on 25H2 since last October, and Oct 7 of this year the 26H2 installed

Yes the usbC connection had been a minor inconvenience, I had hot glued the connection, which seemed to be fine for months until I recently needed to take it out of the system for testing. Then I tried another cable and just pared down the plastic sleeve with a utility knife enough to make a positive connection, which seemed to work and powered on and the freezing situation returned.

Not sure of the timeline between trying the new cable and the freezing returning, but that’s a far more likely cause of the issue than a Windows update. Good detail to know, thanks.

I would definitely try another cable. The only way we have been able to get that error is due to cable problems. In some of those cables, the only thing holding the connection together is the plastic.

When you plug this into your Windows PC, it should immediately show the UI on the device. If it just shows the LCD backlight, then only the power and ground pins are making contact. Seeing the screen doesn’t mean it’s a good connection, just that it’s connected.

Edit: FWIW, the crash dumps show you on 25h2, build 26200, so same version of Windows you used to be on. Your rollback of 26h2 appears to have worked, so that takes the update out of the equation. 26h2 is build 26300.

Pete
Microsoft

I just tried a third cable, pared it down to fit, and this seems to have made the difference!

So looking back… the MS update activity was just a red herring, and the crappy design of the usb port (and the resulting intermittent/suboptimal connection) on the DeerSync most likely to have caused this freezing in Cubase?

If you’ve been able to come and go in and out of Cubase now, and the device continues to work, then it does look that way.

The USB port design on that device makes it appear to me that no one ever tested a production sample before moving forward and shipping everything. It’s a horrible design. Shaving down USB-C cables is always going to cause problems later, and you definitely shouldn’t have to hot glue something to a $220 device just to keep it working.

I emailed them, but did not get a response. Reading some other info online, seems I should not expect to get anything. They list as a California company, but the Times Roman font on the OLED is the giveaway: it’s probably just a company in China cranking these out under that parent brand. Nothing wrong with that, unless you need support.

If you purchased it on Amazon, you should leave a review. The existing reviews fit the pattern of paid ones.

As for updates: Lots of folks think updates are the cause of their problems and jump there first, missing other causes. Sometimes they are, but more often, it’s just the last memorable thing that happened.

Pete
Microsoft