Sign-in / Sign-up
Your question

Xbox 360 Wireless Controller PC Adapter "Code 10"

Last response: in Computer Peripherals
June 14, 2013 3:00:23 PM

Hi y'all, first post here, so sorry if it's the wrong section or something.

I'm running Windows 8 Pro 32bit.

I recently got a wireless adapter to use the Xbox 360 controller with a pc. It's not an official Microsoft one, but a convincing replica and reviewers said it worked after a manual driver installation. I plugged it in, installed the drivers manually (Xbox 360 Wireless Receiver for Windows Version 2.1.0.1349). I had to try two different usb ports but it worked. I paired the controller to the receiver and it worked perfectly...for a few days. One day, after a restart perhaps, the controller wasn't working and Windows said the receiver isn't running properly.
- I replaced controller batteries, still nothing.
- I tried reinstalling the driver and it started giving me "Code 10 'device cannot start'".
- I tried removing the device and reinstalling the driver from a clean slate. Still code 10.
- I tried every other usb port I had, still code 10.
- I tried re-pairing the controller to the receiver at various points during the above steps, but the controller would not pair.
- I tried messing with the xusb21.inf file after seeing it suggested in another forum. I can find more details about it if needed, but it didn't work anyways and I'm back to the stock xusb21.inf file. There are a few threads concerning this wireless adapter, but no definite solutions, and no threads involve Windows 8.
- I grabbed some newer drivers for the receiver off the Microsoft website and tried those. Still code 10.

This code 10 isn't really giving me any information to go on. What really gets to me is that the damn thing worked for about a week, and suddenly, irreparably, stopped. Any thoughts?

More about : xbox 360 wireless controller adapter code

June 16, 2013 3:38:25 AM

Right click on Computer
Go to Properties
Click on Device Manager
Right click on the Unidentified Device
Go to Properties
Go to the Drive tab
Click on Update Driver…
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Windows Common Controller for Window Class
Xbox 360 Wireless Receiver for Windows Version: 2.1.0.1349 [8/13/2009]
Update Driver Warning
Click Yes
m
0
l
June 16, 2013 7:29:07 AM

Thanks but I tried that. That's exactly how I got it to work in the first place. Now i can't install those drivers because of that pesky code 10.
m
0
l
Related resources
November 28, 2013 3:39:20 PM

I also followed the steps and ran into a Code 10. In my case, it happened to be that the controller and a USB dongle was plugged into the front of the computer. I suppose those ports cannot support the demand. I plugged the controller to the back USB slots and it recognized, no issue.

Hope this works for anyone still looking for an answer.
m
0
l
December 30, 2013 7:24:43 AM

WBizarre said:
Hi y'all, first post here, so sorry if it's the wrong section or something.

I'm running Windows 8 Pro 32bit.

I recently got a wireless adapter to use the Xbox 360 controller with a pc. It's not an official Microsoft one, but a convincing replica and reviewers said it worked after a manual driver installation. I plugged it in, installed the drivers manually (Xbox 360 Wireless Receiver for Windows Version 2.1.0.1349). I had to try two different usb ports but it worked. I paired the controller to the receiver and it worked perfectly...for a few days. One day, after a restart perhaps, the controller wasn't working and Windows said the receiver isn't running properly.
- I replaced controller batteries, still nothing.
- I tried reinstalling the driver and it started giving me "Code 10 'device cannot start'".
- I tried removing the device and reinstalling the driver from a clean slate. Still code 10.
- I tried every other usb port I had, still code 10.
- I tried re-pairing the controller to the receiver at various points during the above steps, but the controller would not pair.
- I tried messing with the xusb21.inf file after seeing it suggested in another forum. I can find more details about it if needed, but it didn't work anyways and I'm back to the stock xusb21.inf file. There are a few threads concerning this wireless adapter, but no definite solutions, and no threads involve Windows 8.
- I grabbed some newer drivers for the receiver off the Microsoft website and tried those. Still code 10.

This code 10 isn't really giving me any information to go on. What really gets to me is that the damn thing worked for about a week, and suddenly, irreparably, stopped. Any thoughts?


Finally, someone who got a similar problem to mine. It's unbelievable how many people just post the "Right click on Computer
Go to Properties [...] Update Driver Warning.Click Yes" solution, without realizing that's not the answer for code10.

So my question to you is if you've already found a solution or if you've given up in the attempt.

Thanks in advance
m
0
l
June 6, 2014 3:22:41 AM

WBizarre said:
Hi y'all, first post here, so sorry if it's the wrong section or something.

I'm running Windows 8 Pro 32bit.

I recently got a wireless adapter to use the Xbox 360 controller with a pc. It's not an official Microsoft one, but a convincing replica and reviewers said it worked after a manual driver installation. I plugged it in, installed the drivers manually (Xbox 360 Wireless Receiver for Windows Version 2.1.0.1349). I had to try two different usb ports but it worked. I paired the controller to the receiver and it worked perfectly...for a few days. One day, after a restart perhaps, the controller wasn't working and Windows said the receiver isn't running properly.
- I replaced controller batteries, still nothing.
- I tried reinstalling the driver and it started giving me "Code 10 'device cannot start'".
- I tried removing the device and reinstalling the driver from a clean slate. Still code 10.
- I tried every other usb port I had, still code 10.
- I tried re-pairing the controller to the receiver at various points during the above steps, but the controller would not pair.
- I tried messing with the xusb21.inf file after seeing it suggested in another forum. I can find more details about it if needed, but it didn't work anyways and I'm back to the stock xusb21.inf file. There are a few threads concerning this wireless adapter, but no definite solutions, and no threads involve Windows 8.
- I grabbed some newer drivers for the receiver off the Microsoft website and tried those. Still code 10.

This code 10 isn't really giving me any information to go on. What really gets to me is that the damn thing worked for about a week, and suddenly, irreparably, stopped. Any thoughts?



I HAVE WIN 7 64 BIT, I HAD SO MUCH SHIT WITH THE WIRELESS 360 CONTROLLER, CANNOT CONNECT ETC. AND AT MICROSOFT.COM FINALLY WITH NO HOPE I'VE DOWNLOADED THE VISTA 64 VERSION AND IT WORKED.....
m
0
l
August 4, 2014 8:28:07 PM

I got code 10 when plugging in to a USB 3.0 port (front of PC). Code 10 seemed to resolve when plugging into a USB 2.0 port (front of PC).
m
0
l
November 1, 2014 2:20:56 PM

Biggus Baggus said:
I got code 10 when plugging in to a USB 3.0 port (front of PC). Code 10 seemed to resolve when plugging into a USB 2.0 port (front of PC).


I can back up Biggus Baggus (ha!) on this completely...always use the '1349' driver, and just find a USB 2.0 port to make sure the thing works.
Just did this myself (for the 10th time over a 3-year period--I seem to forget this bullshit every time and end up here and on sevenforums!).

Just letting you know.
m
0
l
January 28, 2015 10:39:49 AM

I had the same Problem with the Code 10. I managed to resolve the issue by simply deactivating and reactivating the device in the device manager. To do that you simply have to right click the device (in device manager), click on deactivate and it will become grey. Right click it again and click activate. After that it worked fine for me.

I use Windows 8.1 64bit home. The driver version is 6.3.9600.17054.
m
1
l
July 4, 2015 9:08:35 AM

Hey guys I had to first download the software, which seemed to add the needed drivers to my system. The 2.1....... driver did not work nearly 20 times. I unplugged the receiver overnight and voila the exact same procedure worked for me. EXACTLY the same. So the receiver seems to have some sort of charge it holds. By letting it sit unplugged for a while this will deplete. This seemed to allow a fresh installation of the drivers. I had used the wrong driver the first time. This caused issues as described above. So... If it does not work and you have tried ANY over drivers than the one recommended here it will not work until you unplug the receiver and uninstall the existing driver. Then allow several hours for the thing to deplete its charge.

Or you could simply put some bacon on it!

Seriously I realize this is necro, but a lot of ppl cannot resolve this problem. I figured this out on my own and I have not seen this solution any where else on the internet.

Good luck and cheers, Watchdogs is calling me.
m
0
l
July 4, 2015 9:09:04 AM

Hey guys I had to first download the software, which seemed to add the needed drivers to my system. The 2.1....... driver did not work nearly 20 times. I unplugged the receiver overnight and voila the exact same procedure worked for me. EXACTLY the same. So the receiver seems to have some sort of charge it holds. By letting it sit unplugged for a while this will deplete. This seemed to allow a fresh installation of the drivers. I had used the wrong driver the first time. This caused issues as described above. So... If it does not work and you have tried ANY over drivers than the one recommended here it will not work until you unplug the receiver and uninstall the existing driver. Then allow several hours for the thing to deplete its charge.

Or you could simply put some bacon on it!

Seriously I realize this is necro, but a lot of ppl cannot resolve this problem. I figured this out on my own and I have not seen this solution any where else on the internet.

Good luck and cheers, Watchdogs is calling me.
m
0
l