Installing the Microsoft class driver(s) for USB Audio devices

This blog post has moved to https://matthewvaneerde.wordpress.com/2016/09/15/installing-the-microsoft-class-drivers-for-usb-audio-devices/

Comments

  • Anonymous
    September 21, 2016
    I recently bought a Lumia 950XL. I tried connecting Blue Yeti Pro mic using a USB 3.0 cable to it. But the mic is not recognized. Is there anything being done to improve the usb/midi audio driver situation in windows 10 mobile? Also, after upgrading my older pcs to windows 10, none of my usb audio devices (Behringer Xenyx 1622 mixer, Roland SH-201, Zoom G9.2tt, Boss GS-10 are being recognized). Most of these manufacturers don't seem to be bothered about windows 10 and are not willing to update the drivers. Now all these devices are rendered completely useless as usb audio interfaces unless I revert back to windows 7. Is MS doing something to address such issues in windows 10 builds? This scenario probably gives you a picture of why so many folks don't prefer not to update to W10 from W7 while MS is pushing aggressively the users towards W10. Unless these important basic productivity affecting issues are taken care (which practically makes expensive equipment that the user has invested in completely useless), there is no point in MS pushing people to update to Windows 10 with just some fancy minor user interface updates (such as dark theme).
    • Anonymous
      September 22, 2016
      Hi Arun. Thanks for your feedback. I will address the two issues you raised separately.> Blue Yeti Pro mic on Lumia 950XL is not recognizedHere's the current picture:1. USB Audio 1.0 devices work on the Lumia 950 XL now, both playback and recording2. USB Audio 2.0 devices work on the Lumia 950 XL if you install a build >= 14912, for playback only3. USB Audio 2.0 recording devices will work on the Lumia 950 XL once we add recording support to the class driverI took a look at http://www.bluemic.com/products/yeti-pro/ and based on the bitrate advertised I think this is a USB Audio 2.0 device (USB Audio 1.0 can't deliver that kind of throughput.) So once we add recording support to the class driver it should work with your Lumia 950 XL. https://blogs.windows.com/windowsexperience/2016/09/21/announcing-windows-10-insider-preview-build-14931-for-pc/"This is an early version of the driver that does not have all features enabled, for e.g.: only playback (render) is supported with this version. Recording (capture) support is scheduled to arrive in later iterations."> USB audio devices are rendered completely useless as usb audio interfaces unless I revert back to windows 7Ouch. That's not supposed to happen. Any peripheral that works on Windows 7 is supposed to work on Windows 10 as well; the driver you had installed on Windows 7 should be carried forward by the upgrade, and Windows 10 should work with that driver just as well as Windows 7 did.Or if there's a better driver on Windows Update, you might get that; but the better driver should be, um, well, better.So... I think there's a bug here (or perhaps a couple of bugs.) Would you be willing to help us track it down? The simplest way to get the information to us would be to install Windows 10 again, and use the Feedback Hub to submit a "problem" feedback under Hardware, Devices, and Drivers | Audio, sound, and volume.This will gather some logs; if you use the "Copy Link" feature to send me a direct link, I can look at the logs and see if they give us all the info we need, or I might ask you for more.
      • Anonymous
        September 23, 2016
        Hi Maurits,Thank you very much for the reply. I am looking forward to using the Lumia 950XL with my Blue Yeti Pro mic once the new driver/OS updates with recording options are available. With regards to usb audio interfaces, I have tried (many times) various methods of installing/un-installing the usb audio interface drivers for Roland SH-201, Boss GS-10, Zoom G9.2tt and more recently Behringer Xenyx 1622. I will try them once again some time next week when I get some time and send any troubleshooting information to you as feedback. To begin with here are the details of what I have attempted and the links to drivers (from the manufacturer's website) that I have tried using in windows 10. I had written Roland about SH-201 and they said that they would no longer update the drivers for this product beyond Windows 8. This synthesizer was in the market as late as 2010. Here is the link to the available driver for windows 8/windows 7 at their website. The irony is that some of the functions of this synth can only be changed using the software provided by the company which will not work unless the operating system recognizes the hardware through drivers.https://www.roland.com/us/support/by_product/sh-201/updates_drivers/Here is a link for drivers of Boss GS-10https://www.boss.info/us/support/by_product/gs-10/updates_drivers/Similarly I tried installing the drivers for Zoom G9.2tt. But the Windows 10 system is unable to recognize it. Here is the link for the drivers:https://www.zoom.co.jp/products/guitar-bass-effects/guitar/g92tt-guitar-effects-console#downloadshttps://www.zoom.co.jp/sites/default/files/products/downloads/software/E_G-Series_ASIO_win64_v2.0.0_6.zipI even tried using the new G-series drivers windows 10 version given in the link below for a similar newer product. It still does not work.https://www.zoom.co.jp/products/guitar/g5n-multi-effects-processor#downloadshttps://www.zoom.co.jp/sites/default/files/products/downloads/software/E_New_G-Series_ASIO_win64.zipBehringer website claims that asio4all drivers should be compatible for Xenyx 1622. But they are not. Here is the link:http://www.music-group.com/brand/c/Behringer/downloads?active=DownloadsAll these have been working with windows 7 and most of them were ok with windows 8 too. But now all these equipment are pretty much useless as usb audio interfaces with Windows 10. I could get the Behringer Xenyx 1622 to playback media from the pc through USB. But it is not recognized by the PC as an audio input device through usb. What concerns me most (regarding Windows 10) is the fact that these devices are made by different manufacturers and yet were working with Windows 7. But with windows 10, none of them are working anymore.Thanking you,Arun
        • Anonymous
          December 21, 2016
          To Arun.do these devices work with ASIO driver?
          • Anonymous
            January 08, 2017
            Hi Mauritis,I could get Roland SH201 and Boss GS-10 working by using the methods suggested through a youtube video showing how to get older roland devices operational with windows 10. But the Behringer usb mixer Xenyx 1622 is still not working as it should. The driver seems to install properly without any error message but input through USB does not function. I have submitted a feedback (8/1/2016 around 8:10 pm EST) through feedback hub in hardware devices topic under sub section usb attached devices. I have attached three screen shots of supposedly installation event logs along with this feedback in the feedback hub I was trying to get a link to the feedback submitted. But I am unable to get the link from the feedback hub app.And to answer the other question, asio4all does not seem to be helpful. None of the attempts with asio4all yielded positive results.
        • Anonymous
          January 08, 2017
          Hi Maurits,Here is the feedback link: https://aka.ms/Ei9rsy. This is about Behringer X1622 usb audio driver installation on windows 10. Audio input through usb does not function after installation.
  • Anonymous
    September 22, 2016
    Hi,I've tried it and I have noticed that the USB 2.0 Audio support is up to 24bit/44.1 kHz at the moment. What about 96kHz and 192kHz? Do you plan to implement it, too?
    • Anonymous
      September 22, 2016
      The comment has been removed
      • Anonymous
        September 22, 2016
        Hallo Maurits,feedback-hub:?contextid=68&feedbackid=ea926916-c255-46b0-a01a-347d76fa9f8c&form=1&src=2 Regards,cas
      • Anonymous
        September 27, 2016
        Hi Maurits,the USB 2.0 Audio on Windows is important right now, but do you plan to implement the USB Audio Device Class 3.0 one day, too?Regards,Cas
        • Anonymous
          September 28, 2016
          Hi Maurits,feedback-hub:?contextid=68&feedbackid=7c295f04-2f0e-4825-9774-e926352063d4&form=1&src=2 Regards,Cas
  • Anonymous
    September 23, 2016
    Hi, What about enable audio recording from external mic during video recording? thanks !
  • Anonymous
    September 23, 2016
    The comment has been removed
  • Anonymous
    September 27, 2016
    Hi Maurits,the USB 2.0 Audio on Windows is important right now, but do you plan to implement the USB Audio Device Class 3.0 one day, too?Regards,Cas
    • Anonymous
      September 27, 2016
      A reasonable question. Can you submit a "suggestion" in the Feedback Hub, under Hardware, Devices, and Drivers | Audio, sound, and volume, and then post a feedback-hub: link here so like-minded people can upvote it?
      • Anonymous
        September 28, 2016
        Hi Maurits,feedback-hub:?contextid=68&feedbackid=7c295f04-2f0e-4825-9774-e926352063d4&form=1&src=2 Regards,Cas
  • Anonymous
    September 27, 2016
    Hi Maurits, great work so far I am excited to see this finally being built into windows!I am having issues with the new class driver in Exclusive mode (driven from Roon to my Esoteric K-01x USB Dac. I submitted feedback on this issue here: feedback-hub:?contextid=68&feedbackid=312a4668-5d06-426d-80ba-be1e87aa0615&form=1&src=2
  • Anonymous
    September 29, 2016
    Tried this on a Focusrite 18i20 (1st gen) which is USB compliant (One of the few USB audio devices which work under Linux).The USB 2.0 driver is in the list, After selecting and reboot the device manager shows and exclamation mark for this driver.Going back to let Window select the best driver,which find the 18i20 driver, audio works again
    • Anonymous
      December 02, 2016
      Thanks for giving the class driver a try!We're tracking this under this feedback item: http://aka.ms/Cdj9ed . We've figured out why the driver is Code 10'ing and we're trying to decide what to do about it.
  • Anonymous
    October 03, 2016
    Hi Maurits. I bought a Lumia 950 XL one moth ago and with it I bought also an external USB audio DAC: LG Hi-Fi Plus B&O PLAY. With the Anniversary Update build, no way to make it work. A notification told me the USB device could not work and to try it on a PC. So I decided to join the fast ring channel and since 2 builds (now 14936), at least when I connect the USB DAC and then the earphones, the DAC is recognized as external screen and the audio works, badly but works. Basically the audio is distorted and the pitch is wrong, lowered. Connecting the DAC, the Gadget app doesn't see it. But when it's plugged, the earphones buttons + - and on/off work. Should I expect improvements on this side, so my audio DAC will work properly, everntually? I read on other forums that DACs such as Dragonfly works perfectly. Would be also appreciated a complete audio interface with paramenters to adjust, such as sample rate/frequency and so on. I'm used that on Android, Poweramp app for example, in the latest builds let you interact directly with the audio DAC of the phone. In the meanwhile I send my feedback in the Feedback Hub hoping my DAC will work, since it sounds a lot better than the built in Qualcomm DAC. Thanks in advace!
    • Anonymous
      October 03, 2016
      Thanks for the detailed response!Would you be willing to submit each of these via the Feedback Hub? https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/> the DAC is recognized as external screenThis should be a "problem" report under "Mobile Environment | Volume and audio controls". Include a screenshot.> the audio is distorted and the pitch is wrong, loweredThis should be a "problem" report under "Hardware, Devices, and Drivers | Audio, sound, and volume". Include "Media issues" logs of the problem in action> the Gadget app doesn’t see itThis should be a "problem" report under "Apps and Games | Gadgets"
      • Anonymous
        October 04, 2016
        Thank you so much for your reply, Maurits. I took the time to send my feedback in the proper sections as you suggested. I made 3 videos and attached the links in my feedback text, so they can see the issue and hear the issue, since I also connected the DAC with a 3,5" jack to the A/V Receiver (aux-in) instead of plugging the earphones, so you can actually hear the distorted audio. In the Italian version of the Feedback App on my Lumia, the "Gadgets" sub-category under Apps and Games, doesn't exists, so I sent that particular feedback in the category: Hardware, Devices, and Drivers | USB connected devices (or whatever is written in English). I guess the moderators will move the feedback in the correct section, looking at the title: "The Gadget app doesn't recognize my USB DAC".Thanks once again, hoping this isse can be easily fixed in one of the next fast ring builds.
        • Anonymous
          October 05, 2016
          Thanks!
          • Anonymous
            December 01, 2016
            The comment has been removed
  • Anonymous
    October 09, 2016
    When can we expect USB Audio class 2 support to hit regular Windows 10?
    • Anonymous
      October 13, 2016
      How can I obtain this driver? Can I install it on windows 8.1?
      • Anonymous
        October 13, 2016
        The driver comes as part of Windows. It is included in Windows builds 14912 and later. It is not possible to apply it to older versions of Windows; in particular, there is no way to download it from somewhere.
  • Anonymous
    October 14, 2016
    Hi Maurits, I've just updated 950xl to 14393.321, and tried using with my "Schiit Bifrost Multibit" usb DAC. Unfortunately when connected there is an OS message that appears saying device not working correctly and try connecting to pc instead. However, my usb cable lights up blue and the dac "clicks" which is registering a connection to the host. I use the dac with my laptop usually with Windows 10 drivers bit want FYI use my phone as source.... Any ideas? Thanks, Rgds, Dee.
    • Anonymous
      October 14, 2016
      I took a look at the specs for your USB Audio device and it appears to be USB Audio 2.0 http://schiit.com/products/bifrostThe Windows build you're running (14393) has a USB Audio 1.0 driver built in, but not a USB Audio 2.0 driverIf you join the Windows Insider program and get a build >= 14912, that will include the USB Audio 2.0 driver; this should work with your USB Audio device. If it doesn't, please file feedback.In particular, it looks like at this time the current builds are:* Windows Insider Fast for Mobile: 14946 (this DOES have the USB Audio 2.0 driver)* Windows Insider Slow for Mobile: 14393 (DOES NOT have it)* Windows Insider Fast for PC: 14946 (DOES have it)* Windows Insider Slow for PC: 14931 (DOES have it)
  • Anonymous
    October 20, 2016
    Hi Maurits,I recently bought a Teac AI-101DA and connected it to my Surface Pro 4 with Windows 10 (14931.1000 Korean). I noticed something:1) it is recognized as a USB 2.0 Audio device but is fixed at 24-bit, 32 KHz.2) after installing Teac's driver, it does not sound at all with no volume meter in Sound panel (volume meter completely disappeared), and3) in Properties panel for the Teac, there is no "Enhancement" nor "Advanced" tabs, and "Level" tab is broken. (has no content in it.)I don't know whether these problems from Teac's driver or from some conflicts with the new USB audio driver... Anyway it just works on my Raspberry Pi 2 (with Raspbian)
    • Anonymous
      December 02, 2016
      Hi JS - thanks for giving the class driver a try!For the 24-bit, 32 kHz issue I believe you're running into this http://aka.ms/Slvjqe which is fixed in 14940 and later builds.
  • Anonymous
    October 30, 2016
    Hi Maurits,I have no problem to play the 24bit/192kHz FlLACs files with my Meridian Explorer now (Build 14955).I can switch between the Meridian ASIO and USB 2.0 Audio driver without problems, too.Regards,Cas
  • Anonymous
    November 06, 2016
    Just tried an USB_Audio 2.0 Device (XMOS XS1) with its Evaluation driver. Works fine - but, of couse, there some noise after 1 hour's use (evaluation sw) ....Since I'm content with 24/96 for the time being - can I use the Win10 1.0 driver until the 2.0 is out? It doesnts show up when looking for drivers.
    • Anonymous
      December 02, 2016
      The USB Audio 1.0 driver will only work on USB Audio 1.0 devices, not USB Audio 2.0.
      • Anonymous
        December 06, 2016
        Thanks!
        • Anonymous
          April 06, 2017
          Installed 15063.13 today - usbaudio2.sys is in place but doesn't show up in the update list. Only the manufacturer's driver.Is that ok?Thanks in advance.
          • Anonymous
            April 06, 2017
            Sorry for bothering!! Everything works perfect after deinstaling the factory driver ....Bernd
  • Anonymous
    November 16, 2016
    It works fine
  • Anonymous
    November 22, 2016
    this works amazingly well ,what a relief when updating drivers from new hard ware installs ,constantly switching out drives and memory and I-7 cores. kids trashed this p.c until I resurrected it by using cmos jump method on main board.took almostb5 minutes .
  • Anonymous
    November 28, 2016
    The comment has been removed
    • Anonymous
      November 28, 2016
      I found this set of specs for the IDOL 4S http://www.alcatelonetouch.us/idol-4s-no-vr (click on Technical Specifications)It looks like it has a micro-USB port; I see no mention of host mode, so I while I think you can plug it in to a PC as a peripheral, I don't think it supports plugging peripherals into it.But just to be sure I would suggest contacting Alcatel to confirm.
  • Anonymous
    December 01, 2016
    Hi Maurits,I had a test in early build when I firstly saw the UAC2.0 support news, it failed. But yesterday I was glad that it ran successfully with a USB D/A on PC with latest build. But for Lumia 930, it didn't work. I don't see any option regarding audio I/O settings in mobile settings. Hope mobiles also can have a smooth support UAC. Could you please elaborate more on UAC support on mobiles?
    • Anonymous
      December 01, 2016
      Yeah, I also would like to now more about the support of USB Audio 2.0 on mobile phones. After around 5 fast-ring builds already, there is no news for my USB DAC LG Hi-Fi Plus. No fix. Audio still distorted. At least, if there was a way to modify the pitch using a tool like Interop Tools, messing around with the registry of my Lumia 950 XL, I could try to fix the issue myself.
    • Anonymous
      December 02, 2016
      If I read the specs ( http://www.gsmarena.com/nokia_lumia_930-6227.php ) correctly, the Lumia 930 USB hardware does not support host mode, so external USB peripherals will not work with it; this includes USB Audio devices as well as things like "on the go" USB hard drives etc.
  • Anonymous
    December 02, 2016
    Hi Maurits,Running 14965.1001. When trying to update the manufacturer provided driver for my DAC (Schiit Yggdrasil, http://schiit.com/products/yggdrasil) to the new USB 2.0 audio driver I get a "This device cannot start. (Code 10)" message.
  • Anonymous
    December 04, 2016
    It would be really great if my Lumia 950 xl would allow my Bluetooth sennheiser urbanite headphones to work with the equalizer app.
  • Anonymous
    December 08, 2016
    Two simple questions:1) If there a list of supported devices?2) Could I request a built-in support for E-MU 0202 sound card?
    • Anonymous
      December 08, 2016
    1. Any device with a "compatible ID" of USB\Class_01&SubClass_??&Prot_20 "should" work. We would like you to try it and tell us if it does work.2) Please plug in the E-MU 0202 and try it - if it doesn't work, please file feedback as described here ( https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/ ) and reply on this thread with a direct link.
      • Anonymous
        December 22, 2016
        I filled bug-report with my USB 2.0 Audio device, and it's here: https://aka.ms/Bzve8t
      • Anonymous
        September 09, 2017
        Sorry, but after release of Creator's Update my E-MU 0202 card still not recognized as suitable! Nor in coming Fall Creator's Update.
  • Anonymous
    December 08, 2016
    End
  • Anonymous
    December 08, 2016
    G=G
  • Anonymous
    December 18, 2016
    Seriously. IS NO LONGER THERE. After my new pc decided to upgrade I have no audio. I need to install it again. I have been trying to get it fix for 9 months. and the computer was purchased last December!Nobody seems to know how to fix it and every one wants to charge me for a program to fix something I should already have. What can you do about that. I spent quite a lot of money and have the worst issues. Now you all want to charge me to fix an issue that I did not cause. I need the sound card / usb audio interface because is not longer there. Help me PLEASE!!!!
    • Anonymous
      December 30, 2016
      A software issue can be easily fixed without any big trouble, usually. What kind of issue do you have, exactly? Did you updrage to USB audio 2.0 and now no sound? If you can, write down your PC config. You can use a software like Speccy to know exactly what harware you have.
  • Anonymous
    December 21, 2016
    Way doing my.
  • Anonymous
    December 24, 2016
    I'm on build 14986 using Bootcamp on Mac. I have a USB dac (no driver is required) which is unrecognized in the device manager. Clicking update driver as above yields no USB audio driver 2 as illustrated.
  • Anonymous
    December 26, 2016
    microphone on camera used as a megaphone, are volume all the way out! does microsoft have a good one? there?
  • Anonymous
    December 28, 2016
    Using build 14986, my Creative E1 Sound Blaster uses the Audio Class 1.0 driver, not the 2.0. If I try to force the 2.0, the 'device doesn't start'. Is there a reason for this?
    • Anonymous
      January 01, 2017
      Sound Blaster E1 seems not a usb audio class 2.0 compliant device. As a result, you cannot use usb audio class 2 driver
  • Anonymous
    January 01, 2017
    The comment has been removed
  • Anonymous
    January 23, 2017
    The comment has been removed
  • Anonymous
    February 07, 2017
    Does the windows 10 buiild 14393 support the native usb audio class 2.0??
    • Anonymous
      February 07, 2017
      14393 has inbox support for USB Audio 1.0 only. Inbox support for USB Audio 2.0 requires build 14912 or later.
      • Anonymous
        February 08, 2017
        The comment has been removed
        • Anonymous
          February 09, 2017
          You can get pre-release versions of Windows by joining the Windows Insider program, or you can wait for the Creator Update.https://insider.windows.com/Yes, the USB Audio 2.0 class driver supports both recording and playback.
          • Anonymous
            February 09, 2017
            Can you confirm that the Creator Update that will be released in April (2017) will support USB Audio 2.0 for both playback and recording.Also, will it support 32bit / 192khz?
          • Anonymous
            February 21, 2017
            I cannot confirm what may or may not be in the Creators Update.I can tell you that the current insider builds have the USB Audio 2.0 driver, and by and large the Creators Update is likely to look very close to the current insider builds.
  • Anonymous
    February 12, 2017
    Hi Maurtis, thanks for your reply, I upgraded the win10 pro from 14393 to 15031.rs.release. My device can be recognized by the win10 pro as the UAC2.0 but the yellow exclamation mark is showed!!. Are there any way or log can know why the yellow exclamation mark is showed??thankLeo
    • Anonymous
      February 13, 2017
      Thanks for trying the class driver. Can you submit a problem report and share a direct link? That will grab some logs which will (hopefully) help us get a clue about what is causing the Code 10.https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/
      • Anonymous
        March 08, 2017
        Hi Maurits, My device can be recognized by win10 pro build 15048 as the mic phone device. but the voice recording app can not use and find the mic phone device. How can I know why my device can be recognized but can not be used for recording?? Is it caused by the wrong USB audio descriptor on device responded to usbaudio2.sys driver??? submit one the problem item to your feedback hubhttps://aka.ms/F4jc1h could you give your advice?? what is lost on my device??
        • Anonymous
          March 08, 2017
          Thanks for the problem report, we'll take a look.
          • Anonymous
            March 13, 2017
            Hi Maurits any susggestion? Does my device reply the wrong descriptor to the usbaudio2.sys so that the recording voice app can not use and not find my device??thankLeo
          • Anonymous
            April 12, 2017
            Hi Maurits, I updated the WIN10 to build 16170 for trying the recording function of the native USB audio 2.0 driver. But the problem that I met in the previous WIN10 build still exists. sorry ,query the question again, Is the recording function ready in the native USB audio 2.0 driver? Are there any device you use for verifying the recording function of the native USB audio 2.0 driver?? or could you recommend any device for test the recording function of the native USB audio 2.0 driver???? I would like to compare with my device.thanks a lot.Leo
          • Anonymous
            July 25, 2017
            Hi Maurits, Our UAC2.0 Mic device still have the same problem: can be recognized by win10 build 1703,16241.1001 as the UAC2.0 mic device but can not be used by the voice recorder application or the other recorder application. from the debug log our device printed, usb host set altinterface 1 to our device ,immediately set altinterface 0 I have feedback :https://aka.ms/Nj9n8u Could you help us check or suggest what is wrong??thankLeo
  • Anonymous
    February 16, 2017
    Hi Maurits,I am currently using the Build 15031.rs2_release, and I have a USB Audio 2.0 device which supports only PCM Type I format with both playback and capture. When connected to Windows 10 Host, the device shows a yellow exclamation mark with error code 10.This device worked with both Ubuntu and Macbook.Some third party USB Audio 2.0 drivers requires a clock selector for multiple clock sources and must use the same clock source for both playback and capture.Are there any such assumptions and requirements for the USB Audio 2.0 driver that needs to be met?Thanks in advance.
    • Anonymous
      February 21, 2017
      Hi Allen. Thanks for trying the USB Audio 2.0 class driver.Can you file a problem report with "media issues" logs capturing the time when the device is plugged in, and share a direct link?https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/
  • Anonymous
    March 06, 2017
    What kind of recording and playback latency is supported? Will we need to use ASIO drivers?
    • Anonymous
      March 07, 2017
      The latency should be similar to the USB Audio 1.0 class driver. You may be interested in this article describing audio latency improvements in Windows 10:https://msdn.microsoft.com/en-us/windows/hardware/drivers/audio/low-latency-audio
  • Anonymous
    April 08, 2017
    HelloI have installed the RTM version of the creators update and this driver (15063), and when my DAC is connected using this driver, my computer will not turn off the screen or get to sleep when left unused. If I disconnect my dac from the USB port, sleep and screen turn off resume to work normally.Is it a known Issue?
  • Anonymous
    May 21, 2017
    Hi, I plug 'Logidy UMI3' usb midi pedal to my Windows 10 x64. (version 10.0.15063).UMI3 should be recognized as 'Audio device' but it is recognized as 'Other device'. (or Software device in Computer management).I try to 'Driver Update' -> Manually install a driver -> Let me pick from a list, but the list has no 'USB Audio'.I want to change UMI3's category from 'Software device' to 'Audio, video and game controller'.Can I do that?Sincere, Ryan.
    • Anonymous
      May 22, 2017
      Please file a "problem report" as described herehttps://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/Use the "share" widget to grab a direct link to the reportSend me the direct link
      • Anonymous
        June 01, 2017
        I reported 'Feedback hub'.It's the direct share link.https://aka.ms/Mo20rrThanks.
  • Anonymous
    May 23, 2017
    The comment has been removed
    • Anonymous
      May 24, 2017
      Let's start with a problem report:https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/File a problem reportOnce filed, use the "share" widget to grab a direct link to the problem report in questionSend me the linkIn addition to the logs automatically grabbed by the Feedback Hub, it would be useful to have the USB descriptor for your device; send me this when you send me the link. You can grab it using usbview.exe, which comes with the Windows debugger package; I can provide additional detail if you like
      • Anonymous
        May 28, 2017
        Maurits, Here's the link to the feedback hub report. I'm not entirely sure if the capture happened; I added one for Media and USB; but as far as 'replicating the problem' the best I could do is uninstall the device and let Windows install it (as a USB Audio Class 2.0 device) once again.https://aka.ms/FwajbiNote that the behavior is the same across 5 test systems running Creators Update; so it certainly isn't a problem with this dev machine.I am seeing some troubles in the USBView capture, but am not sure which one would cause a Code 10. I'm not sure how to go ahead and send you a copy of that capture; since I don't have your email or any other way to contact besides this blog (I think). So I hope a pastebin link will do:https://pastebin.com/hwv2GYbAI also attached as many screenshots deep into device manager that I could on the feedback hub report.... I hope this is enough to at least provide a lead we can give our firmware guys...
      • Anonymous
        May 30, 2017
        Maurits,I replied with the links requested -- but my comment is still awaiting moderation... What would be the best way to get the USBview logs to you? (I've also filed the Feedback Hub report, but I think posting the link to that here is also what's causing my reply to go into moderation..)
        • Anonymous
          June 06, 2017
          Hi MichiLumin:I also get the problem as you describe.I can't assess your feedback hub.Have you solve the problem or MS give the feedback?
      • Anonymous
        June 11, 2017
        Hi Maurits,I also get the problem as described.Here’s the link to the feedback hub report.https://aka.ms/bd3621 Have you solve the problem or give the feedback?
  • Anonymous
    June 04, 2017
    Hi Maurits, I want to know if the Windows IOT core system does have the UAC 2.0 driver ?
    • Anonymous
      June 05, 2017
      Yes, the IOT SKU has both the USB Audio 1.0 and USB Audio 2.0 class drivers.
  • Anonymous
    June 06, 2017
    Hi Maurits,Is there any way to extract usbaudio2 driver from Win 10 and install it to WS2016? I was able to locate usbaudio2.inf and usbaudio2.sys on Win 10, but cannot install it to WS2016 without digital signature *.cat file)
  • Anonymous
    June 12, 2017
    This has just recently happened. And i don't know why since it was working perfectly fine before. I'm using an old PS3 Headset as my... well... headset for gaming. And it's not getting recognized as an audio output / input. The driver is having problems starting. (Specifically, USB Audio Device, Code 10). I've reinstalled it, disabled and re-enabled it, restarted my computer, i even installed it manually but it just says it cannot because it can't start.
    • Anonymous
      June 12, 2017
      So I've left it unplugged for a bit and now it's decided to work. I'm not sure if it will happen again so I've chosen to stay active on this blog. If it fails again or anything else happens, i'll post here.
  • Anonymous
    July 16, 2017
    Hi all,I have a Micca Origen, which is a USB audio class 2 DAC that comes with its own software for Windows. The software has not been updated since Vista, and although it functions, it often causes a BSOD, especially in ASIO mode.The devices uses a controller chip from the company VIA Technologies. The device shows up as a "USB\Class_ff&SubClass_00&Prot_20" for the "compatible id" in Device manager. Currently, any attempt to use any other driver causes Code 10, and I have build 15063 and have tried the current Class 2 drivers. Is there any hope we can have support for my DAC?I have posted this on the Feedback Hub under my account, but I am not sure if this is the same as a "problem report" that is being mentioned.
    • Anonymous
      July 17, 2017
      Can you use the "Share" widget to grab a direct link to the thing you submitted in Feedback Hub, and then send me the link?USB devices which are compliant with the USB Audio class specification have PnP IDs that start with USB\Class_01. Class_ff means "vendor specific" so it is likely that only the manufacturer's driver has a chance of ever working.
      • Anonymous
        August 04, 2017
        Hi Maurits, sorry for the delay I didn't realize you replied...Heres my feedback link https://aka.ms/Qnh1jiI know you just said that it will likely never work, but this DAC, like many others here, are plug-in ready for Linux and Mac...Also, if it might help, I can send BSOD information to someone so that maybe windows can get an update that prevents BSODs from occurring in mine and other similar cases. If that helps who can I send data to?Thanks
        • Anonymous
          August 07, 2017
          Upload C:\Windows\memory.dmp after a bluescreen and I can take a look.
  • Anonymous
    July 23, 2017
    Hi guys, desperately need your help! I'm trying to get my xcitel md-port dg2 usb to optic audio converter to work on my win 10 pro 64 bit and no success.. When I follow the instrucrions above, I have only "USB Audio Device" in the list and it is already the driver Windows using for this device. In Device Manager I see it with a yellow traingle and a "This device cannot start. (Code 10)" error status.I'm running a Version 10.0.15063 Build 15063 Windows and don't know what to do. This device previously ran on a home version of Windows 10 that I had on an another computer that I don't have an access to and I don't remember if there were an issue with it's installation there..Please help!
  • Anonymous
    August 29, 2017
    good