Issue

There is a known Windows issue affecting the MIDI service when used with EasyWorship and other third-party applications. Specifically, third-party drivers that dynamically create MIDI ports are not functioning as expected. MIDI ports are only recognized if they are created before the MIDI service starts; otherwise, they are not visible to applications.

The root cause appears to be the startup sequence of the involved components—namely, the Windows MIDI service, and the application itself. In this case, the issue arises because the devices create MIDI ports after the Windows MIDI service has already initialized, and the service does not currently detect ports that are added to an existing device after startup.

Solution

Microsoft is actively working on a resolution for this issue, with a fix currently scheduled for release by the end of April.

In the meantime, the following steps may help mitigate the problem:

1. Close EasyWorship.
2. Download the Windows batch file attached at the bottom of this article, which is designed to restart the Windows MIDI service.
3. Right-click the CreateMIDITask.bat file and select Run as Administrator.
4. After the script completes, press Enter to close the command window.
5. Restart your computer.
6. Reopen EasyWorship and attempt to use the MIDI service again.

If this does not resolve your issue, please contact EasyWorship Support.

Create Support Ticket