Last week, I wrote a piece about console vs. PC gaming in which I came down, very gently, on the side of PCs. While they can be expensive to build, I argued that their huge game libraries and broad range of nongaming applications make up for any shortcomings.
Well, almost any shortcomings.
In my article, I pointed out that my biggest gripe with PC gaming was having to act as your own tech support. This is partially true if you bought your PC from a big manufacturer like Asus or Alienware; it’s especially true if you built a machine from scratch. A recent experience reminded me of just how hair-pullingly frustrating it can be to effect the simplest PC gaming repairs — and how the rewards are still (mostly) worth it.
Credit: Microsoft
Contents
Control(ler) freak
Connecting a controller to a console is simplicity itself. Just turn on the console, turn on the controller, and they’re linked, right out of the box. If there’s a problem, you can often just press a button to sync them, or attach them directly with a USB cable to reinstate the connection.
Would that it were so easy on a PC. I’ve been playing a lot of The Witcher 3: The Wild Hunt (side note: Play The Witcher 3, if you haven’t already; it’s probably the best PC RPG since Baldur’s Gate). But the wire on my old Xbox 360 controller kept wrapping around my arms and thighs. Newer Xbox One controllers can connect to PCs via either Bluetooth or a specialized adapter. I built my PC before Bluetooth was a thing, so the adapter it was.
(You can also simply connect Xbox One controllers with a USB cable, but if I did that, I’d be right back to square one with a wired controller.)
If you’ve never used the Xbox One Wireless Adapter on a PC, let me tell you: It’s a thing of beauty. I’d used it at work many times, and installing it could not be simpler. You just plug it into an open USB port, let Windows automatically install the drivers, then press a button to sync your Xbox controller. I assumed I would take it out of the box and be playing The Witcher 3 within 5 minutes.
Four days later, I took my first tentative steps back into Geralt of Rivia’s bloodstained boots.
One of the simplest PC gaming accessories wound up causing a catastrophic cascade failure, and the fix was something I never would have imagined — nor would a tech support representative, if I even had access to such a person.
Credit: Amazon
The problem
I popped the wireless adapter out of the box and into the first open USB drive in my computer. The sync light didn’t light up, which I thought was unusual, because it’s supposed to take only about 30 seconds for installation to complete.
Like all great computer users who came before me, I figured the most expeditious solution would be to unplug the gizmo, restart the computer and plug it in again. I did so, to no effect. Clearly, this was going to take longer than I thought.
I decided it was time to roll up my sleeves and deal with the drivers directly. After opening Device Manager, I was sure I’d identified the problem. My computer recognized the adapter, but there was an ugly yellow sign with an exclamation point inside of it. The driver had failed to install correctly.
I’d already spent about 10 more minutes than I’d wanted to spend installing the adapter, but at least my odyssey was nearly at an end. I uninstalled the driver completely, unplugged the adapter, restarted my computer and plugged it back in. The sync light did not illuminate. The dreaded yellow exclamation sign appeared once again.
From here, I decided that Reddit, Tom’s Hardware, NeoGAF or a similar site would hold the answer. However, after scouring the web for hours, I was no closer to finding an answer. While other people had problems connecting Xbox controllers wirelessly, those people tended to have very prosaic solutions (update the firmware), the wrong operating system (the adapter is optimized for Windows 10, which I have) or completely different issues with similar search terms (Xbox 360 controllers or Bluetooth connections).
A handful of people seemed to have my exact problem. No one had ever replied to their threads.
Credit: Kiselev Andrey Valerevich/ShutterstockThe tech-support conundrum
At this point, I certainly could have contacted Microsoft and explained the problem to people there. A quick glance at the Microsoft forums convinced me that this would not be a good idea. Other people had attempted this procedure and gotten what is known in technical terms as “the runaround.” Additionally, Microsoft’s tech supporttends to be lackluster even at the best of times.
Microsoft told callers that they’d have to contact the Xbox division, because the adapter was technically an Xbox product. That division informed callers that they’d have to call general Microsoft support, because the adapter is a PC accessory. The absolute best-case scenario was that Microsoft would offer to replace the adapter, assuming it was a defective device — and yet I knew this wasn’t the case, after borrowing two other adapters from work and getting the same results.
There comes a certain point in every PC gamer’s life when he or she just knows, in his or her bones, that the problem has exceeded the capabilities of the average customer-support technician. Like the beleaguered hero at the end of a ’90s action film, I knew this was something I would have to handle alone.
Luckily, Windows users always have access to the nuclear option: wiping the hard drive and reinstalling everything from scratch. I assumed that some other driver or piece of software I’d installed somewhere along the way must be interfering with the adapter installation. After backing up my files, I arranged to work from home for a day in order to wipe my OS and install a squeaky-clean version. With no drivers or software to get in the way, the adapter was sure to work.
The adapter did not work.
Hours later, after Windows 10 was up and running once again, I plugged in the adapter. A fully patched version of Windows 10 with absolutely no extraneous software tried to install the driver — and failed.
[Source”GSmerena”]