microsoft / microsoft/MIDI

[BUG] WinMM app stops receiving messages when open/close connection multiple times across several apps

Open
#564 13 comments 0 reactions 2 assignees View on GitHub

@judzmura is already working on this.

Since Sep 14, 2025.

bug :lady_beetle: needs-investigation :mag:
Dominant language
C++
Stars
679
Forks
72
Avg merge
4h 51m
Merged PRs (30d)
59

Description

Describe the bug

This issue was observed with the Internal Preview (2025-02-18 Customer Preview 2 Daily).

WinMM app stops receiving messages.
This issue can be reproduced with both MIDI 1.0 device and MIDI 2.0 device regardless of the driver.

To Reproduce
Following steps may not be required steps but they are reproducible steps.

  1. Set the Roland UM-ONE mk2 to class-compliant mode (set the switch to "TAB") and short INPUPT and OUTPUT to loop back messages.
  2. Attach the UM-ONE to PC.
  3. Open the Pocket MIDI and choose the "UM-ONE" as an InputPort and an OutputPort.
  4. From the "File" menu, open the attached "test.pocketmidi" file.
  5. Open midi.exe and monitor the "UM-ONE".
  6. Open midi1monitor.exe and monitor the "UM-ONE".
  7. In the two System Exclusive windows, click the "Transmit" buttons to send messages.

Image

  1. Close the Pocket MIDI.
  2. Open midi.exe and send 0x20904040 to the UM-ONE to make sure both monitors still working.
  3. Double click the attached "test.pocketmidi" file and click the "Transmit" button on the System Exclusive windows.

The midi1monitor.exe does not receive any messages.

Expected behavior
The midi1monitor.exe continues receiving messages.

Installer Name or Version

  • [Internal Preview] Windows MIDI Services (In-Box Service) 1.0.3-preview-11.250218-1656-x64.exe
  • [Internal Preview] Windows MIDI Services (SDK Runtime and Tools) 1.0.3-preview-11.250218-1656-x64.exe

Desktop (please complete the following information):

  • OS: Windows 11 24H2 build 27788.1000 (Insider Canary channel)

Device information, if this is with an external MIDI device:

  • Roland UM-ONE mk2

Application Information

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.