Metaserver went live on an old RC4 version of Windows MIDI Services that is no longer available

Support & Troubleshooting
1

Just a reminder about what I posted back in June: The old release candidate from earlier this year did not have a go-live license, and the API fundamentally changed in preparation for going in-box for Windows 11 25h2 and later. Discussed extensively on our Discord server and in the GitHub - microsoft/MIDI: Windows MIDI Services · GitHub release notes.

Customers need to have rc4 uninstalled from their PCs, and doing so causes this app to no longer see Windows MIDI Services.

If this product is still using the Microsoft.Windows.Devices.Midi2 SDK/API it needs to be updated to Windows.Devices.Midi2 and follow the instructions in the releases at Releases · microsoft/MIDI · GitHub .

I recent customer on my Discord server had some issues they ran into and I had to have them uninstall the old supported rc4 bits. It’s only then that I found out that metagrid is still using those.

Pete
Microsoft

2

Hi Pete,

Thanks for following up and for helping the customer who ran into this. You flagged the upcoming API change back in June, and we should have followed up sooner.

We confirmed that MetaServer for Windows 6.0.5 shipped with the RC4 SDK. Its native MIDI detection checks for the RC4 runtime first, which explains why removing it can leave MetaServer unable to see native MIDI ports. We’ve retired the old setup guide and removed the RC4 installation steps.

The MetaServer for Windows 6.0.6 hotfix will be ready this week. It will move native MIDI support to Windows.Devices.Midi2. I’ll post the download link here when it’s available.

Przemek

3

@przemek I am the customer! I sent you a message and an email, but I gather this is the answer. I will have to wait until the fix comes out to be able to use Metagrid. Is this correct? TY