Hi, for about a week now this message has been appearing before I access Cubase. I’m still using version 14 and I’m waiting for an offer to upgrade to 15.
What happens is that everything works except the MIDI connection — there’s no connection with the keyboard, so I’m unable to play. The issue is resolved if I restart the computer.
Hi, thanks. If I understand correctly, it’s a Windows problem. I thought it was the sound card drivers (UR816C) since I’ve never updated them and I’m thinking of doing so. So, what do you recommend? Thanks.
I’m not certain whether this is a Windows issue. You can try to update the UR816C driver.
If it doesn’t help, you can revert the Windows update. I believe the author of the other threads described how to remove this specific update somewhere.
It’s a Windows problem all right. For starters, here’s my set-up: Cubase 15 Pro + Halion 7 + several Steinberg libraries running on Windows 11 with the latest updates, M-Audio MIDISport 8x8/S box with latest drivers hooked up to 6 synths and a UR22 sound box. I’ve had this setup for several years, and never had any problems, and the upgrades to Windows 7 to 8 to 10 and finally 11 were seamless, as were the upgrades from Cubase SE to 14 to 15.
Now comes Windows 11 updates in mid-February. All of a sudden Cubase doesn’t shut down properly, and I start getting “Freeze” errors upon re-start of Cubase. Then I lose my MIDI connections, Cubase freezes completely, then starts up but after a few minutes freezes, etc. I uninstalled the 3 Windows updates that I got since mid-February, but nothing changed, so I uninstalled the 25H2 update. I got Cubase to work with no problem, and the MIDI connections were perfect. Worked on a project for 2 hours, when all of a sudden Cubase froze again.
All along I was emailing Steinberg back and forth, and everything seemed to point to a Windows problem. Last night I received this email from Steinberg, and answer I had picked up on some chat sites a few days earlier: “It looks like Steinberg has finally got some guidance on what to do with the help from Microsoft. Details are here.
The issue you’re reporting and OP’s issue are not the same thing. So I wouldn’t confidently say it’s due to the MIDI Services rollout.
In your case, the inMusic drivers hang the service. It’s in the pinned post in Announcements,. Uninstall the m-audio drivers, and if the MIDI device is class-compliant, you will be unblocked.
For older m-audio/AKAI/etc. MIDI devices that are not class-compliant, we’re working with inMusic on getting the driver fixed.
Hi, first of all thanks for the support. Yes, I’ve tried everything, but I’m still having a doubt and I’ll try again by turning on the board first and then the PC, even though I think I’ve already done that. That said, I’ve also updated the UC816C drivers, but no luck. Do you think I should try uninstalling everything and reinstalling the drivers?
Antonio
I ran two tests by powering on the audio interface first and then the PC, and it worked. I didn’t have to restart the PC, so both tests were successful. For now, it’s all good—thanks everyone! I’ll keep an eye on it, hoping it continues to work without issues.
For the past few weeks, in order to avoid Cubase 15 not connecting to my MidiSPORT 8x8, and freezing upon exit, it appeared that it was a known Windows update problem. So I uninstalled the 25H2 update, paused all Windows updates, re-installed Cubase 15 Pro, and left the whole DAW running. Everything is working fine since March 20. But has the Windows problem been addressed/fixed in the new Cubase update? Any suggestions?
The problem is in the inMusic driver. It’s in the pinned post. The driver has always hung on exit, but the impact is much broader with the new MIDI Service in place.
We have a workaround in Windows in our Discord server Windows MIDI / Audio . It will roll into Windows at the end of May. Preview is there now to unblock folks.
When you visit the discord server, look at the post in #start-here which tells you where to go for different known issues.