- Jan 16, 2005
- 2,635
- 106
- 106
Note: this might belong in Operating Systems, but as the impact is to PC gamers, I'm putting it here.
Like many PC gamers, I play some games using a wireless Xbox 360 controller. To do that, I had to purchase a wireless receiver which I did many years ago through Amazon. It's worked great.
Until recently.
Several weeks ago MSFT released a Windows 10 patch (2004) that quietly made any non-MSFT wireless receiver inoperable. Apparently MSFT only wants to support their own branded hardware. Personally, I find this disappointing.
I suspect LOTS of PC gamers did what I did: ordered a controller and wireless receiver from Amazon. Most of the sellers on Amazon are selling Chinese-made hardware that's identical to MSFT branded stuff...but a few dollars cheaper.
Fortunately some people have figured out a workaround. After about an hour of installing/disabling/reinstalling drivers, I stumbled on this video which provides a relatively easy solution. Basically, you have to edit the MSFT driver to change the hardware id to match the hardware you have, then trick Windows into installing the driver that's now been tampered with.
Like many PC gamers, I play some games using a wireless Xbox 360 controller. To do that, I had to purchase a wireless receiver which I did many years ago through Amazon. It's worked great.
Until recently.
Several weeks ago MSFT released a Windows 10 patch (2004) that quietly made any non-MSFT wireless receiver inoperable. Apparently MSFT only wants to support their own branded hardware. Personally, I find this disappointing.
I suspect LOTS of PC gamers did what I did: ordered a controller and wireless receiver from Amazon. Most of the sellers on Amazon are selling Chinese-made hardware that's identical to MSFT branded stuff...but a few dollars cheaper.
Fortunately some people have figured out a workaround. After about an hour of installing/disabling/reinstalling drivers, I stumbled on this video which provides a relatively easy solution. Basically, you have to edit the MSFT driver to change the hardware id to match the hardware you have, then trick Windows into installing the driver that's now been tampered with.