Click to view our Accessibility Statement or contact us with accessibility-related questions
Limbo
41
Jun 28, 2017
Just so everyone is aware. As of right now this will NOT play on Windows 10 Creators Edition 1703. The drivers are not signed and new features in Windows 10 version 1703 will not allow it to load the drivers. It will allow you to install them but Windows will immediately block them from loading once it is installed. I've reached out to XDuoo support a couple times now over the past week and they are not getting back to me. Right now the only work around is to disable driver signature enforcement which I do not recommend.
Limbo
41
Jul 7, 2017
LimboUpdate: I've tried multiple times to contact their support about signed driver updates with no luck. At this point I have no option but to determine xDuoo support is horrible. The worst part is they use http://www.thesycon.de/eng/usb_audiodriver.shtml driver version 3.34 and the current version is 4.11 which officially supports Windows 10 signed drivers BUT consumers can't buy it, the license is only for hardware and software manufactures. I can only determine XDuoo is too cheap to update their license agreement with Thesycon. Why else would they be so far behind?
Aside from not putting out updated / supported drivers they do say " Supported OS: Windows 7, 8, Vista, XP; Mac OS X: iOS; Android with OTG " which has no mention of Windows 10. If you read the specs and do a little research you'll realize the best possible output with real HD files (24 bit and 192000 Hz and above) is to use USB so lets hope xDuoo gets with the times.
On a side note I did initially have an issue with the USB port having a short but Massdrop support took care of me for that without issue. It did take a month to get the replacement though but massdrop support was great.
SantiagoDraco
611
Jul 7, 2017
LimboThis is a pretty serious problem. The device is supposed to support Windows and it should NOT require that you reduce the security of your system in order to do so. Massdrop needs to step up and get with xDuoo and find out what the problem is here. This needs resolved asap. I have an amp on order and I am very concerned about receiving an unusable unit. I do not want to turn off driving signing. Frankly I won't. If we can't get a straight answer I'll be asking for a refund and looking to pickup an Oppo or another alternative.
Massdrop have you been in touch with xDuoo on this issue? Thanks.
rclose
10
Jul 15, 2017
SantiagoDracoSo, maybe I am doing something wrong, but I had little issue getting the driver installed and running on Windows 10 (1703) without turning off driver signing enforcement.
The initial package (XMOS-USB-Drive-V3.0.0.exe) is absolutely broken, but it's just a self-extracting archive. I opened it in 7-zip and removed the driver itself (XMOS_EVAL_KITS_DriverSetup_v3.34.0.exe, as described in the accompanying documentation) and it installed fine, without error, and without having to disable signed driver enforcement. I'm listening to music right now through foobar2000 and the xDuoo X-5 on Windows 10 1703. This was from the package on the accompanying cd.
Can you guys give that approach a try and see if it works for you?
SantiagoDraco
611
Jul 16, 2017
rcloseI'll give that a try when I receive my unit and when I'm back in town. Hoping it will work.
bsoplinger
79
Jul 18, 2017
SantiagoDracoDid it work for you?
Limbo
41
Jul 18, 2017
bsoplingerThose are the same exact steps I've gone through on 3 different machines and none worked for me. 2 machines were upgrades and the third was a fresh install. It will install the driver but as soon as it goes to load them I get a popup saying Windows blocked a driver that wasn't signed.
F.Y.I. Still no word from their support. I've sent multiple emails to them and haven't received a response.
rclose
10
Jul 18, 2017
Limbo@bsoplinger , that's interesting. I wonder if they updated the package between product releases? I just received mine last Saturday (July 15) and that process worked first try, no issues. The driver has a signature when inspected through the device manager. This is on a Windows 10 non-upgrade machine (started as Windows 10, not Windows 7 or 8) and upgraded through the normal mechanisms to 1703.
<shrug>
I have no idea why it would work for me and not for others, but I'd be happy to provide any additional details if you can tell me what you want to see.
I'll also, just to duplicate my test, install it on my wife's machine. Will do that tonight after work and post back. I'm interested to figure out why it didn't complain on my main machine.
rclose
10
Jul 19, 2017
LimboHmm, well, no ideas.
I verified that my machine (Windows 10 64-bit Home, 1703) has driver signature enforcement on (via registry). I uninstalled and reinstalled the driver, no complaints.
I did the same exercise on my wife's machine (Windows 10 32-bit Pro) which also has driver signature enforcement turned on (verified via registry). Hers was a Windows 7 machine upgraded to Windows 10. Same thing, installed, never complained about signature. Both machines, when looking at the driver in the device manager, show what appear to be valid signatures from "Thesycon Software Solutions" blah blah blah.
So, maybe my machines are both broken and the registry is being ignored for signature enforcement? <shrug>
Let me know if I can be of any help. Sucks so many people are having problems.
bsoplinger
79
Jul 19, 2017
rcloseI really appreciate you taking the time to check this out on 2 machines. I did my standard installation of a new device work flow which starts with ignoring the included drivers and going to the manufacturer's web site for them. Since it so often happens that a newer version is available seems easier to start there. This was the first time that I couldn't get any drivers online and had to rely on the installation CD. Luckily I have a workhorse Dell Latitude E6430 with a DVD drive. Any newer machines I own don't have media drives although I do have an old external from my old netbook. They seemingly installed fine once I copied them via flash drive to my current laptop but immediately got the unsigned warning once I connected the XD-05.
Guess I can try removing them from the machine completely by using the Windows way point feature. What is it called, the feature where Windows saves the current system files before an install. Then perhaps try installing differently. Plug in the XD-05 and when Windows prompts about needing a driver and using the I have the files option. It'd be doing the same thing as just installing first but perhaps the slightly different methodology might make a difference. I'll report back as soon as I try. It may be a few days, I'm not the healthiest person right now.
rclose
10
Jul 19, 2017
bsoplingerAlso, check this post : https://www.massdrop.com/buy/xduoo-xd-05-dac-amp/talk/1755367
He found another driver package on the Japanese xduoo site that worked for him - might help you out.
bsoplinger
79
Jul 19, 2017
rcloseWell don't know if the change to the Japanese xduoo site file or just going back to the previous way point (what is that darn Windows feature called?) and installing again was the magic, but it finally worked. Forced 24 bit 192k and I'm listening fine without Windows complaining. Life is good. Thanks
Limbo
41
Jul 20, 2017
rcloseHow old is your PC? Does it have a Secure Boot mode in BIOS and if so is it enabled or disabled? The main reason I'm asking is after extensive research I found since my machines are relatively new (less than a year) there is a BIOS setting for Secure Boot mode which prevents unauthorized OS's from running at boot time. If you disable that Windows will load the xd-05 drivers and run fine. Not sure if I'm comfortable with doing that but.
To test it I found an older laptop that didn't have that feature in the BIOS and had Windows 10 (1703) installed (luckily I have access to a lot of laptops at work). I installed the xDuoo XD-05 drivers and it worked fine. Somehow that setting is stepping on the XD-05 drivers.
rclose
10
Jul 20, 2017
LimboMy machine is just over a year old, so I am assuming it both has that feature and that it is enabled.
I'm not at the house right now, but will be later tonight. I'd be more than happy to check my BIOS just for the data point and report back. I'd really like to know definitively why some people have no problems while others are plagued.
rclose
10
Jul 21, 2017
LimboThat must be the issue.
So, I confirmed my machine has Secure Boot disabled (via powershell). I had no idea, and was kinda pissed. But, when researching how to even enable it on my machine (because there isn't an option in my BIOS that actually says "Secure Boot"), it looks like my particular mainboard has a problem with that feature. So, maybe I am just lucky all around that it was left off by the OEM.
If it were something easy to turn on and test, I would do it, but I fear corrupting my bios (as others report).
Limbo
41
Jul 21, 2017
rcloseI'd also be worried about corrupting the OS. I'd leave that one be.
bsoplinger
79
Jul 21, 2017
LimboInteresting. I've installed on my MacBook Pro (current model) which of course has a slightly different BIOS setup than a typical PC but I was under the impression that its status was secure only without a way to disable (because its a Mac not a PC). So just to see tried installing on my Dell Latitude E6430 which is my 'work' laptop. Figured I couldn't really mess up the machine with USB DAC drivers. Its BIOS is set to secure and I'd never mess with that on a machine for serious use. Same as above. The drivers from the little CD that came with the unit trigger the unsigned warning but dropping back to the last restore point explicitly created just before the driver install and redoing it with the Xduoo Japanese site files worked fine. Perhaps Xduoo has updated their software but just ships the 'international' version with whatever disc they have, being too cheap to pay to produce a new CD? I did poke around on the Chinese language version of the site and noticed that they do have a driver file download that isn't there in the same download area if you've chosen the English language version of the site. Since I had working drivers from this thread (well the other thread but info from here) I haven't bothered to try to download and use them.
Limbo
41
Jul 21, 2017
bsoplingerThe other thing is the driver is a third party driver from Thesycon . The version xDuoo is sending out is version 3.34 and is over a year old. 3.34 also doesn't officially support Windows 10. The latest version is 4.11 which does support Windows 10. I'm guess xDuoo is too cheap to pay for the upgrade and license agreement or if they have an active support agreement then to lazy to have the new driver package created. Thesycon's site says the following http://www.thesycon.de/eng/usb_audiodriver.shtml
  • Windows 10 version of the driver is signed with Microsoft Attestation signing.
  • Windows 7/8 version of the driver is signed with Thesycon’s code signing certificate.

SantiagoDraco
611
Jul 22, 2017
LimboSo the big question is how do we get the new driver.
I have to say I'm very concerned and disappointed in Massdrop's silence on this. They are usually responsive and work to assure they are delivering a quality product but in this case... not so much.
Limbo
41
Jul 22, 2017
SantiagoDracoThe main problem is xDuoo. They are the only ones who can get and distribute the new driver. Thesycon will only sell to software and hardware vendors.
bsoplinger
79
Jul 22, 2017
SantiagoDracoAfter all, in this case, Massdrop is delivering exactly what you'd get if you purchased the Xduoo anywhere else including directly from the Chinese website.
Its as Limbo says. Xduoo is completely responsible whether the driver gets updated for Windows 10 or not. I'll argue that Windows 10 has been out long enough now that any product that wants to claim its "Windows" compatible must be compatible with Windows 10 and saying in either small or large print only up to Windows 8 just doesn't work.
PRODUCTS YOU MAY LIKE
Trending Posts in Audiophile