[wdmaudiodev] Re: WIN11 did not fix the audio driver installation problem...
- From: "Vincent Burel \(VB-Audio\)" <vincent.burel@xxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Mon, 8 Nov 2021 09:13:44 +0100
Hello Matthew & Gary
As you were suggesting one year ago,
Did you ask to PnP team why the Windows Audio Driver Installation procedure
does not take the Driver Hardware ID in account ?
(as it as been explained by Gary too see discussion history).
We are in November 2021 and I see that Win11 does not fix anything about
this question.
Regards
Vincent Burel
De : Matthew van Eerde (^_^) [ <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx>
mailto:Matthew.van.Eerde@xxxxxxxxxxxxx] ;
Envoyé : lundi 30 novembre 2020 21:21
À : <mailto:vincent.burel@xxxxxxxxxxxx> vincent.burel@xxxxxxxxxxxx; Gary
Daniels
Objet : RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
Thats the right question to ask. I dont know the answer. I think at this
point we need to loop in the PnP team and ask them.
From: Vincent Burel (VB-Audio) <mailto:vincent.burel@xxxxxxxxxxxx>
Sent: Friday, November 20, 2020 10:01 PM
To: Matthew van Eerde (^_^) <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx> ; Gary
Daniels <mailto:Gary.Daniels@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs
- second part.
Ok, but why their key-string starts by an hardware ID in your examples ?
what does it mean on the inf level?
Because many drivers are using this REFERENCE STRING
AddInterface=%KSCATEGORY_AUDIO%,"Topo",xxx
AddInterface=%KSCATEGORY_AUDIO%,"Wave",xxx
AddInterface=%KSCATEGORY_CAPTURE%,"Wave",xxx
AddInterface=%KSCATEGORY_RENDER%,"Wave",xxx
Why Windows Installation process would add hardwareID at the beginning of
this string ? what must be added in the INF to have this behavior ?
Regards
Vincent Burel
De : Matthew van Eerde (^_^) [mailto:Matthew.van.Eerde@xxxxxxxxxxxxx] ;
Envoyé : vendredi 20 novembre 2020 21:17
À : vincent.burel@xxxxxxxxxxxx; Gary Daniels
Objet : RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
Heres an example of a driver that does NOT have the problem: the Microsoft
USB Audio class driver. This is from the USB microphone on my desk.
\\?\usb#vid_b58e
<file:///\\%3f\usb%23vid_b58e&pid_9e84&mi_00%237&78cc2bf&33&0000%23%7b6994ad
04-93ef-11d0-a3cc-00a0c9223196%7d\global>
&pid_9e84&mi_00#7&78cc2bf&33&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\glo
bal
In this case, the interface name is Global rather than Wave or Topo
but thats fine.
The reason this driver doesnt have the problem is not because of the
Global vs. Wave or Topo string its because of the
usb#vid_b58e&pid_9e84&mi_00#7&78cc2bf&33&0000 string. This is the hardware
instance ID of the USB audio device. If I had multiple USB audio devices
plugged in at once, they would have different hardware instance IDs, and
therefore these reference strings would be different in their entirety, even
though their global strings are the same.
Heres another example of a driver that does NOT have the problem: the
Realtek audio driver on my system.
\\?\hdaudio#func_01
<file:///\\%3f\hdaudio%23func_01&ven_10ec&dev_0262&subsys_103c1589&rev_1002%
234&9d29fb7&0&0001%23%7b6994ad04-93ef-11d0-a3cc-00a0c9223196%7d\rtmicintopo>
&ven_10ec&dev_0262&subsys_103c1589&rev_1002#4&9d29fb7&0&0001#{6994ad04-93ef-
11d0-a3cc-00a0c9223196}\rtmicintopo
\\?\hdaudio#func_01
<file:///\\%3f\hdaudio%23func_01&ven_10ec&dev_0262&subsys_103c1589&rev_1002%
234&9d29fb7&0&0001%23%7b6994ad04-93ef-11d0-a3cc-00a0c9223196%7d\rtlineinwave
&ven_10ec&dev_0262&subsys_103c1589&rev_1002#4&9d29fb7&0&0001#{6994ad04-93ef-
11d0-a3cc-00a0c9223196}\rtlineinwave
Here the hardware instance ID is the same between the two strings. But
because the Realtek HD Audio driver exposes different short names for line
input and microphone input, it doesnt hit this problem.
So this problem is really limited to the case where there are multiple
ROOT\MEDIA drivers installed simultaneously, and some two of them use the
same interface name.
As far as I know, only VB-Audio does this.
From: Vincent Burel (VB-Audio) <mailto:vincent.burel@xxxxxxxxxxxx>
Sent: Friday, November 20, 2020 12:02 PM
To: Matthew van Eerde (^_^) <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx> ; Gary
Daniels <mailto:Gary.Daniels@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs
- second part.
I guess all audio driver using the same reference string like this:
AddInterface=%KSCATEGORY_AUDIO%,"Topo",xxx
AddInterface=%KSCATEGORY_AUDIO%,"Wave",xxx
AddInterface=%KSCATEGORY_CAPTURE%,"Wave",xxx
AddInterface=%KSCATEGORY_RENDER%,"Wave",xxx
Or all driver having reference string in common
Regards
Vincent Burel
De : Matthew van Eerde (^_^) [mailto:Matthew.van.Eerde@xxxxxxxxxxxxx] ;
Envoyé : vendredi 20 novembre 2020 19:21
À : vincent.burel@xxxxxxxxxxxx; Gary Daniels
Objet : RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
· YOU MUST UNDERSTAND That Im not the only one impacted by this
problem, and you will be surprised to see how much it will remove a lot of
strange audio problems.
Can you give an example of someone else who is also impacted by this
problem?
From: Vincent Burel (VB-Audio) <mailto:vincent.burel@xxxxxxxxxxxx>
Sent: Friday, November 20, 2020 10:19 AM
To: Matthew van Eerde (^_^) <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx> ; Gary
Daniels <mailto:Gary.Daniels@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs
- second part.
Sorry no, I cannot.
My planning is full for 3 months at least.
But you have the solution already: just use driver HardwareID to build your
installation key-strings...
Regards
Vincent Burel
De : Matthew van Eerde (^_^) [mailto:Matthew.van.Eerde@xxxxxxxxxxxxx] ;
Envoyé : vendredi 20 novembre 2020 16:38
À : vincent.burel@xxxxxxxxxxxx; Gary Daniels
Objet : RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
* Customize the reference string in the inf & driver binary for each
of these endpoints
Vincent, can you try this in a private build of your driver?
From: Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, November 19, 2020 10:37:08 PM
To: Gary Daniels <Gary.Daniels@xxxxxxxxxxxxx>; Matthew van Eerde (^_^)
<Matthew.van.Eerde@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs
- second part.
Hello,
Well, this not very clear to me, but Im not sure to make a specific process
just for our drivers is the right idea.
What you asked me to do in your previous e-mail is simply what you are
expected from Windows.
Because basically, You asked to add a unique ID to our reference string
but In a driver INF file, the following string are unique (from any other
drivers):
DeviceName="VB-Audio VoiceMeeter VAIO"
HardwareId="VBAudioVMVAIO"
ServiceName="VBAudioVMVAIOMME"
DriverFile="vbaudio_vmvaio64_win10.sys"
Why dont you simply use the HardwareID to generate your unique Key-String
for the installation process
Exactly Something like you asked for finally, but automatically done by
Windows:
<file:///\\%3F\ROOT#MEDIA#0003#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy>
\\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topology%Hardware
ID%
YOU MUST UNDERSTAND That Im not the only one impacted by this problem, and
you will be surprised to see how much it will remove a lot of strange audio
problems.
So I recommend you to study a general fix first.
We will certainly change our reference string (for unique one) in the next
driver update, but it wont be before 2021.Q3 and it wont fix everything
since we know that some other driver are impacted by this problem which
can disturb overall audio stack anyway (our Voicemeeter application is
expected to be connected to all installed audio device in the same time so
if one is fucked up , the audio behavior becomes undefined).
Thanks for your help anyway. Let me know your progression on this subject if
any.
Regards
Vincent Burel
De : Gary Daniels [mailto:Gary.Daniels@xxxxxxxxxxxxx] ;
Envoyé : jeudi 19 novembre 2020 21:54
À : Matthew van Eerde (^_^); vincent.burel@xxxxxxxxxxxx
Objet : Re: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
The hardware ID is a list, not a single id, and it often contains multiple
id's which align to different driver installations that coexist in the
system, with only one active at a time. For example, you might see the
hardware id list contain both HDAUDIO\func&ven and INTELAUDIO\func&ven, the
func and ven may or may not be the same, the hdaudio class driver could be
installed against to the first id, and an intel driver installed against to
the second id, and we have audio endpoint data for both. The list of
hardware id's can also change when firmware is updated. We do not cache the
hardware ids on the audio endpoint, and do not have the previous OS hardware
id list available during audio endpoint migration, so a hardware id check is
not possible at all right now. Also, to add an umbrella check for hardware
id(s) to the migration process would be problematic and high risk for the
ecosystem as a whole, and could cause missed migration opportunities.
So, the problem you are encountering is a concern only for legacy style root
enumerated devices which use the same reference string. The existing
migration process works correctly for the many different cases which are
needed for devices with real hardware.
I see that in your specific case you do have a unique
DEVPKEY_Device_MatchingDeviceId for each of the driver installations. The
other root enumerated devices I have assisted with were reusing the same inf
and driver binary in order to get code reuse, which resulted in the same
MatchingDeviceId as well. To get the benefits of code reuse and still meet
OS upgrade constraints, those implementations required runtime reference
string selection. This made the solution much more difficult to implement
than in your case, where you have different inf's and driver binaries that
could be targeted at compile time.
This variable does make the vbaudio situation unique among the other root
enumerated software devices, and does open the possibility of adding an
additional check enforcing that migration of root enumerated devices also
have the same MatchingDeviceId. I do not believe this check would regress
any of the other root enumerated products i've looked at, and could help in
this particular case. We'll have to file a bug and do some additional
investigation and flighting to ensure it doesn't cause any regressions. I
can't make any guarantees that the check will be added, but I'm happy to
investigate further to see if I can help.
<mailto:Matthew.van.Eerde@xxxxxxxxxxxxx> @Matthew van Eerde (^_^) do you
want to file a bug to me to check for a matching
DEVPKEY_Device_MatchingDeviceId when migrating devices with ROOT
DEVPKEY_Device_EnumeratorName?
Vincent, I do want to set expectations, this will not solve your problem
overnight.
Here's the issue. Luckily, i started caching the MatchingDeviceId property
in the mmdevice store about a year ago due to changes unrelated to
migration. This property is only available for Windows 20H2 and later
releases. Older releases will not have this property available during OS
upgrade, so this check is simply not possible for upgrades from those
releases.
If i add a new migration check for the next major release of Windows, only
users upgrading from 20H2 and later to the release with this check will
benefit from the check. Users which do a skip head, skipping 20H2 and going
from 19H1 or 20H1 to the release with this new check, will get the same
behavior that they get right now.
Also, this change will not meet windows servicing requirements, as the
existing behavior has been the design for decades. Users still using and
upgrading prior OS versions, many are businesses, won't see a benefit until
they first go to an OS build with the change to collect the
MatchingDeviceId, and then an OS upgrade which checks it.
Given that you are using different driver binaries and INF's, the most
expedient solution is still to change the reference strings to be something
like what i proposed below.
-Gary
Sent from Outlook
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Faka.ms%2Fw
eboutlook&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804482
6470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529449
43713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=aQI%2BmNyO%2F%2Bw4JET9av2Osnw5yJE6ZXEaAJC6
uIEKxdI%3D&reserved=0>
From: Vincent Burel (VB-Audio) < <mailto:vincent.burel@xxxxxxxxxxxx>
vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, November 19, 2020 10:06 AM
To: Gary Daniels < <mailto:Gary.Daniels@xxxxxxxxxxxxx>
Gary.Daniels@xxxxxxxxxxxxx>; Matthew van Eerde (^_^) <
<mailto:Matthew.van.Eerde@xxxxxxxxxxxxx> Matthew.van.Eerde@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs
- second part.
Yes, we know that!
The question is why Windows does not take the Hardware ID in account ?
(only the hardware ID is expected to be unique, from a driver to another).
This problem does not concern only our drivers
Regards
Vincent Burel
De : Gary Daniels [mailto:Gary.Daniels@xxxxxxxxxxxxx] ;
Envoyé : jeudi 19 novembre 2020 18:53
À : Matthew van Eerde (^_^); vincent.burel@xxxxxxxxxxxx
Objet : Re: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
The device interface path for VB-Audio Virtual Cable is:
<file:///\\%3f\ROOT#MEDIA#0003#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topology
The device interface path for VB-Audio VoiceMeeter AUX VAIO is:
<file:///\\%3f\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topology
The device interface path for VB-Audio VoiceMeeter VAIO is:
<file:///\\%3f\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topology
The device interface path for VB-Audio VoiceMeeter VAIO3 is:
<file:///\\%3f\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topology
The number X'd out is present on these devices, however this number is tied
to installation order and is subject to change during OS upgrade or driver
update, so it is ignored during the upgrade process.
The windows audio system uses this string to match the audio endpoint to the
audio interface for migration after OS upgrade. As you can see, all the
strings are identical, so the migration system is unable to accurately match
the audio endpoint to the audio interface.
As i stated in the public forums, this is a limitation of the OS upgrade
design and this limitation exists for all released versions of windows going
back through 9x.
You have 4 different inf's with 4 different driver binaries installed, all
installed as a root enumerated device and all using identical interface id
strings:
vbmmecable64_win7.inf & vbaudio_cable_64_win7.sys
vbvmauxvaio64_win10.inf & vbaudio_vmauxvaio64_win10.sys
vbvmvaio64_win10.inv & vbaudio_vmvaio64_win10.sys
vbvmvaio364_win10.inf & vbaudio_vmvaio364_win10.sys
So, the driver fix for this issue is quite simple. Customize the reference
string in the inf & driver binary for each of these endpoints.
For example, using the following reference strings for the endpoints will
resolve the problem:
The device interface path for VB-Audio Virtual Cable is:
<file:///\\%3F\ROOT#MEDIA#0003#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy>
\\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\TopologyVirtualCa
ble
The device interface path for VB-Audio VoiceMeeter AUX VAIO is:
<file:///\\%3F\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy>
\\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\TopologyAUXVAIO
The device interface path for VB-Audio VoiceMeeter VAIO is:
<file:///\\%3F\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\TopologyVAIO
The device interface path for VB-Audio VoiceMeeter VAIO3 is:
<file:///\\%3F\ROOT#MEDIA#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\Topolo
gy> \\?\ROOT#MEDIA#XXXX#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\TopologyVAIO3
-Gary
Sent from Outlook
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Faka.ms%2Fw
eboutlook&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804482
6470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529449
43713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=aQI%2BmNyO%2F%2Bw4JET9av2Osnw5yJE6ZXEaAJC6
uIEKxdI%3D&reserved=0>
From: Vincent Burel (VB-Audio) < <mailto:vincent.burel@xxxxxxxxxxxx>
vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, November 19, 2020 8:19 AM
To: Matthew van Eerde (^_^) < <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx>
Matthew.van.Eerde@xxxxxxxxxxxxx>
Cc: Matthew van Eerde (^_^) < <mailto:Matthew.van.Eerde@xxxxxxxxxxxxx>
Matthew.van.Eerde@xxxxxxxxxxxxx>; Gary Daniels <
<mailto:Gary.Daniels@xxxxxxxxxxxxx> Gary.Daniels@xxxxxxxxxxxxx>
Subject: [EXTERNAL] RE: WIN10 Update and audio driver installation bugs -
second part.
Hello,
So, the VBAudioPC2.pnp should have shown you a problem with VB-CABLE &
Voicemeeter devices installation (as we described in previous message)...
To fix this on our side, we de-installed Voicemeeter Potato+ REBOOT +
de-install VB-CABLE + reboot
- I generate VBAudioPC3.pnp after that (to show you the current
state)
https://download.vb-audio.com/Download/VBAudioPC3_pnp.zip
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.
vb-audio.com%2FDownload%2FVBAudioPC3_pnp.zip&data=04%7C01%7CMatthew.van.Eerd
e%40microsoft.com%7Cbb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2
d7cd011db47%7C1%7C1%7C637415352944953670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=tPyQz5v
Hl5zCWTGEPLiIcOJ1BUh6CKkNajVUSwo8PpA%3D&reserved=0>
Then I re-install VB-CABLE + REBOOT and Voicemeeter Potato + REBOOT
And all is well installed again, VB-CABLE and Voicemeeter VAIO appear with
the right name, and there no strange stuff in audio routing and audio device
behavior
- I generate VBAudioPC4.pnp after that
https://download.vb-audio.com/Download/VBAudioPC4_pnp.zip
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.
vb-audio.com%2FDownload%2FVBAudioPC4_pnp.zip&data=04%7C01%7CMatthew.van.Eerd
e%40microsoft.com%7Cbb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2
d7cd011db47%7C1%7C1%7C637415352944953670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BzfC8JV
AAQB%2BKDxUerSQ%2F05Tk%2BqOyCLUEQ%2FtatkH4O4%3D&reserved=0>
this last pnp file should show a correct installation of our 4 audio devices
(VB-CABLE and the 3x Voicemeeter audio device).
This experience shows at least that the audio driver installation process is
not stable.
The 4 pnp file should help you to understand why Windows is merging audio
drivers pin in some case during installation (or de-installation or both)
and fixe it...
Regards
Vincent Burel
De : Vincent Burel (VB-Audio) [mailto:vincent.burel@xxxxxxxxxxxx] ;
Envoyé : mercredi 4 novembre 2020 13:57
À : 'Matthew van Eerde (^_^)'
Cc : 'mateer@xxxxxxxxxxxxx'
Objet : WIN10 Update and audio driver installation bugs.
Hello,
After our discussion on twitter, Ive switched ON a PC-TEST WIN10 computer
(off since 2 months I guess)
And we got a WIN10 update while we were updating Voicemeeter too so it
means the WIN10 update has been done after having de-installed previous
Voicemeeter version and reboot Then again when we installed latest
Voicemeeter version and REBOOT we got other WIN10 update.
And we got the typical problem we talked about: the VB-CABLE Audio device
playback pin is renamed in Voicemeeter AUX !?! (2 different drivers with one
getting pin name of another newly installed).
The chance maybe, is that I can provide you with 2x PNP file of the same PC
- VBAudioPC1.pnp before win10 update
- VBAudioPC2.pnp after win10 update and Voicemeeter update
I placed these two file in two ZIP file on my download server:
https://download.vb-audio.com/Download/VBAudioPC1_pnp.zip
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.
vb-audio.com%2FDownload%2FVBAudioPC1_pnp.zip&data=04%7C01%7CMatthew.van.Eerd
e%40microsoft.com%7Cbb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2
d7cd011db47%7C1%7C1%7C637415352944963625%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=0gN3NR%
2BnTAr8bS1hwCQG3Jm7hTSA%2FhkDN2cHRAvYYC8%3D&reserved=0>
and
https://download.vb-audio.com/Download/VBAudioPC2_pnp.zip
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.
vb-audio.com%2FDownload%2FVBAudioPC2_pnp.zip&data=04%7C01%7CMatthew.van.Eerd
e%40microsoft.com%7Cbb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2
d7cd011db47%7C1%7C0%7C637415352944963625%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=3CT9lPT
2RM5f9yIFxt2kgxxgM7N%2Bm6HUjdOw8Yf7628%3D&reserved=0>
Regards
Vincent Burel
www.vb-audio.com
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vb-aud
io.com%2F&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804482
6470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529449
73583%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=pWPtCzgSGN7GstUMILAZkuaNx%2F%2FeoItS5Gde7D
V4%2FPw%3D&reserved=0>
www.mt128.com
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mt128.
com%2F&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804482647
0408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529449735
83%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
WwiLCJXVCI6Mn0%3D%7C2000&sdata=3ZqtvBkqHf37ZdL13CBerm4TSNG8XAlJeFLz2L6c%2F1c
%3D&reserved=0>
www.vb-cable.com
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vb-cab
le.com%2F&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804482
6470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529449
83537%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=P4B0I64KIihp3bW4tNfSn%2B2n4KzOfOwPw8OpwoYH
eaA%3D&reserved=0>
www.voicemeeter.com
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.voicem
eeter.com%2F&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe804
4826470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153529
44993495%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BJi3yryiGaviRyDWz8rRgN8DfMjNSv2kaQ6Uy7u
UqAg%3D&reserved=0>
www.spectralissime.com
<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spectr
alissime.com%2F&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe
8044826470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374153
52944993495%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=CxrYgpQflIi%2FkTBhtfpLuTkIKB89JbKnCv
JPSRYuwQI%3D&reserved=0>
https://www.facebook.com/vbaudiosoftware
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb
ook.com%2Fvbaudiosoftware&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7
Cbb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0
%7C637415352945003451%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2
luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=sLEtgdemqlmHrKuwzA73mvqITc
18qeS6J%2Bgv4xKbamE%3D&reserved=0>
https://twitter.com/VB_Audio
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.c
om%2FVB_Audio&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7Cbb07141fe80
44826470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637415352
945003451%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
I6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=H7AL4EZRo%2B1%2BXVEbCy3wYveszgQmmZ0Yis
SYGTTG0hg%3D&reserved=0>
https://www.youtube.com/vbaudiosoftware
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu
be.com%2Fvbaudiosoftware&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7C
bb07141fe8044826470408d88de22ef9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%
7C637415352945013408%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l
uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=hW5ptOvboK5JNg440TU0ZC278aE
gw%2FcqMh28C6NArsQ%3D&reserved=0>
- Follow-Ups:
Other related posts:
- » [wdmaudiodev] WIN11 did not fix the audio driver installation problem...- Vincent Burel (VB-Audio)
- » [wdmaudiodev] Re: WIN11 did not fix the audio driver installation problem... - Vincent Burel (VB-Audio)
- » [wdmaudiodev] Re: WIN11 did not fix the audio driver installation problem...- Vincent Burel (VB-Audio)