When I open Cubase for the first time after booting up my PC it works perfectly fine, but if I close it and try to open it a second time, one start up it gets stuck saying “Initializing All MIDI Inputs” or “Initializing MIDI”. I’m on Windows 11 and I checked other forums saying to uninstall the most recent updates, but that didn’t work. If I restart my PC it opens fine for some reason but after I close the application the second start up gets stuck. Any advice would help. Thanks!
1 Like
Upon some testing, I opened the settings of my Scarlett 2i2 and noticed it’s buffer size wasn’t matching what I had changed it to in Studio Setup (which I’m now realizing was something I changed in the last project before I started having these issues). So far the issue has seemed to fix itself but it’s also only been 5 minutes. If it breaks again I’ll update.
If it fails again on MIDI, then check to see if you are using any inMusic brands drivers (Akai, m-audio, RANE, etc) for devices. Those are crashing the MIDI Service, and I validated today that the problem is in the driver itself.
In most cases, you can just use our in-box MIDI driver instead. It doesn’t have that issue.
Pete
Microsoft
I’m having this same issue. I have a Focusrite Solo and an Akai MPK Mini IV. How would I check what drivers are being used?
Hi and welcome to the forum!
Perhaps check in Windows, Settings->Apps->Installed apps, search for “Akai”?
That was it. After i removed the Akai driver, no more issues. Thanks everyone!
2 Likes
Unfortunately, ChatGPT got that all wrong, like it usually does.
The problem is the inMusic driver (AKAI, in-music, etc.). It’s not all third-party drivers, just those. It’s also not some handshake between the parts, and it doesn’t understand the relationship between WinMM and Windows MIDI Services.
There’s a pinned thread in the Announcements section where I explain the issue and what needs to be done. All most folks have to do is use our in-box drivers instead of the inMusic drivers.
Disabling the service without taking additional steps doesn’t force the old behavior. It completely breaks it.
That makes no sense. I’m not sure what that is referring to, but all MIDI devices show up there, as they should.
Pete
Microsoft
1 Like
“There’s a pinned thread in the Announcements section where I explain the issue and what needs to be done. All most folks have to do is use our in-box drivers instead of the inMusic drivers.”
If I had seen this “Pinned part in the announcement section" in this thread that would have been helpful to know when I was here yesterday
If what you suggested works even better for me then I can easily go back and undo the changes I made in W11.
Thanks
Actually, you can’t exactly. When you changed the service from demand start to disabled, you can’t change it back to demand start based on the same triggers anymore. The triggers can’t be set in the Services UI.
You can change it to automatically start if you want.
As for ChatGPT, its explanations were all wrong, as was the metaphor. It leads folks down the wrong path.
It’s hard to get info out to folks, unfortunately. There’s the pinned post here, but there’s also a blog post that I wrote which shows up as a top result in all search engines, but I suppose you need to have the right keywords to search for 
But specifically, that’s not correct. If that solved it, then Windows MIDI Services was never actually enabled on your PC. When Windows MIDI Services is switched on on the PC (not the service, but the feature) Audio Endpoint Builder no longer enumerates MIDI devices and instead delegates that all to the MIDI Service. If you turn off the MIDI service in that case, then nothing is enumerating MIDI devices.
So not sure what is happening with your PC, but the ChatGPT explanation is more wrong than right in ways I want to make super clear to anyone else who might look at that and follow the same steps.
Pete
Microsoft
I totally hear you and will find your pin post but I don’t understand half of your terminologies you use. You’re talking here like as if I was one of your colleagues. You have to be able to explain this stuff like you’re talking to people who have no idea about this stuff but are having major issues loading their DAWs or even being able to even close them.
You! Understand from a technical point of view what is the error in Chatgpt’s resolve but WE! Aren’t tech wizards who understand your verbiage.
Like, what does this even mean? LOL
“When you changed the service from demand start to disabled, you can’t change it back to demand start based on the same triggers anymore. The triggers can’t be set in the Services UI.”
-demand start? Same triggers? Services UI?
LOL
what I did using chatgpt solved the issue I was having
That’s not bad info being passed down to someone who can’t figure out what the heck you’re even talking about lol
I was unable to to open Cubase. After a restart I could open it once but after that it would freeze on “all midi onputs”
If I could get in after a restart it wouldn’t let me close Cubase. Same with my Akai software. I couldn’t get in but after a restart I could get in, but couldnt close
Those steps I followed above from Chatgpt solved that issue and didn’t create other issues.
And yes i just undid the steps without any issues. But then the same issue i initially had came back.
I’m hoping to now find your post about the inMusic issue and try it your way.
Thanks
No, I’m not saying to go back and change back if you have something working. I don’t understand why it is working (something else had to have been changed here as well), so guiding you through more changes would not be a good idea.
I mostly just don’t want others to follow the same steps, because they shouldn’t have worked in your case, and definitely will not work in any other case I can think of. They ignored the rest of the info in this thread you replied to, and added potential confusion for others.
(Edit: I see you have updated your post to indicate that. Thanks. That’s my primary concern)
The Windows MIDI Service is responsible for finding all the MIDI devices on the system, and making them available to applications. That’s called “enumeration”. When you turned that off, you should no longer have seen the AKAI device, or any other MIDI port other than maybe a Korg device using their older style driver.
Sorry. You were using terms and tools in your explanation above, so I made the assumption you were familiar with them.
The MIDI Service is, with the Windows install, set to start up the first time an application makes a MIDI call. That’s called “demand start” or “triggered start”. It’s something we have to set up when configuring the service in Windows.
“Services UI” = The services tool (technically a Microsoft Management Console snap-in) you used to disable the Windows MIDI Service
Pete
Microsoft
1 Like
Hey Pete
Appreciate your response and patience and for explaining all the terminologies. I totally understand assuming based on my responses that I might carry similar technological attributes but it’s a facade only slightly and recently dipped in depth, but is forgotten within a few days. I have a tendency to only remember the things I truly care to know if it pertains to my passions. Thats why I’m so quick to humble myself and edit my post with a preface in fear that I might look like I know what im doing, and like a prophet, point people your way.
You’re doing great work out here.
I don’t know why it worked for me either. I tried so many things, circumnavigating possible further issues. I try my very best to deep dive thoroughly even without Chatgpt. I use YouTube alot too, but all the new video’s on W11 updates weren’t related to these issues.
If you email me your post that you pinned that would be great. If you recommend I take this post down I will unless you see value in it
Thanks
PS: I see that you linked the Pin in your response. No need to email
BA
No worries. I’d never ask anyone to take a post down. I don’t think it’s helpful (or generally ethical) to do so.
The pinned post is the last link in my response above.
Pete
Microsoft
I had some weird issues also with my MPC XL & X drivers. There working i did get the freeze with cubase 15 when scanning midi.. I had uninstalled my akai drivers and re installed. Its been working.. my question you want us to uninstall all inmusic drivers and windows will install the correct drivers that will work with the usb c audio and midi drivers for the new MPC XL and live 3?
Our in-box drivers won’t work with combined audio/midi devices, just class-compliant MIDI devices.
The Discord server with workarounds and discussion is Windows MIDI / Audio
Pete
Microsoft
[quote=“Psychlist1972, post:14, topic:1025697”]
The Windows MIDI Service is responsible for finding all the MIDI devices on the system, and making them available to applications. That’s called “enumeration”. When you turned that off, you should no longer have seen the AKAI device, or any other MIDI port other than maybe a Korg device using their older style driver.
[/quote]
This now makes total sense. I opened Cubase today and couldn’t play any of my midi keyboards. I went to devices where midi ports are and it showed nothing at all except the Korg.
I went back and turned Windows MIDI Service back on in Services.msc
That fixed the problem of no MIDI in my Cubase DAW.
But the same Issue i had from the last 3 days reappeared
Cubase freezes at All MIDI Inputs
→ Cubase freezes on close
I tried going to your link and where it says
“Drivers from inmusic brands (m-audio, AKAI, RANE, and a few others) are crashing in the Windows MIDI Service midisrv.”
I’m not sure what to do from there. I opened my Control Panel > install or uninstall a program and I don’t know which one to uninstall.
I can’t click on the link to Discord because I don’t have Discord.
I now know why you said chatgpt was wrong.
That waa a cheap workaround but it left me without my midi ports and now I have my midi ports back But the freezing is back
Thx 
Is this what I need to follow?
No.
Here are instructions directly from Korg.
It is important that you uninstall Korg’s own drivers and then use the Microsoft drivers.
1 Like
MPC X and MPC XL are both class compliant devices on passes audio / midi bi directional over usb c and the other over usb. I dont and never have used discord.. I did sign up but my question is simple leave akai driver or uninstall