Share via

[19041] Audio Endpoint Builder removes custom MIDI drivers!

Anonymous
2020-03-03T01:45:32+00:00

In the latest 2004 Slow ring build (19041), maybe also in 19033, the Audio Endpoint Builder service removes all custom MIDI drivers (e. g. Coolsoft VirtualMidiSynth) from the system and replaces them by the builtin library. Every time upon reboot I need to reinstall these drivers to get proper MIDI playback.

Process Monitor displays this clearly:

3:34:17.7288780    svchost.exe    2316    RegQueryValue    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1    SUCCESS    Type: REG_SZ, Length: 42, Data: VirtualMIDISynth.dll

3:34:17.7332640    svchost.exe    2316    RegDeleteValue  HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1    SUCCESS    

3:34:17.7333624    svchost.exe    2316    RegDeleteValue    HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1    SUCCESS    

3:34:17.7372816    svchost.exe    2316    RegSetValue    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1    SUCCESS    Type: REG_SZ, Length: 22, Data: wdmaud.drv

3:34:17.7373767    svchost.exe    2316    RegSetValue    HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32\midi1    SUCCESS    Type: REG_SZ, Length: 22, Data: wdmaud.drv

This did not happen in the regular 1909 build.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2020-03-09T19:09:27+00:00

Hello,

I have identified the cause for this issue, the CoolSoft application is modifying the Drivers32 registry keys in an unsupported way. I'm in contact with the CoolSoft developer and assisting with the fix.

Thanks,

-Gary Daniels

Senior Software Development Engineer

Windows Audio Drivers

Was this answer helpful?

2 people found this answer helpful.
0 comments

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-04T08:55:49+00:00

    Hello,

    I have identified the cause for this issue, the CoolSoft application is modifying the Drivers32 registry keys in an unsupported way. I'm in contact with the CoolSoft developer and assisting with the fix.

    Thanks,

    -Gary Daniels

    Senior Software Development Engineer

    Windows Audio Drivers

    Windows Audio Endpoint Builder service is now rebuilding the "old" Drivers32 reg key from scratch, getting info from installed device drivers.

    This could be ok, but a lot of software synths out there (VirtualMIDISynth, Munt, ...) are not device drivers but software only components.

    And also, they aren't kernel-mode .sys drivers but user-mode DLLs, managed by winmm.dll.

    User-mode drivers were (and still are) great for this kind of software, because they're both easier to debug and safe for the system.

    Requiring them to be installed with .inf and catalog files, like real hardware device drivers, is a huge work and a costly request.

    VirtualMIDISynth is a free passion-driven project, without any income; can't (and don't want to) buy an expensive kernel signing certificate for... just creating a registry key !

    I wonder how much does it takes for someone on the net to create something that detects changes made by Windows Audio Builder service and reverts them... someone already proposed this on my forum, but I refused the idea because it's really an unsupported and hackish way.

    What about adding a "special" registry key to let "Audio Endpoint Builder" service create additional midiX entries in the old Driver32 key for user-mode DLLs?

    Thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Sumit D - IA 171.1K Reputation points Independent Advisor
    2020-03-03T02:14:28+00:00

    Hi,

    I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.

    Can you please share a link of the feedback so that I can escalate above?

    https://support.microsoft.com/en-in/help/402156...

    https://www.tenforums.com/tutorials/130174-shar...

    Content on the above blog is written by a Microsoft MVP so it is safe. However, do watch out for the ads.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Sumit D - IA 171.1K Reputation points Independent Advisor
    2020-03-03T15:57:26+00:00

    Hi,

    Escalated to the relevant people. Appreciate your patience.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-03-03T08:14:52+00:00

    Was this answer helpful?

    0 comments