I would start by trying to roll back the driver. I had several devices that didn't want to work after the latest update, including Windows Hello on my Surface Pro 4. Driver rollback seemed to do the trick, easier than aa reinstall. Open Device Manager. Right-click the device for which you want to roll back to the previous version of the driver, and then click Properties. Click the Drivers tab. Click Roll Back Driver. In the Driver Package rollback dialog box, click Yes.
Last Edit: Aug 9, 2017 18:20:48 GMT -5 by mattfaske
I would wait for the almighty Keith to weigh in. Let's see if we can summon him. Keith, oh Keith...are you there...? KeithL what have you to say sir?
XMC-1 DIRAC Full; Oppo 105/Roku Ultra to Panny AE4000 w/106" screen; UltraRendu to LH Labs Geek Pulse X-Infinity; nCore nc400's or Prima Luna Premium Prologue to Maggie 1.7's; Rythmik F25; XPA-5 to CC-470v3 Center/ERD-1's; Thorens TD166 MkII/Denon DL207/XPS-1; 5-zone Sonos w/Def Tech AW5500's @ deck/pool/master bath & Sony SS-MB105/Polk R10 @ great room & kitchen. Two headphone setups: Hifiberry/BasX A100 and Allo BOSS/Schiit Asgard 2 (each to Senn 600's). PC w/Airmotiv 3b's. Roon user.
First off, you have to be careful when you talk about "the latest updates" because different computers are not always going to get the same updates. For example, they started offering the Creator's Edition update to some people several months ago.... But, according to Microsoft, there were lots of compatibility issues (it wouldn't run with certain hardware - including some network cards very popular in laptops). For that reason the Creator's Update was "only being offered to computers they were reasonably sure it would work on". (If you weren't offered the update, you could still get it manually, but Microsoft advised "that only tech savvy users who were willing to deal with possible issues" should do so.) This means that some people have had the Creator's Edition for months, while others still haven't got it.
In fact, there's also something further going on with distribution - probably because they're simply trying to roll it out gradually. I set up a new computer about a month ago, and did "all the latest updates", but was NOT offered the update to the Creator's Edition. Then, a few days later, the Creator's Edition was offered. (Either it had become compatible with that machine due to the latest update, or they just have a bit of delay with figuring out which machines it will work on.)
The bottom line, however, is that you won't know exactly which version you have unless you look (or remember doing the update)..... And there are probably very different updates being offered to machines with the CE and those without... (And internal UAC2 support is ONLY included on the Creator's Edition; as far as I know it is NOT included, even in the latest update, if you DON'T have the Creator's Edition.)
In any case, my test machine here is relatively new, and has the Creator's Edition on it. When I updated to that version, I DELETED the original Emotiva C-Media drivers, and all of our USB stuff worked just fine with the internal Windows drivers (including the Ego DACs, the DC-1, the PT-100, and the USB input on the XMC-1).
I just fired it up this morning, and installed the latest Windows 10 updates (according to Microsoft), and it STILL works just fine with my Ego DAC. Therefore, assuming you have the Creator's Edition, I would suggest, if anything, REMOVING the drivers using Device Manager. Then, when you unplug, and then reconnect the DAC, your computer SHOULD reload the Windows internal drivers and it SHOULD work.
Just for the record, it can be a little difficult to tell which version of Windows you actually have on your computer. You can find out by typing WINDOWS VERSION into the little search box, then picking "See if you have a 32 bit or 64 bit version of Windows" from the list. (Sometimes you get a slightly different System Information screen offered.)
On 64 bit computers Windows 10 Creator's Edition Pro, it shows up as: Version 1703 Build 15063-xxx
If you don't see those numbers, then you don't have the Creator's Edition. (There's a really nice page in WikiPedia that lists all the OTHER versions and builds you might have... )
Incidentally, when I look at the Driver Properties for the Ego driver in Device Manager what I get is: "No driver files are required or have been loaded for this device". So it really is running on the internal UAC drivers.
Note that, as usual with Windows, the details on your computer may vary.