[19041] Audio Endpoint Builder removes custom MIDI drivers!

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.

Answer
Answer

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

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated September 30, 2020 Views 411 Applies to: