Wie man den XBox One Wireless Receiver (1713, Windows 10/11) installiert

You can actually download the driver manually to force the installation. To force the installation, you will need this driver for Win10: Microsoft driver update for Xbox Wireless Adapter for Windows (18.31.1.43)

If the issue is installation, you need to unzip the folder and put the files in a normal folder. The .cab folder from the download site doesn’t work as-is. I should have clarified this, but it’s corrected.

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 - 1.0.46.1

Products: Windows 10 Anniversary Update and Later Servicing Drivers,Windows 10 S and Later Servicing Drivers

Classification: Drivers (Networking)

Last Updated: 7/11/2017

Version: 1.0.46.1

Size: 217 KB

—

For x86 systems:

Title: Xbox - Net - 7/11/2017 12:00:00 AM - 1.0.46.1

Products: Windows 10 Anniversary Update and Later Servicing Drivers,Windows 10 S and Later Servicing Drivers

Classification: Drivers (Networking)

Last Updated: 7/11/2017

Version: 1.0.46.1

Size: 194 KB

—

I really hope this helps anyone else out there with the same issues as me.

Eryn

I did it on a W10 Build 1708 system with deferred updates and the throttled internet connection option enabled. I think 1708 is the Anniversary update, so there’s a chance that system had an older build at the time.

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 :)

I added it to step 1 as a note and made it bold. Hopefully that works to make this issue more prominent.

I’m sure I could modify the driver and use the new one by adding the VID to the old W7/8.x driver but I’d rather just have the one that works. I still use W7, which is why. If I had a Windows 10 system, I might be willing to try that and see.

I didn’t add the driver information for the one you have because I made this guide for the old one and labeled the device page accordingly. This wasn’t an oversight but an issue that came up later on.

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.

The only thing the adapter you own does is remove W7/8.x compatibility by changing the VID. I think it’s existence is stupid, but they still released it. Changing the VID isn’t sufficient to fix the issue - they should have changed the device name and VID to make it easier to differentiate.

The fat one isn’t as pretty (and needs an extension on most laptops) but I’d rather maintain native 7/8.x compatibility.

Thanx! My hero !!!

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!

Eryn

Strange - that driver worked for @erynmillennial. I had to take her word for it when I added that note to the guide and I trust she’s right since she got it working with that driver. I don’t have the new receiver like her (partially because I STILL use Win7 and 8.x and don’t own ANY Win10 hardware) so I can’t go in and figure out which driver works.

Code 48 means the driver has known compatibility issues. Are you using the new driver on the “fat” adapter? That’s the wrong driver for that receiver and ONLY applies to the small one she mentioned. You need to use the one I mentioned in Step 3. I may have to end up making a guide just for that receiver if this happens again.

For everyone else, I’ve updated my warning to clarify this.

I also had this problem, but I noticed that there are actually 4 variants of the 1.0.46.1 driver. I had to pick the third one, so maybe try out the other variants, it may depend on your windows version. All in all I find it outrageous that a microsoft product needs this much effort to work.