Depends on what you mean by "(+two updates https://sourceforge.net/projects/munt/files/m … /2.3.0-Updates/)". The update mt32emu_win32drv-1.5.1-win32-amd64.zip is dedicated to solve the problem with Windows 10 2004 compatibility. Did you install the updated driver or just reinstall the munt-2.3.0 package?

More info on the matter can be found in this topic.

sergm wrote on 2020-08-03, 15:35:

More info on the matter can be found in this topic.

Thanks! Wow, its a long thread, can you direct me to solution of this problem (if there any of course)?

Yes, sure. Just download mt32emu_win32drv-1.5.1-win32-amd64.zip from SourceForge and have a look at README.md.
I hope that running

1drvsetup.exe repair

will be enough to fix the issue.

sergm wrote on 2020-08-04, 07:24:

Yes, sure. Just download mt32emu_win32drv-1.5.1-win32-amd64.zip from SourceForge and have a look at README.md. I hope that runni […]
Show full quote

Yes, sure. Just download mt32emu_win32drv-1.5.1-win32-amd64.zip from SourceForge and have a look at README.md.
I hope that running

Copy code to clipboard

1drvsetup.exe repair

will be enough to fix the issue.

Thank you, fixed my issue (so far) 😊

I've tried uninstalling and reinstalling Munt, trying both drvsetup repair and drvsetup install, and still nothing works.

As if I needed another reason to hate Microsoft.

The repair fixes it for me, but only until the next reboot of Windows 10....
I hope there will be an updated version.

I had the same problem and I found it useful to remove the driver using drvsetup uninstall from the C:\Program Files\munt\mt32emu_win32drv directory using the Command Prompt.

Then I use loopMidi and create an new MT-32 Midi port.

From within Munt, I simply click New Midi Port and select the MT-32 Midi.

The only "drawback" is that you have to select that MT-32 Midi port every time you start a new session of Munt. But really, just leave Munt open the whole time and just keep it minimized in the Task Bar.

The loopMidi port stays the same within DOSBox no matter how many times you reboot your machine.

Is this still a problem with munt package 2.4.0? If so, I hope it is fixable. I've forgotten about this problem for several months, but if it still present on some systems, it'd be great to sort it out.

sergm wrote on 2021-01-20, 21:43:

Is this still a problem with munt package 2.4.0?

Not yet! 🤞

I haven't had any issue with Munt since June, and version 2.4.0 so far survived two reboots B)

The only glitch was when Win10 rev2009 was released in November. I ran "drvsetup.exe repair" to register the driver again.

Kaminari wrote on 2021-01-20, 22:53:

I haven't had any issue with Munt since June, and version 2.4.0 so far survived two reboots B)

The only glitch was when Win10 rev2009 was released in November. I ran "drvsetup.exe repair" to register the driver again.

I realise this is as intended. Still, drvsetup doesn't deploy a driver package which could be reinstalled on a new system (yes, the update to 20H2 was essentially installing a new system with migration of the world). If you had infinstall run beforehand, it'd probably survive even that 😉 Just pity that infinstall is a bit imperfect atm, probably it's worth to merge both these approaches (need to think more).

I downloaded and installed Munt 2.4.0.2 (x64) a few days ago and that appears to work just fine on Windows 10 20H2.