Oh yeah, I totally agree Nick - this guide is for a specific issue with a specific device and you provide the best solution for that issue. I think the note you added to Step 1 is perfect and should tell anyone who comes here with the same problem as me everything they need to know.
Ultimately, apart from releasing a device that commonly fails to interact correctly with their own ecosystem (and then updating the hardware without solving a problem from 2015), Microsoft screwed up by not meaningfully differentiating between the original version of the adapter and the slim update.
So we have 2 devices with different model numbers (1713 vs 1790)… but the same name, same MS support page, same issue - and different solutions.
Which is a problem for people just searching “xbox wireless adapter “xbox acc””! But hopefully they come here first instead of going to all the Reddit & Steam posts that don’t include your note.
No problem, Zoe.
I actually replaced mine once before I ended up here (but not until after I’d wasted half of videogame night trying to get the first one to work because I’d assumed an MS device would work just fine on an MS operating system - so glad one of the girls brought her Xbox just in case). When the second one had the exact same issues I decided it was time to start actively posting about it and I ended up here… my success is the result of downloading every Xbox-related driver on the Update Catalog and force-installing them one by one in total desperation.
Just really glad it’s already helped someone!
Yeah, that makes sense.
I also just realised that your guide is for the original Wireless Adapter - whereas I’ve got the new (smaller) one. Maybe add a note that owners of the newer adapter will also need the newer driver?
None of the other guides I’ve seen out there include this info either, and yours is still the easiest to follow… so you’re still winning :)
Thanks, but that wasn’t my issue.
I figured out that you can use the “Have disk…” option in the driver update dialog to force the install, but that still didn’t fix it - Device Manager correctly identified the device as “Xbox Wireless Adapter”, but it showed error code 10 and still failed to work.
What actually fixed it was a NEWER, entirely different (and deceptively named) driver in the Update Catalog.
For 64-bit systems:
Title: Xbox - Net - 7/11/2017 12:00:00 AM - 126.96.36.199
Products: Windows 10 Anniversary Update and Later Servicing Drivers,Windows 10 S and Later Servicing Drivers
Classification: Drivers (Networking)
Last Updated: 7/11/2017
Size: 217 KB
For x86 systems:
Size: 194 KB
I really hope this helps anyone else out there with the same issues as me.
This is a great guide. It seems to be a common issue and many people have offered similar solutions, but this one is the clearest and most well-explained.
However, it didn’t work for me - and from comments I’ve seen around, I know I’m not the only one. I wonder if you have any thoughts on this?
At the end of Step 3 (“Click Next and install the driver”), the window flashes to something like “Searching location…” for less than a second and then I get:
Windows was unable to install your XBOX ACC
Windows could not find drivers for your device.
If you know the manufacturer of your device, you can visit their website and check the support section for downloadable drivers.
I’m using Win 10 64-bit, fully updated.
I’ve tried the other drivers on the Update Catalog with the same result.
Is it possible to manually force the drivers to be installed?
Quando isso acontecer, você poderá ver um gráfico da reputação que ele adquiriu ao longo do tempo.
Aqui está uma prévia de como será o gráfico: