Ahh, I’m reminded of what really makes me hate NT: hardware support.

Ever since my good cable got a tad bent at the connector, I’ve only had two cables that really like to drive my Xbox One controller. One that’s like 3 meters, and one that’s like 30 centimetres: neither of which is particularly fun with my desk. But at least they work, if you deal with the cable lengths.

So, I figure let’s try the wireless adapter for Windows. Well, guess what? It’s shit.

The “Slim” model 1790 now available doesn’t work with Windows 10, 1903, up to date as of what Microsoft lets my desktop get. As far as the base operating system is concerned there is no driver for this device–none, nadda, zilcho!

If you browse the go fetchy it catalog referenced in places like this and this, and get a bit creative in pointing Windows at various entries and fine one that’ll actually match the device: the most you’ll get is an error code: “The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)”. If you give up more easily than I do when I’m tired and almost ready for sleep: you’ll just get a message saying it didn’t find squat that works with the driver you extracted.

Because why would you expect Microsoft’s driver’s to work with Microsoft’s hardware? That’s a lot to ask, I guess.

In my experience there are really only three kinds of drivers for Windows.

  1. Those that just work, and often those come with the Microsoft’s install.
  2. Those that almost never work; and
  3. Those that are about as stable as drunk with ten shots of rum in’em.

On the flipside scenario 3 is why error codes like 48 exist. Not being able to use a piece of hardware is frequently better than it turning the rest of your experience to crap.

For the extra curious nerd, the device reports itself as usb vid 045e pid 02fe in the device manager’s GUI. 0x45e being MS’s USB vendor id. Dunno what their product ids in the wild are, and I’m not buying multiple adapters to find out.

The Microsoft Xbox One Wireless Adapter for Windows kit also comes with a really nice but rather short length USB extension cable. Which aside from being an overpriced cable when you consider the wireless adapter is actually a paperweight until MS fixes the driver, does in fact solve my real problem. I.e. if I was smart I would’ve just bought a decent cable in a length > 0.3 & < 3.0 meters long instead of MS’s wireless adapter. Ha! 🤣

Thus my real solution is to take the extension cable that came with the useless wireless adapter, plug in my too damned short cable I wanted to replace, hook up my controller and go play a damned game before my head droops and hits the desk.