Metagrid midi has disconnected and does not show any choice in the drop down now. I’ll send my log to your DM (update: restarted all services did not help, but I did a full reboot and that did work)
Thank you for the update. It is useful to know that restarting the services did not restore the MetaGrid MIDI ports, but a complete Windows reboot did.
Please send the logs you mentioned, ideally covering the period before the reboot while the ports were still missing. Please also confirm the exact MetaServer Windows version and whether Windows MIDI Services or the legacy WinMM backend is selected.
I will compare the logs with the existing Windows MIDI Services issues. For now, I suggest keeping this topic open because the reboot restored the ports but did not explain why they disappeared.
1 Like
Logs were sent by DM
Thank you for sending the log. I have now analyzed it and found the failure.
Before the reboot, MetaServer found stale virtual MIDI endpoints that Windows MIDI Services would not remove. It then attempted to create the MetaGrid, Cubase, and Cubase Sync ports, but Windows MIDI Services would not open any of them. That is why the ports were missing in Cubase. After the full Windows reboot, the same ports were created and opened normally.
This confirms that the problem was not caused by your Cubase configuration or the USB connection. It is a MetaServer recovery issue when Windows MIDI Services enters this stale endpoint state. I have scheduled the fix for MetaServer Windows 6.0.4 so MetaServer can detect this condition and recover the ports without requiring a full Windows reboot.
The log also confirms that this is related to the Windows MIDI lifecycle involved in the separate Quit problem, although the missing-port recovery is being tracked as its own fix.
1 Like
Great bug hunting!! Glad you figured it out, nothing worse than a mystery! 
1 Like
Status update: this correction has been implemented and is currently included in the MetaServer Windows 6.0.4 Beta 1 and MetaGrid Pro 1.7.4 Hot Fix beta.
This post is primarily an informational update for everyone following this issue. If you are already a member of the beta program, you are welcome to verify the correction and report the result here. If you are not a beta tester, no action is required—the correction is planned for the upcoming production hotfix.
The beta downloads and TestFlight build are available only to authorized beta testers, so the linked beta resources may show “Access denied” for other forum members.
Beta testers can download the server beta from https://forum.metagrid.app/t/latest-metaserver-beta-builds. Please reproduce the previous stale or unavailable MIDI-port state and confirm whether MetaServer restores the ports without a Windows reboot. If not, attach the new MetaServer log from that attempt.
Thank you again for the detailed diagnostics. The latest support package exposed one remaining gap in the RC1 recovery path.
MetaServer successfully created the MetaGrid, Cubase, and Cubase Sync APP virtual devices, but Windows did not make their output endpoints ready quickly enough for the first connection attempt. RC1’s fallback handled Loopback endpoints, so it did not perform the promised recovery for these APP virtual devices. This also explains why restarting MetaServer could restore the connection: Windows had finished registering the endpoints before the second launch.
The APP virtual-device recovery has now been corrected for MetaServer Windows 6.0.4 build 6014. Newly created endpoints receive a bounded readiness window with repeated open attempts against the same device. The complete Windows test suite passes 88/88, and a production installer candidate has been compiled.
The candidate is still undergoing final release verification and has not been published yet, so this topic remains in Beta Verification rather than being marked fixed. I will update the topic with the public download when the verified production build is available. At that point, please test it without restarting Windows first and confirm whether all three MetaServer MIDI ports appear and connect normally in Cubase.
1 Like
MetaServer Windows 6.0.4 is now publicly available and includes the MIDI endpoint-recovery changes developed from this report.
MetaServer now detects stale MetaServer-owned Windows MIDI Services endpoints, reconciles them and performs bounded readiness retries when newly created APP virtual-device endpoints are not immediately available.
Please update to MetaServer Windows 6.0.4, start Windows MIDI Services and Cubase, and verify that the MetaGrid MIDI ports remain available in MIDI Remote without requiring a complete Windows reboot.
If the ports disappear again, please capture a MetaServer support package before restarting MetaServer, Windows MIDI Services or Windows itself. Please also note whether the ports are absent from Cubase only or from other Windows MIDI applications as well.
1 Like