[Beta Verification] MetaServer cannot quit on Windows 11

Small bug, in the system tray, right clicking on MetaServer and pressing Quit does not quit, it keeps running in the background. W11 latest MG server

(also, the server menu stays on the screen!)

Thanks for reporting this. Choosing Quit should close MetaServer completely, and the tray menu should disappear.

Please confirm the exact MetaServer version and build shown in the app. Does the same behavior occur when quitting from:

  • the right-click system-tray menu; and
  • the Quit option in the left-click MetaServer tray popup?

Please also confirm whether ending MetaServer from Windows Task Manager closes it normally. This will help determine whether one tray command is broken or the shutdown process itself is blocked.

I tried to left click and press quit and it still did not close. And the menu stayed on the screen. v 6.03.6010

Thank you for confirming the exact version and testing the left-click Quit command.

The investigation has identified the problem. MetaServer requests shutdown correctly, but cleanup of the active Windows MIDI backend can block the shutdown process before its timeout takes effect. This also explains why the tray menu can remain visible after selecting Quit.

The fix is now scheduled for MetaServer Windows 6.0.4. It will move potentially blocking MIDI cleanup away from the interface, enforce a real shutdown timeout, and ensure that MetaServer can close even if a Windows MIDI component does not respond.

Until the update is available, please use Windows Task Manager to end MetaServer when Quit does not complete. I will update this topic when a verification-ready build is available.

Thanks. I am not sure if this has to do with my other problem, I posted about losing the Metaserver midi ports.

It is possible that the two problems are related. The Quit failure occurs when MetaServer is cleaning up the active Windows MIDI backend, while the missing ports may indicate that the same backend or Windows MIDI Services had entered an unhealthy state.

However, there is not enough evidence yet to confirm that they have the same cause. Please send the logs requested in the missing MIDI ports topic, ideally captured while the ports are absent and before rebooting Windows. I will compare the final MIDI-related entries with the shutdown path and keep the two reports linked during the investigation.

If the ports disappear again, please capture the MetaServer logs before restarting services or rebooting the computer.

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 test Quit from both the main window and system tray, with Windows MIDI Services and WinMM where available, and report whether the process exits within a few seconds.

HI, I don’t have access to the file.

Thanks for checking. The link is working, but it points to a beta-testing area that is available only to authorized beta testers.

This topic was updated primarily to let everyone know that the correction has been implemented and is now being verified. If you are not currently a beta tester, you do not need to do anything—the correction is planned for the upcoming production hotfix.