[wdmaudiodev] Re: WIN10 update changes drivers name and icon + bug in control panel.

  • From: "Vincent Burel \(VB-Audio\)" <vincent.burel@xxxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Wed, 26 Aug 2015 09:01:47 +0200

Finally I think I know why WIN10 update renamed some audio driver point name
…

Because it basically re-installs the audio driver but does not keep all
information stored in registry related to this driver.

For example WIN10 update lost Render/Friendly name & icon, but keep
Capture/Friendly Name.



I guess it’s a bug in the update procedure ? Someone can confirm ?



Regards

Vincent Burel





De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Vincent Burel
(VB-Audio)
Envoyé : samedi 22 août 2015 10:19
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] WIN10 update changes drivers name and icon + bug in
control panel.



Hello,



Does someone knows why WIN10 update renamed as default name, some audio
device points ?



Other new behavior: the Control Panel / Sound Dialog Box does not always
show the level meter of playback or recording devices if used by WASAPI or
KS interface (in exclusive mode)…



Regards

Vincent Burel



De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Vincent Burel
(VB-Audio)
Envoyé : lundi 10 août 2015 17:43
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] WIN10 update changes drivers name and icon



Hello,



Just made a WIN10 update from a WIN7 64bits with my different Virtual Audio
Driver installed (VB-Cable / Voicemeeter).



And I got different strange problems :

On first Windows startup (1 or 2 first) the Control Panel / Sound Dialog Box
was not usable (crash when moving the mouse on it).



After that I discovered that VB-Cable’s and Voicemeeter Playback device were
renamed (with default “speaker” name) and the icon was changed in default
speaker icon… but not for recording device… re-installing VB-Cables just
reset the things correctly. But of course changing the name of audio driver
affects the audio configuration of your different application.



Does Anyone knows something about that !?



Regards

Vincent Burel

www.vb-audio.com

www.mt128.com

www.vb-cable.com

www.voicemeeter.com

https://www.facebook.com/vbaudiosoftware

https://plus.google.com/110557338955940627490

https://twitter.com/VB_Audio





Other related posts: