New Windows (insider) update screwed up all my virtual midi ports! 25H2 26220.7653
NEVER get involved with the Window insider betas when having CB 15 pro as your DAW..
I agree but too late now!
Roll back the update?
Not possible unfortunately
Something to do with this perhaps?
I don’t think so. Fortunately, I managed to remove the Windows update came yesterday and everything’s back to normal.
In what way did it screw up your virtual MIDI ports?
See this post:
Loop Midi disappeared completely and LoopBe30 had to be reinstalled and had less ports and completely different names. A real PITA!
Which Insider channel are you on, and do you know the update number/description?
FWIW, this sounds more like the Insider upgrade not being able to reinstall the drivers vs anything with the new MIDI stack. That happens with some software (each Insider release is typically a full Windows Upgrade). But more info can help tell.
Pete
Microsoft
I was on Canary and the number was
25H2 26220.7653
And you no longer have it installed, correct?
If you still have it, I’d like to figure out what happened there. I just looked it up, and that Canary release did include the new MIDI bits starting on January 9.
But I’ve tested them with LoopMidi and similar before (not LoopBe30) and those functioned as before. I’ve never had to reinstall anything. That may still be related to the OS upgrade process.
As you know, Canary is where we experiment (it’s the first public stop after our internal builds), so things can go wrong there. “Canary in the Coal Mine” is how it got its name.
Pete
Microsoft
Good one
![]()
Good luck!!
Likely bug, including workaround info, in case you want to track.
Pete
Microsoft
Yesterday I got the Windows Preview 26200.7705 via the standard Windows Update (I’m not subscribed to the Insider channels).
According to the release notes it contains the new MIDI 1.0 and 2.0 services, but I don’t see anything different than before on my system.
Do I miss something here?
This explains how the rollout works.
Pete
Microsoft