Thanks for the reply.
The driver gets installed by a custom action in the installer.
It uses the SetupDiXXXXX functions. It is basically a copy of the code the
would be called by "Devcon install".
From: wdmaudiodev-bounce@xxxxxxxxxxxxx [wdmaudiodev-bounce@xxxxxxxxxxxxx] on
behalf of Matthew van Eerde [dmarc-noreply@xxxxxxxxxxxxx]
Sent: 11 September 2019 16:06
Subject: [wdmaudiodev] Re: The link between Audio Properties and the Driver
How are you reinstalling the driver exactly?
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Ed Tottenham <Ed.Tottenham@xxxxxxxxx>
Sent: Wednesday, September 11, 2019 12:37:46 AM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] The link between Audio Properties and the Driver
I'm hoping that someone can help here.
I am trying to find the link between the Endpoint information used in a WDM
Audio Driver and the Audio Properties for an endpoint.
When the driver is installed, the AddReg section in the .inf file causes the
EndPoint names top be written to
The Audio Control Panel gets all its information using the MMDeviceApi which
gets all its information from
There was a problem in our .inf file which meant that in the update to 1903 the
EndPoint Names weren't added to the registry. All endpoints were given a
default name of "Digital Output" or "Digital Input" in the Audio Properties.
This is now what is retrieved by the MMDeviceAPI and displayed in the Audio
Reinstalling the driver with a corrected .inf file writes the names correctly
to the MediaCategories section of the registry, but the MMDevices is not
I'd like to write a simple command line program to correct the names but I can
see nothing in the information returned by the MMDevicesApi which links to the
MediaCategories section to be able to retrieve the intended names for the
Am I on completely the wrong path? Is there a better way of updating the
endpoint names in the MMDevices section?
Many thanks in advance