Im trying to use my 360's wireless adapter for my laptop but i cannot find the drivers anywhere. More about: xbox360 wireless network adapter laptop. Forum; SolvedI have reinstall window 7 32 bit on my laptop model Compaq persario CQ 57 TU 300.but unable to find network adapter driver.ple Forum.

Wireless Receiver for the Xbox 360 from China has arrived. Wireless Receiver for my Xbox 360 controller (Sometimes referred to as a wireless dongle) from China is one of those tools that has become more and more relevant in the gaming industry with console ports and couch co-ops. And unlike other types of electronics I have gotten from China where it was inferior or simply was nothing more then a piece of plastic or an identifier chip saying what it was but it really did nothing at all. This adapter from china actually does work! But it needs the right drivers! Video tutorial fallback mirrors: In case you have no-script enabled or for some reason cannot see the title video on this website. I have provided direct links for these videos.

• WebM – – This is the newest video standard, works great on Opera, Firefox, Chrome, and newer android phones, not good for Safari, IE, Apple. • MP4 – – The most compatible codec but also rather large in file size. Make take a while to download. • OGV – – The fallback codec for older PC’s and Linux USB stick OS’s.

1st generation web video streaming based on Ogg-Vorbis encoding. PDF file available: When I still had an analytic installed I noticed a lot of people where saving my tutorials onto the hard-drive.

I understand that you may not trust this site being around in the next few months. Or perhaps you are going into a part of the world where internet isn’t fantastic.

Or perhaps you are a seller of these receivers and are looking for a document that you can print up and attach to your product. You can now for you to have, print, and read on your hard drive. Introduction: Now for those who don’t know what this little guy does; It allows you to hook up ANY wireless Xbox 360 Controller which operates on a wireless 2.4ghz range to your PC (Up to four devices just like the original Xbox 360) which is useful for playing a lot of Steam games which are coming out which are all about Couch-Action multiplayer action. This wireless receiver is actually a really nice device to have considering Xbox One is released making the hardware of the 360 obsolete. And when hardware becomes obsolete it gets very cheap!

I personally paid for 4 Xbox 360 controllers on eBay for around $55 with shipping included. Which isn’t bad at all! Read on if you would like to know more about this little $8 unit! Original wireless receiver versus the Chinese version. This is a brief summary and differences between the two Xbox 360 receivers that you will find out on the internet. This is the official Microsoft Xbox 360 Wireless Receiver. Note the Microsoft Logo on the casing and the tab on Cable.

I should note it is next to impossible to find an OEM Microsoft 360 Wireless Receiver unless you are willing to fork out $50-60 for a controller and receiver pack. Used game stores such as GameStop will not keep these around and often will not even have a receiver. GameStop treats odd-ball hardware devices by only offering a few pennies to buy it off of someone. When you do official receivers show up on eBay. They are typically going anywhere from $15-20 dollars because they are no longer in production thanks to the Xbox One.

This can also be verified by checking the hardware ID in device manager. USB hardware ID for the official receiver is: USB VID_045E&PID_0719 This is the Chinese Xbox 360 Wireless Receiver with has no indication it came from Microsoft. Chinese receivers will come in cheaper packing (if any at all) and will not say the word “Microsoft” anywhere on the unit or package. This allows them to sell this units in this country without them getting pulled for various intellectual property related laws (And don’t think Microsoft won’t go after people for this!

They still throw cease and desist letters to people giving out MS-DOS disks for gods sake!) You’ll also get a CD and that’s about it! No real instructions in the packaging itself.

This can be verified by checking the hardware ID in device manager. USB hardware ID for the official receiver is: USB VID_045E&Pid_0291 for windows 7 or USB VID_05C6&PID_9244 for windows 10. Where to purchase the China Wireless Xbox Receiver.

• – Ignore the Malaysian listings as it generally takes three times longer then China and the sellers use dirty tactics to get the lowest price. Generally 8 to 10 dollars USD with shipping from China. • – More for North American buyers who don’t want to mess with Ebay. Prices are 9 to 13 USD plus possible shipping. • – A little more expensive then Ebay in the 12 to 14 USD range. DX however may be more suitable for international buyers. Note: Zero commission is made from these links.

These are posted as a service to those reading this blog. Wireless receiver woes: Lets go through some of the issues encountered with the Chinese Wireless receiver. Toss this CD, it’s pointless! An issue with the Chinese receiver is that although it gives you a driver-CD. That CD is absolutely useless unless you have windows XP 32-bit you minus well just throw the thing away!

So if you have a Windows 7 or Windows 8 box. The Screen Below is the typical screen you will get! Now for those who do not beleive me or just want to see what china packed onto this CD. I have uploaded an archive of my disc which can be downloaded. To access this file.

This was only uploaded for archival purposes and will not be used in any way during this tutorial. 10/5/2017 note: File has been re-compressed to.7z A.K.A for better compression. WinRAR can extract 7z files as well. No driver update, can’t point to the CD because the OS supported is Windows XP. This is because the China Xbox 360 Wireless Receiver is emitting a different hardware ID then the Microsoft one.

USB VID_05C6&PID_9244 for Windows 10 to be exact. Because of this Windows has no clue on what to do about this and Unlike a wired 360 controller or dance pad where it will simply pull its drivers off of Windows Update. It cannot do anything with our Chinese receiver. So how do we work around this problem? Simple, we force the Microsoft driver down its throat!!! Acquire the software.

You are first going to want to dealing with Xbox Controllers. We highly recommend installing this driver as it will load all of the default Microsoft interfaces for this tutorial. Microsofts driver will give you a battery utility so when you press your center button for Xbox control it will tell you how much battery is left in your controller. Direct download: This site prides itself on being the one-stop blog for everything you could need in a guide. However, as our usual disclaimer you should always run a virus checker over any executable you get from a third party site including my own. Do not trust anything unless it comes from the source manufacturer. We will keep things clean as long as the site owner is alive but you may never know!

Also note that to preserve file space and for simplicity sake all versions have been compressed into a single solid file. You may use WinRAR or to extract the files in this archive: This archive which is approximately 8Mb in size contains both the 32-bit and 64-bit versions of the Xbox 360 receiver driver. Or click on the icon to the right of this paragraph to begin.

I will always try to provide links as I am never sure when a company discontinues support. Extract files: The first thing you will want to do is get a copy of WinRAR. Basically any package that is capable of extracting 7-zip files. In this tutorial we shall extract it to C: chinaxbox. You can extract it anywhere you like just keep a note as to where you extracted these files while reading this tutorial. Notes about the archive: In the following example above we will be extracting everything in the C: chinaxbox folder.

This archive contains the following files: • Xbox360_32Eng – This is the 32 bit version of the Xbox Driver for those working with Windows 7 32-bit, Windows 8 32-bit, and finally windows 10 32-bit. • Xbox360_64Eng – This is the 64 bit version of the Xbox Driver for those working with Windows 7 64-bit, Windows 8 64-bit, and finally windows 10 64-bit. • Xbox360_Mod_XP – This version is made specifically for windows XP 32/64 bit and Windows 7 32/64.

Xbox 360 Wireless Receiver driver installation for Windows 10. For those with the latest windows 10 operating system please continue reading. Software installation. If you downloaded your driver from then you may simply double-click on the EXE file that you downloaded from them. If you used our archive.

Navigate to either the C: chinaxbox Xbox360_32Eng or C: chinaxbox Xbox360_64Eng folder depending on what OS you have installed and double-click the setup.exe file inside. The very first thing we will be doing is (with administrative rights of course) launch that installation file you have downloaded to begin installing the drivers into windows 10. Check the box to “I accept this agreement” and click the Next button to continue. You may or may not see this window depending if there was another application on your computer that requires this dependency. In windows 10 the.NET Framework 3.5 can be automatically downloaded.

If for some reason it does not automatically download for you you may to go to Microsoft’s website for.NET Framework 3.5. If you are working offsite for any reason you may wish to download the Offsite version of.NET Frame 3.5. Otherwise you can let Windows 10 take care of it for you by simply selecting “Download and install this feature” and give it permission to do so. The only reason why this program requires.NET Framework 3.5 as a dependency is due to the battery and player status tool that comes with this program which you shall see later in this blog. You may now click the Finish button to complete the installation. Plugging in the hardware.

Upon plugging in your USB cabling windows 10 will attempt to find the driver for these Chinese controllers. It of course will not find anything and label the device as “Unknown Device.” If this were a true Microsoft OEM receiver it would have found your driver and installed it ending the tutorial for you. However, due to differences in product ID we have to install this driver manually. To begin you are going to want to go to your device manager. On windows 7 you an click your Start Button and then right-click your “File Explorer” and click on Manage to open the Computer Management screen.

Finally, click on “Device Manager”. From here provided that you have already hooked up your Xbox 360 USB Receiver. We see that we have other devices that the system cannot identify. Right-click the Unknown Device and then click on Update Driver Software of this particular devic e.

Since this driver cannot be found by the CD or Windows Update. Searching automatically is a waste of time.

Click on Browse my computer for driver software. Since we are going to inject the driver manually select “Let me pick from a list of device drivers on my computer” and then click Next. Note: If you did not install the as stated at the beginning of this tutorial this catagory may not exist. In my case since I had some Xbox wired controllers Windows Update did the job for me. Select “Xbox 360 Peripherals ” and then click Next.

This is the section which deals with only Xbox 360 Controllers. All of these drivers are digitally signed indicating that they come right from Microsoft which is good. Select “Xbox 360 Wireless Receiver for Windows Version: 2.1.0.1349” and click the Next button to continue.

Note: Windows 10 by default will have the newer driver v10.0.10240. The software we just installed inserts 2.1.0.1349 into the list. The reason why I choose the old version of the driver will become very apparent when we go and test the Xbox 360 controller later on in this tutorial. I shall explain why at the end. This is the part where windows does not believe that you know what you are doing.

Silly windows. Click Yes to continue and it will begin installing the driver. It will come up stating that the driver has been successful in installation. You may now Close this window. To verify the driver is installed. Go back into your Device Manager section of Computer Management and you should see a catagory dealing with Xbox 360 Controllers.

A Xbox 360 Peripherals at the button and inside of this section Xbox 360 Wireless Receiver for Windows. Driver installation on Windows 10 is Complete Testing the Xbox 360 Wireless Receiver from china. The steps here will seem really simple for people which have owned an Xbox 360 however when looking at a lot of forums this is also the most overlooked step. Resulting in people thinking that they got a bad receiver when in all reality it is perfectly fine!

• Turn on your Xbox 360 Wireless Controller. It should have all four corners of the controller flashing indicating that it’s on but it cannot find a device to connect to. • Press the button on the wireless receiver and it will begin flashing. • While the wireless receiver is flashing, press the “Sync” button on the front of your Xbox 360 Controller as shown in the picture above.

You know it will begin to Pair the device if you see the Green LEDs on the start button of your controller move in a Clock-Wise Fashion • If you have a solid LED light in the upper left-hand corner indicating player 1. Your Xbox 360 controller is now paired up to your wireless receiver. If the LED’s spin in a clockwise circle but then returns to all lights flashing that means that it cannot find your Wireless receiver to pair up to.

(Special notes: If you are hooking this up to an Android box. The controller will still flash but at a slower speed. This is because the Android OS has no official drivers for the Xbox 360 Wireless controllers as for the date of this publish your compatibility will vary from game to game under Android) Windows will begin installing drivers the moment the controller is properly paired up. If you don’t want to go into control panel and navigate all of the different windows you can simply type the command “control joy.cpl” However, for the sake of this blog we will do it the long way in Windows 10 by first clicking on settings.

In windows 10 we will first select the Devices tab. Then we select Connected devices and finally select the devices and printers link to open up something that we are more firmilliar with in the older tutorial.

Lets see if windows can actually see and test our new joystick that we installed. Click the start menu and click “Devices and Printers”. Right-Click on the Xbox 360 Wireless Receiver for Windows and click on “ Game Controller settings”. As you see, inside of the wireless receiver is where all of the wireless Xbox 360 Controllers will reside. Click on whatever controller you would like to see and click the “Properties” button.

From here you may now start pressing buttons and moving your joystick around. You also get to see if perhaps you had any bad buttons, poor analog hats which are badly calibrated or are in need of replacement hats for your controller. Also you get to visually see how terrible the D-Pad is on the X-Box controller.:) About Driver versions. Wait a minute S, you’re telling users to install an older driver designed for windows 7 when windows 10 has it built right in. Why even install the files you provided for Windows 10?

Lets assume that you did install the “latest and greatest” driver that came built right into Microsoft. Will it work? Yes, but you will be missing two things. The first thing that you’ll notice upon using the new wireless receiver driver is all of your Xbox 360 controllers are listed as generic HID-compliant game controllers.

They are not listed as true Microsoft Xbox 360 controllers anymore. In about 80 to 90 percent of the games on the market this will not affect a thing! There are however some games that are built around the Xbox 360 controller and will map all of the keys for you if it so happens to find a true controller that came from Microsoft. This bug in the new driver is an annoyance and not a deal-breaker. Battery gauge. The second bug deals with functionality of the center xbox button. Using the old driver when you download and install the software.

Let it install Net 3.5. Normally it places a file known as XboxStat.exe as a startup program for Windows which will listen through the Chinese wireless receiver for any command from that button to give the user information such as what controller is connected, battery life, and more. This is a nice feature but once again it’s not a deal-breaker. The lights will flash on your controller when the battery is getting low. If you don’t care about this and you want to save about 3mb of memory by not installing the older driver. Then the new driver should suit you just fine. Summary of driver confusion: As for exactly why Microsoft neglected to put these tools into their OS could end up with a lot of different answers.

That they wanted to keep the drivers simple? That perhaps they didn’t bother to talk to the hardware development side of Microsoft prior to releasing their OS? Either way it goes everyone thinks that a bigger version driver means better but you have to take into consideration that this is Microsoft the same company that skipped a version number in their OS because they didn’t like the way it sounded. Version numbers no longer have the integrity they used to. American Pageant 14th Edition Ch 25 Weather. Notes for critical errors. On 02/01/16 – We had one of the Chinese wireless receivers die on me after a years worth of service bouncing back and forth between devices. This can even happen to a Microsoft OEM Receiver as the only thing that is really inside your dongle is a microchip and that’s it.

The Chinese versions don’t even have a fuse along the 5 volt power lines and in my case the regulator that reduces voltage from 5.0vdc to 3.3vdc for the chip to use was totally fried out. A dead give away that the receiver died on me is by pulling up the Hardware ID in device manager underneath the properties of the USB device and it will display USB VID_0000&PID_0000 or USB VID_???? Depending on operating system.

Also when you try installing the drivers you may receive this description for your Chinese wireless receiver. This is not a good sign. What your system is telling you is that it cannot get a response from the micro-controller inside. You can try a different computer/USB port but if it keeps saying the same thing then it’s a serious hardware failure of the receiver. Related Blog Articles: Final thoughts. Besides the driver headaches explained above.

It behaves just like the Microsoft OEM version. I got it to work all the way across my house which is identical to my Xbox 360 console wireless length. So no real complaints about connectivity or lag issues. For $8 it’s not bad and I suppose the great thing with having the wireless receiver is they give you a few feet of cable so you can place the wireless receiver anywhere giving you better reception then the Xbox 360 could ever give you.

I hope you find this article useful and hopefully it will keep a few xbox 360 controllers in circulation. If you have any problems you may leave it in the comments below. Please include OS and hardware ID of the controller you are using. Server protect you. END OF LINE+++ Categories Tags,,,,,,,,,, Post navigation. Great to hear.

The only way to really make it stick regardless of what USB port you plug it into is by modifying the inf file like what i did in the /Xbox360_Mod_XP/ folder. You can run on windows 10 but you need to do some extra steps such as disable signature enforcement similar to my. Depending on who loaded your windows 10 you may have to disable Secure Boot as well. I haven’t found an easy way to sign a 64-bit driver without paying lots and lots of money doing so. Which is why turning off certain security features is the next best thing.

Anyhow, happy gaming! That has already been done in the /Xbox360_Mod_XP/ folder on my 7-zip archive and those instructions are isolated to. The reason why I do not suggest people do what you mention above with disabling signature enforcement is due to the wall of comments received on the where you have to do it that way in order for it to work. Not only do you have to disable signature enforcement but if the OS is OEM loaded then you’re also going to have to disable secure boot or else the driver will code 39 not explaining WHY the drivers are corrupted.

It would be nice if every user disables signature enforcement so they only have to run the driver setup once and be done with it. That will end up being a lot more frustrating to the novice end-user then simply re-running the manual driver install. Anyhow, thanks for checking out my blog. I’ve had one of these things for years and love it.

I got mine off of eBay, the first one did not work and I was afraid I’d been ripped off, but after contacting the Chinese seller, they were very pleasant and sent me another for free. It seems to lose “connection” with the drivers every so often so you have to repoint the drivers to it, but that is pretty easy (I have it set up as a script I just launch from the desktop). My only real gripe is that the Mac OS X drivers will only recognize real Microsoft receivers. Which is not too bad, as I only have a PC, but I wanted to set one o up for my sister on her Mac.ah well. Still a great buy for its price! Thanks for the input and for checking out this blog! We do know of the whole loosing its drivers problem.

It happens to me when plugging it into a different USB ports. The fixes of old windows 7 such as modifying the INF file so it knows all of the time doesn’t really work on windows 10 without totally disable signature enforcement/secure boot in a windows 10 environment. There has been requests to take a look at MAC. We would love to make a blog about it.

Unfortunately there is no macs in our test lab. People just don’t throw those out like many of the machines we use for testing!:D Closest I can come is making a hackintosh machine. But someday we’ll dive into the mac universe of gaming with these receivers and other projects that we do. You can back up from that window and go to “all device” and the next window click the button “Have disk”. Type in the following path: C: chinaxbox Xbox360_64Eng xbox360 setup64 files driver win7 It should find the xusb21.inf file which contains the receiver software in it. I did a for those operating systems that simply refuse to accept what the setup.exe gives to it. As you are the second reader that experienced this I may need to update that blog entry for those who do not see the xbox receiver normally.

When you state manual selection of the xbox 360 receiver in windows. Is it at the device manager window? Or at the update driver software window? If it is not showing up at the device manager level where you have to right-click on the unknown device and update driver software.

Then there may be a serious hardware problem with your adapter. Ether it’s not making proper connection to a USB port in which you can try other ports to see if it comes back in device manager. Or, in the worst case scenario which happened to one of my four receiver where it does not even show as unknown device.

But instead shows up as “standard universal PCI to USB host controller” under the “Usb devices catagory” which effectively means that the microchip has no clue what it is anymore. Contact your vendor and ask for a refund if that is the case. If it does show up in device manager and you are able to get update driver software. But for some reason the catagory for “Xbox 360 peripherals” is blank or missing. You can back up from that window and go to “all device” and the next window click the button “Have disk”.

Type in the following path: C: chinaxbox Xbox360_64Eng xbox360 setup64 files driver win7 It should find the xusb21.inf file which contains the receiver software in it. I did a manual install tutorial for for those operating systems that simply refuse to accept what the setup.exe gives to it.

I should probably do the same for windows 10 as well. Hello, thanks for the great job on this guide. My Chinese Xbox 360 Wireless Receiver for few seconds it was recognized as a xbox360 peripheral but immediatly after shows “Device descriptor request failed”. There is something that I can do moreover to waste it? Another question: these Chinese Xbox 360 Wireless Receivers work with Android? What excatly means “If the LED’s spin in a clockwise circle but then returns to all lights flashing that means that it cannot find your Wireless receiver to pair up to.

(Special notes: If you are hooking this up to an Android box. The controller will still flash but at a slower speed. This is because the Android OS has no official drivers for the Xbox 360 Wireless controllers as for the date of this publish your compatibility will vary from game to game under Android)”? Thanks in advance Eus •.

To answer your first question: Device descriptor request errors are not a good sign. It means that although your USB is receiving power and the computer even knows your receiver is out there it cannot establish communication with the micro-controller inside to get the proper hardware ID. Basic troubleshooting is check your cabling to make sure there is not shearing, change to a different USB port. If everything is tried then you may wish to get a refund from whoever you bought the china receiver from. We have had one blow up on us after heavy use and from dropping it into a few dozen systems. Second question: Yes, they work with Android. It’s just not smart enough to tell your controller what player it is.

This requires you to import the.kl file into whatever android device you are using. If you don’t import the KL file android will map it as a “Generic Joystick” which then your controls get all weird.

It should also be noted that certain android games may see multiple xbox360 controller on a single receiver as just one controller. But that varies from game to game. Doesn’t work out for me, followed step-by-step, i install the driver and check if it was installed correctly, it is, time to test it, i start up my controller, click on the middle button of the receiver, tap on the connect button on the controller (the one between rb/lb and above the battery button) my controller just keeps on flashing the full circle while the receiver does the same but with the led, then nothing, my controller keeps on flashing, the receiver blinks about 15 secs and then the light just stays rock solid. I’ve been searching everywhere for a solution in the past fifteen hours and i can’t get it to work, so frustrated! If for some reason these wireless adapters do not sync even after installing the drivers and you know that your controllers sync with your Xbox 360 eliminating that part of the troubleshooting.

My suggestion at that level would be to contact the seller you purchased the wireless receiver for a refund/exchange. Considering these china receivers don’t even have things such as a 250Ma in-line fuse that the OEM microsoft version has it’s really easy to power-spike the chip inside causing a DOA. One out of my four receivers i bought from various vendors on Ebay did this to me.

You sure seem to know your stuff:D S- Config, Hope you can help. I’ve installed an original Microsoft wireless receiver on windows 7 home to use with two Xbox 360 wireless controllers. I downloaded and installed the Xbox 360 Wireless Controller for Windows and the Microsoft Xbox 360 accessories 1.2 software. After plugging in the receiver, Devices & Printers shows an Xbox wireless receiver under the Unspecified category.

Connecting both 360’s to the receiver goes smoothly and results in two Xbox 360 wireless controller icons appearing under the Devices category in Devices & Printers (First with player 1 light; Second with player 2 light). So what’s the problem? When I right click on either Xbox player 1 or 2 icons in Devices & Printers and go to test them – They both work with the Player 1 controller but neither will work with the player 2 controller? Also tested in notepad. Player 1 works as expected but player 2 does nothing:(. Am I missing something or is this normal for PC.

Thanks again, Marty. I have both the china and OEM receivers. But never experienced this problem myself. However, I think there was one person I heard from this experienced a similar issue. I think he resolved it by forcing the drivers in device manager because the OEM receiver can come from multiple sources. In windows 10 for example, there is a natural driver for it v10.4 and if you installed the Xbox Accessories executable from Microsoft or from my site it also gives v2.1.0.1349. Finally windows 10 could also reach out to the microsoft update servers and pull a driver from there.

Windows 10 naturally will choose the latest driver assuming its the best for your system. What I would do is go into device manager and update the driver, browse for the driver, let me pick from a list of driver, choose xbox 360 peripherals, an try to select the version v2.1.0.1349 Xbox Wireless Receiver driver (which is the one that comes with the Xbox accessories installation. ) By changing the driver it could also change the way your receiver behaves. Hopefully the joystick identification issue can be resolved. I would also re-sync your joysticks just to see if perhaps two joysticks are fighting for player 1. Hope that helps!

It’s appreciated that you want to throw some money our way. But you don’t have to.

We’re just happy the information worked out for you! But to answer your question. There actually is a BTC donation button under the donation and support section of this site. Is the address if you want to check it out. You’ll find the QR code for this sites bitcoin wallet on the bottom and we’re in the process of activating a merchant account with coinbase to make it work a little more smoother.

We don’t advertise the donation thing too heavily because we’re just happy people are stopping! That and we don’t like ads. Even our own.:) Crazy I know! I spent about an hour faffing about with drivers and on forums before I came across this.

Following your steps, I now have a working controller. Thank you SO much, I thought I was going insane. Download Film 99 Cahaya Di Langit Eropa 2 Ganool. PS: few notes for anyone still struggling: 1. I did this on Windows 7 64 bit. The OP mentioned the ‘file explorer’ when you click start. For me, I didn’t have this option but clicking Start and then right clicking ‘Computer’ and then ‘manage’ worked fine. This method does not work using the traditional ‘Devices and Printers’ screen.

For some reason it did not allow me to manually update the drivers there. (In case you’re trying that) 3. The ‘Windows Peripherals’ section did not come up for me, for whatever reason. Instead, I had to go on the full list (which took a few mins for my system to retrieve) and search for ‘M’ for the ‘Microsoft’ category and ‘X’ for the Xbox subcategory. There, I found the ‘wireless controller’ certified driver which worked.:) •. Hey, Thank you for the guide, really useful. I installed it on both of my laptops but I noticed when I wanted to hook up with the first laptop I had to do these steps again (found in the comment section): Then go into device manager, find the unknown device that is your China Xbox Controller.

Right-click and click on Update Driver Software. Then click on Browse my Computer for Driver Software. Click on Let me pick from a list of device drivers on my computer.

Click the very first catagory Show All devices. Click on the Have Disk button in the lower right-hand corner of the driver installation window. When it asks to insert your manufacturers disk where it defaults to A: either browse to the this path or if you have extracted the folder to the root of C: like I did copy this into the white text box: Do you have any idea why I needed to redo this and is this going to be needed every time I want to hook it up? Kind regards, Teddy •. The problem you are describing is one of the minor problems dealing with doing a manual driver installation versus modifying the.inf file of the driver to accept the vendor ID. And windows 10 seriously hates it when you attempt to modify the inf file. If you are on a windows XP, 7, or 8 box.

Then you could the modified.inf driver. If you want to use the modified inf driver in windows 10. You will need to disable a bit of security for it to work. Or else you will get a red ‘driver signature failed, driver has been tampered’ which windows 10 is totally right but also wrong to block the user from installing it.

In command-line. Bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS bcdedit -set TESTSIGNING ON shutdown /r it’s basically the same instructions i had to do through with the documentation for really old xbox gamepads. Under windows 7 it’s relativly easy to do. You can extract the files from the exe. Go into Xbox360_64Eng xbox360 setup64 files driver win7 modify the xusb21.inf file and replace all instances of Vid_045E&Pid_028E with Vid_045E&Pid_0291 for windows 7. Once you install the driver again windows 7 will remember that INF file reguardless of where you plug it in. Windows 10 becomes a lot more annoying!

Because even modifying the inf files makes windows 10 freak out thinking that you have injected malicious code into your driver. In order to do the same thing underneath windows 10 without me paying hundreds per year in driver re-certification is similar to my article where you have to enable test signing mode in order for it to work.

Hope it answers you question. Happy gaming! So you took it to a friends house and it works fine. But upon taking the receiver back to your computer it no longer works. If your windows box installed it as a generic human interface you may have to check the hardware tab in the advanced window and see if your ID is USB VID_045E&PID_0291 or USB VID_05C6&PID_9244. This can be found by right-clicking on the device in question.

Clicking properties. Then going into the details tab and selecting the “Hardware ID” box to reveal what USB ID it truly is. If you can find it then you can uninstall it as a human interface device.

And then re-install it as your Xbox Receiver. My 360 controller is installed and working on Windows 10 64bit with the Chinese xbox 360 wireless receiver. Device Manager Shows * Xbox 360 Wireless Receiver for Windows * Driver Date * Driver Version 10.0.14393.0 * Driver Signature Microsoft Windows Devices and Printers Show * Xbox 360 Wireless Controller Operating System: Latest Windows 10 – 1607 The problem I am having is that the controller keeps randomly disconnecting. Even when playing a game. Can hear the USB disconnect / connect sound when this happens..Any ideas on how to fix? Also is there a way to restore the Xbox Button to what is used to do? Its now linked to the Xbox app which I don’t have installed.

Before when It would bring up a xbox logo and display the battery level. On a short press. And on a long press would brig up a 3rd party application which would allow •. Hi – I have a weird problem. I followed all your instructions on the blog and I now have the drivers on my wndows 10 64 bit. I even get them to pair and sync. Lastly I went to the settings/device and printers part and the calibration button check and it works there too!!!

Thing is it doesn’t seem to control the cursor – its like its not connected at all – the only evidence I can find that it is paired is on the test window. Desperaately trying to get it to work on minecraft for my son but when I load minecraft I can only move the cursor with either the touchpad or the mouse – xbox controller does nothing even though its paired and tests properly:( Can you advise?

This is the first time I am hearing of these cases and apparently there’s two users in a row experiencing these problems. I reloaded windows 10 and let it go from the base install through all of the service updates. Installed the Xbox controller and rebooted several times and the receivers did not loose connection. Also popped the batteries out and back in and my windows 10 was able to sense and remove the controller and re-add without problems. The only thing I might be doing differently is that I am running windows 10 under the administrator account as I get annoyed with the security pop-up requesting access.

A lot of how pairing works deals with the Xbox Controller chip and the receiver chip. It’s mostly hardware controlled and if it’s already paired it can remember the controller. On my machine I could pair it before the OS is even loaded. The only time the software really comes into play is when you pair a new controller up to the receiver which could be why when you reload the driver it works. Since this isn’t happening with the China receivers I got from Ebay about a year and a half ago.

Could I ask where you got the receivers from? And also, has this been a problem since you had the receiver or did it work totally fine until it started to fail recently? Finally, what controller are you using? Stock OEM controller? Or third-party controller? If i have a real one from microsoft that will save me trouble for that read the 2 line bellow??? 1-This is because the China Xbox 360 Wireless Receiver is emitting a different hardware ID then the Microsoft one.

USB VID_045E&PID_0291 for windows 7 and USB VID_05C6&PID_9244 for Windows 10. Because of this Windows has no clue on what to do about this and Unlike a wired 360 controller or dance pad where it will simply pull its drivers off of Windows Update. 2-The first thing that you’ll notice upon using the new wireless receiver driver is all of your Xbox 360 controllers are listed as generic HID-compliant game controllers. They are not listed as true Microsoft Xbox 360 controllers anymore. In about 80 to 90 percent of the games on the market this will not affect a thing!

There are however some games that are built around the Xbox 360 controller and will map all of the keys for you if it so happens to find a true controller that came from Microsoft. If you have the real receiver from Microsoft (i.e. The one that costs around $14-19 on Ebay right about now) this saves a lot of driver headache issues in statement #1 as Windows 10 will simply install the driver for you. But statement #2 will still effect you because the Windows 10 driver will list the controllers as Generic HiD.

Once again, it’s not the end of the world if they’re listed as Generic HiD as many games will still work just fine. But for those who want the battery status and the controller notification when they press the Xbox button then you will want to go to the earlier windows 7 x64 driver. First of all thank you very much for this great tutorial.

I have a kind of specific question but because you seem to have a good knowledge about this controller and driver issues I will try my luck: me and my friends regularly do an esports event using up to 20 XBox 360 at once. During the event the controllers are deactivated and reactivated (reinstalled) while the game we play is running. Under Win7 that was no problem at all because when connecting the controlling the driver was installed “silently” in the background. Under Win10 a window is opened (//www.s-config.com/core/wp-content/uploads/2014/04/Xbox-receiver-Win10-installing-drivers-xbox-360-controller.png) which minimizes the (fullscreen) game we are playing. Do you maybe have any idea how to prevent this? Is there a way to make the controller driver installation happen “silently” in the background as it was in Win7? I can’t really help on a game by game basis.

Just that there’s some games which auto-detect the Xbox controller where-as others you may have to go into the settings or options of the game and tell the game that you have a controller hooked up in order to use it. As long as it works in the XBCD utility and it also works in windows nativly under: Windows Start >Settings >Devices >Connected Devices >Devices and Printers >and pull up the properties of your xbox controller.

Then almost any game should be able to see it as well. Anyhow, best of luck! I purchased a third party receiver from amazon a while back and it worked great for a good long year, but recently got that message – Device Descriptor Request Failed, and could never get it to work again. I purchased another receiver from a new vendor on amazon, it worked for a few days, then Windows Update happened and once again, Device Descriptor Request Failed. Are the receivers pretty much useless after that? Hours of tinkering and diagnostics reading on forums have proved fruitless and I’d really prefer to get it working again as opposed to having to get a refund and purchasing a more expensive receiver from Microsoft.

Thanks for keeping it up and being so active on this blog man, it’s very admirable ^.^ •. There isn’t a whole heck of a lot that you can do when it says “Device Descriptor Failed” because this is the error that you get when a USB device simply stops throwing its device ID down the line to your computer. You can try all of the basic stuff (I.E. Plugging into a different port. And ultimately, trying it in a different computer) But if it still errors to a device descriptor failed then the micro-controller inside probably got fried due to inadequate circuit protection/regulation like what happened to one of the three I got. The only time it should do that is if you already have controllers powered on and spinning in a clock-wise circle waiting to sync.

Typically the wireless receiver will flash for around 15-20 seconds the moment you press it waiting for you to press the sync button on your Xbox game controller. Kind of like the video that I posted where it’ll keep flashing until it finds something or times out. So it’s not normal for a wireless receiver to just flash once or twice and stop. Since there’s so many variants being made you can try doing a long press to see if that helps (3 seconds). The special xbox-driver.zip file will throw that error in windows 10 because I changed the vendor ID in the.inf file. This is a very annoying feature in windows 10 x64 where they’re locking drivers requiring digital signatures from the net in order for them to work.

Following part of my you could disable signature checking if you wish to use the xbox-driver.zip files This however, shouldn’t block the default.exe files and you should at least be able to select the drivers from Microsoft manually via device manager as explained above. Hi, I tried to do this and it didn’t work for me. My device manager doesnt recognize the receiver and is only visible when I activate the tab “show hidden devices”. There I can see my “Unknown device” and my DM reports this with code 45 (This device is not connected to the computer”.

At first I thought that the receiver was broken. But then I connected it to my laptop and after completing the instructions above, worked perfectly. Both computers work on the same OS (Windows 10). Who can help me fix this issue? Hello, I have this strange issue of my controller automatically disconnecting and reconnecting over and over or not being able to reconnect for several minutes. This mostly happens when using the emulator ePSXe but the disconnecting and reconnecting also happens less often in other games.

At one point I was playing with 3 other people and 4 xbox controllers combined and they would all have this problem. The constant disconnecting/reconnecting noise can drive you insane if you hear it over and over for long enough. The dongle was tested in another computer and had no problems and another dongle was testing on my computer and had a similar problem although slightly less often. Also this only happens when I move my computer to my GF house although the other computer which it was tested on was two feet away so I don’t think its an interference issue. The dongle was never more than 6 feet from the controllers. I’m running on Windows 10.

For testing we had about 4 different types of dongles because there was reports of these units breaking after a short while of using them. We had one which lasted for about a week before it showed up as a total unknown device. We e-mailed the Chinese vendor about it and got our money back on Ebay with no request to return the defective. If you pull up the properties of this device click on the details tab and then choose “Hardware ID’s” from the dropdown is it reporting to you all zeros?

If you are getting something like USB VID_000C&PID_0000&REV_0000? If this is the case.

Then the micro controller chip inside that dongle may have died. If it is showing an ID then there’s still hope in bringing it back. That means that the computer can see that there is -something- plugged into the USB port but the data is either corrupt or missing when it sends the command to identify itself.

Every USB device sends this little set of characters to a computer telling it what it is. Even if the computer cannot understand the new device it at least stores the hardware ID so if it finds a driver it knows what to do.

This level of data corruption can happen if a USB port is bad. In super-rare cases the operating system may be blocking the plug-n-play service. But this can also happen if the device itself is bad. One of the last things you can try is plug your receiver into a different PC if at all possible such as another laptop and/or desktop.

If it comes back with the same hardware ID failure then the chip inside of your xbox receiver is gone. If it at the very least gives a proper device ID on another machine then you start getting into possible bad USB port or OS at that point. Hope it helps.

Thank you for the super helpful post. I have a cheap chinese ZettaGuard 360 wireless adapter and I’m running Windows 10.

I installed the older driver as instructed. The controller works wonderfully and I’m getting the batter popup when i hit the xbox home button on the controller. Problem is, I’m finding that a bit annoying, and I would much rather have it bring up the Steam overlay when I hit it. If I install the newer Windows 10 driver, the controller works fine still, but now the Xbox Home button does absolutely nothing.

It doesn’t bring up the overlay as i’ve read about in other forums. It just does nothing (although the rest of the controller functions well). Is there anything i can do to get that big Xbox button to actually do something useful? There should be more people like you on the internet!

I almost crushed this ‘Chinese piece of crap’ but you made it work like a charm! Mine wouldn’t connect to the reciever and I was sure it was broken since I was convinced that even with the wrong driver, the controller should at least connect to it. As it appears, that’s not the case. At first under ‘select the device driver you want to install for this hardware’ I chose the wrong driver, which seems an easy mistake since there are a few others to choose that also make sense. Many thanks from Amsterdam.

Just so folks from Holland will also find your page on Google: Draadloze 360 controller voor pc maakt geen verbinding met ontvanger •. I have been using this Chinese adaptor successfully for about a year with minimal issues, and it was even fine after my upgrade to Windows 10. But this weekend I came home to a restarted computer (presumably for an update), and suddenly my receiver doesn’t work properly. I connect the controller as usual, and it works for around ten seconds in Fallout 4 and about a minute in Witcher 3, before the controller simply stops sending (or the receiver stops receiving) any input.

There is no blinking light or a disconnecting sound from Windows to indicate a connection has been dropped. From there I have to uninstall and reinstall the driver to get it responsive again, and it repeats this over and over. I tried using the Windows 10 and 7 drivers, as well as your method. When I attempt to use your drivers downloaded from this page, it will not successfully install, saying, “The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.” Any insights into this?

Any help would be MUCH appreciated. Well, windows 10 is correct. I did tamper with the file. I changed the inf to find the device ID of the Chinese driver in that one. You will have to disable driver signature verification.

Start >shutdown >hold shift+click restart >troubleshoot >advanced options >startup settings >disable driver signature enforcement. That should calm windows 10 down. But I don’t think a driver issue is your problem.

If it only works for a little bit after you unplug and replug it back in. It sounds like you’re dealing more with a hardware issue. Either the microprocessor in your controller is locking up. Or the microprocessor in your Chinese receiver is locking up. In ether case I haven’t experienced this myself. You can try plugging the receiver into another laptop or PC, doesn’t have to be an ultra-modern gaming pc just enough to load the drivers and see how it behaves in the joystick menus.

Controller testing, of you got a xbox 360 pair it up and see how it behaves. If it doesn’t lock then its not the controller. Finally, you could try different USB ports. If you have a modern PC plug it into a USB 3.0 slot to see if problems go away. I say usb 3.0 not because of the speed but in general a USB 3.0 will be a different chipset then your USB 2.0’s. Apologies if the troubleshooting seems kind of vague. It’s a problem I never encountered myself.

If anyone else wants to chime in feed free. On all three of the receivers that I have and use for testing they all light up green the moment you supply power to the USB port. So it sounds like there’s something wrong with the microprocessor that’s in your receiver. That it may identify itself as a device in device manager but may have any programming to actually turn on the light to even say its ready. Much less to sync. Bottom line, if you’re not getting lights.

Then you probably have a defective. It can even happen to a Microsoft OEM receiver too. If you’re Xbox receiver is installed correctly in device manager as described on my. Then it sounds like it’s coming down to a pairing issue between your controller and the receiver.

If you are pressing the sync button on the front of your Xbox 360 controller first and the receiver next and the controller LEDs spin clockwise but never assigns a player ID. There’s two things to try. 1: Is it possible to test your controller on a Xbox 360? Just to verify that your controller did not burn out it’s internal wireless amp. 2: If you don’t have a Xbox 360 game console do you have another controller by chance to try it out with? If the controller pairs with the Xbox 360 gaming unit but not the wireless receiver.

It can be possible that you may have a defective receiver as the receiver does a lot of the work of pairing the controllers before device manager even sees it. It doesn’t even make the sound that a device is plugged in and unplugged when moving the Xbox receiver from port to port? If it is at least making the sound then we know windows acknowledges that it’s there but it may be doing something dumb by placing the controller in a totally different catagory in device manager such as Universal Serial Bus at the bottom of device manager as just an example. Which if it thinks its a ho-hum genetic USB device then the controller will simply not work.

I will have try to take a windows 7 box and upgrade it to 10. My test boxes both x86 and x64 were clean windows 10 installs right off of the retail DVD. Sorry to hear it’s not working out for you. Usually the installation works as it copies the.inf files into your OS-System folders allowing you to actually see it when you go into Microsoft Controllers. But there could be factors which may be beyond the scope of this blog such as firewall controll or access policies I may not be aware of. Then using a program like WinRAR, you’re going to extract the files from the EXE files into a folder because it’s just a self-extracting zip container that Microsoft uses. If you have extracted it to your C: drive.

It should give you a folder with the same name as your exe file. In my case the 64 bit example is located in C: Xbox360_64Eng Then go into device manager, find the unknown device that is your China Xbox Controller. Right-click and click on Update Driver Software. Then click on Browse my Computer for Driver Software.

Click on Let me pick from a list of device drivers on my computer. Click the very first catagory Show All devices. Click on the Have Disk button in the lower right-hand corner of the driver installation window. When it asks to insert your manufacturers disk where it defaults to A: either browse to the this path or if you have extracted the folder to the root of C: like I did copy this into the white text box: C: Xbox360_64Eng xbox360 setup64 files driver win7 It will finally come up with three selections. The bottom one being “Xbox 360 Wireless Receiver for windows”. Click on Xbox 360 Wireless Receiver for windows. And then Click Next.

Click Yes to the update driver warning. Profit.:D That should be the procedure to manually install the driver without running the Microsoft executable. The closest error I have ever seen on updating drivers is the following: “This verison of this file is not compatible with the version of Windows you’re running.” Which the first thing the Microsoft Community would ask is what version of windows are you running?

To verify this. Click on the start button in the lower left-hand corner, right-click on computer, and then click properties. It will tell you the version of windows you are running at the type, and underneath the system catagory it states if you are running 32 or 64 bit (or even ARM if you are running Windows Tablet edition). Before i ordered my ebay (china) wireless receiver i was looking arround for info on it and came across this blog. Saved the link and now my receiver got in the mail i instantly checked this blog again and had it up and running in no time!! Extremely clear installation steps and very thorough.

Thanks for taking the time to write this how-to. Usually i don’t take the time to comment when i find info but this was so usefull and put together very well that i just had to comment. Many thanks from Belgium!

• • Helpful resources • • • • • General rules • Follow • Keep it civil and on topic. Comments or posts that are disrespectful or encourage harassment of others (including witch-hunts of any kind) are not allowed. • Do not post pirated content or promote it in any way. • Blogspam, mobile links and URL shorteners (such as tinyurl or bit.ly) are not allowed. • Do not post any offensive material • Do not post personal information (address, email, phone number, etc.) • Please remain respectful to users at all times. • Do not 'backseat moderate' - Report any rule breakers to • No spamming, advertising.

• No referral/affiliate-links. • Promoted Subreddits • - Office 365 Team communication service subreddit. • - Main Windows community for all versions of Windows. • - dedicated to Windows Mobile OS and discussions about it. • - dedicated to Windows Insider program, WI builds troubleshooting. • - dedicated to Xbox One console and its peripherals, news and discussions.

• - dedicated to Surface powerful laptop/tablet and discussions around it and its peripherals. • - dedicated to Excel, powerful program of Office suite. This subreddit is suitable for both Office warriors and newbies.

Filter content by flair • • • • • • • • • • • • • • • • • • Related Subreddits • - dedicated to solving problems and helping others out. • - Android Operating system and its peripherals discussions. • - Apple devices, services discussions. I used the steps in this thread to get the adapter working: Getting Internet Explorer to work properly was a PITA, so here is a link to the driver download: As soon as you have the.cab file, you can extract it and point the driver updater to it.

I know the link looks sketchy, so if you don't trust me you can follow the steps in the steam thread. Edit (04/21/16): People have been asking for the Windows 7 version of the driver. I HAVE NOT tested these drivers, but they are from the same page as the Windows 10 version. Oh my gosh I love you.

Download appears legit for anyone else endlessly googling for this. (I trust it, it worked, no issues). I mean fucking hell getting the dongle working was a huge pain in the ass.

This fixed it so easily. Also fucking annoying that MS's catalogue thing doesn't work in edge, but the dongle is a win10 device only, which makes fixing it a huge pain. Wonder why the drivers for it are so broken. Edit: For future google search troubles: Error 10. This device cannot start. Driver download. Since that's what I searched for at first and couldn't find anything useful.