Fake Xbox 360 Controller Driver

  1. 360 Controller On Pc
  2. Fake Xbox 360 Controller Driver Download

After playing around with Nintendo 64 emulators with the intention of taking screenshots for some N64 games that I plan to review one of these days, I determined that it was finally time to break down and get a new gamepad for my PC. None of my other pads had anything akin to analog sticks – I mostly bought them with playing much older games in mind. I’m a big fan of the Xbox 360 controller and since I already have a couple I figured it would be easiest (and probably most economical) to go the route of buying the Microsoft Xbox 360 Wireless Gaming Receiver which simply let you use your Xbox 360 controllers with your PC. Looking around I quickly discovered that these receivers were in shorter supply than they used to be, some places even charging quite a bit for them. Still, I ended up finding some eStores on Amazon that had them for fairly cheap and nabbed one.

  1. Today we checked out fake xbox 360 controller and it is actually very good. This controller really gives you no reason to buy original. It very well made.
  2. Then, Xbox 360 Peripherals at the button and inside of this section Xbox 360 Wireless Receiver for Windows. Driver installation on Windows 10 is Complete. Syncing the Xbox China receiver to the Xbox 360 controller. The steps here will seem simple for people who have owned an Xbox 360.
  3. Connect your XBox 360 controller to your PC. You need a wired XBox 360 controller that connects to a USB port or a wireless controller with a wireless adapter. Your PC needs to be running Windows 10 on the same network as your XBox One. Both devices need to be connected the same way to your home network.

When it finally arrived I immediately recognized it as a fake – not just some other brand, but a genuine, stereotypical Chinese counterfeit. The packaging didn’t quite look up to par – while at first glance it was reasonably similar to official looking packaging, the plastic blister pack wasn’t nearly as stylized as most Xbox 360 related packs, and perhaps even more telling, it wasn’t an immense fucking chore to get into. Also despite some okay use of Xbox 360 and Xbox Live logos and branding style there wasn’t a single sign of a Microsoft logo anywhere on the packaging – not a good sign as Microsoft LOVES to crap their corporate logo all over everything they make. The unit itself looked identical to the real thing save for the Microsoft logo on the front being replaced by an Xbox 360 logo and the little holographic seal sticker on the back saying “XBHD” instead of Microsoft. Other stickers on the unit and packaging looked a little off as well. Upon closer inspection it is even more suspicious – the connect button isn’t flush and is even a little offset, the rubber “foot” ring on the bottom isn’t seated perfectly and looks a little odd, and the piece of the housing where the cord goes in wasn’t seated properly. None of these were major issues, but an obvious departure from the high quality standards that you usually see in Microsoft hardware.

“Quite a departure from the real packaging but good at a glance.”

At first I was pissed about being duped by Amazon (who listed it as being a Microsoft product and having pictures of the genuine article) but the more I researched the more I discovered how common place these knockoff receivers actually are – they’ve been floating around for years now, presumably ever since Microsoft stopped supplying the real thing as readily. Most people have reported success with them. In fact, some people even preferred them to the genuine ones as apparently they don’t have the fuse issues the real ones have. If I complained and returned it by the time I paid return shipping and whatever “restocking” fee the eStore might have I’d probably be paying double what I paid and, I figured, if it works, I certainly didn’t pay much for it even if it is a fake. Still, I was highly skeptical – I figured though, if it were a true counterfeit and would work okay with the official Microsoft drivers I wouldn’t be putting myself in any danger by using it and, from what I read, despite some occasional difficulty in getting Windows 7 to recognize the device the official drivers worked fine with it. Still running Windows XP 32bit, I guessed I’d probably be fine.

I've done that, uninstalling the driver was the only way to fix it. I've reinstalled the driver a bunch of times already and that did not help, the issue remains the same, the controller appears as a detected device in the devices manager, it recognizes it as an xbox 360 controller, but it won't work in games, won't send or receive any input, checking the 'Game Controllers' setting doesn't.

I wasn’t about to try the software on the disk that came with it figuring that it would be some poorly written knockoff driver that would destabilize my machine, or worse yet be infected with malware (although upon further inspection the disk appeared to include the genuine Microsoft driver, albeit an older version.) I immediately grabbed the Microsoft package and went from there. Hours later, I finally got the fucking thing working. At first I couldn’t get Windows to recognize the device as being compatible with the driver, even after trying to force it to use it. Later I abandoned that version and went for the same one that was on the included disk, and although that one was recognized the driver installation would fail every time. I’ll save the gory details and get to the point – since my solution ended up being an amalgamation of various other tips rather than based on any one thing I read online, here is how I got my knockoff receiver working with Windows XP SP3:

Don’t plug it in yet – if you’ve already done so, go to your Device Manager, uninstall it, and unplug it. It depends on how far you got it, but it’ll likely show up as an “Unknown Device” with a black and yellow exclamation mark on it. It could also show up as a “USB Device” or possibly even as an “Xbox 360 Wireless Receiver for Windows”. Just look for the exclamation mark.

  1. Download and install the latest official Microsoft Xbox 360 Wireless package: http://www.microsoft.com/hardware/en-us/d/xbox-360-wireless-controller-for-windows
  2. Download and extract this updated version of the device driver to someplace temporary: here
  3. Plug the receiver in. Windows will detect it and attempt to install a driver for it. If yours behaves as mine did it will NOT automatically match up with the official package you installed in step 1. Otherwise, you got lucky and you’re done!
  4. Choose the second option: “Install from a list or specific location (Advanced)”. Click Next.
  5. Choose the second option: “Don’t search. I will choose the driver to install.” Click Next.
  6. If it shows you a list of hardware categories click Next first. Click “Have Disk…” and find the “xusb21.inf” file that you extracted from the archive in step 2.
  7. If for some reason it comes up asking for additional files, choose them from the same location where you found “xusb21.inf” in the last step, in the “x86” (or “x64” if you’re running 64bit Windows XP) folder below it.
  8. If for some reason it asks for “WdfCoInstaller01005.dll” when “WdfCoInstaller01007.dll” is what you’ve got in “x86” you can insert the included driver CD and find it there. It was in “PC Driverx86” on my disk. It did this to me though it was a result of my earlier attempts to get the original driver working.
  9. It should copy the files and then be done. If you receive a “Fatal error during installation” error my solution didn’t work for you. Otherwise, click Finish and try syncing up your controller!

I hope that helps somebody out there. If the thought of dealing with shady Chinese hardware and old driver packages scares you I’d recommend trying to track down a wired Microsoft Xbox 360 controller (a Play and Charge kit for the wireless controller will NOT work) from a used game store and simply using that if you can find it for cheap, though they sell at Gamestop for about 3 times what I got my knockoff receiver for. *shrug*

Some sources:
The thread where I originally found the updated driver
A blog article troubleshooting similar problems under Windows 7 64bit

Update 9/2016:

Manace comments “It works on Windows 10 x64. You should first start a cmd.exe as administrator and type: “bcdedit.exe -set TESTSIGNING on” (without the quotes). Then reboot and you see in the down right corner “TESTMODE”. This means you can install unsigned drivers.

Now got to your device manager, select the unknown device, choose update driver, select the folder where you extracted the driver package and voila!”

You can also install unsigned drivers this way.

🚨 Obsolete solution 🚨

DsHidMini (official successor) has been released, please use that instead! This article will remain online for historic reasons but use is discouraged as no more updates will follow!

What's this

Ever wanted to use those pesky outdated yet absolutely lovely game controller devices shipped with your PlayStation(R) 3 on the Windows platform without constantly tripping over wires in your living room and risking becoming a victim of gravity? Well fear no more, you've come to the right place, mate! We got just the piece of magnificent software you need and all it will cost you is a few minutes of your precious time!

Coming to you from the Austrian University of Awesome (AUA ), BthPS3 has surfaced as the result of research and development by one crazed fella; Dr. Nefarius! Known for his expertise of building software nobody knows how to even install or, for that matter, getting rid of!

Sounds exciting? Want to join the herd and risk getting your PC turned into something even greater than before? Well, what are you even waiting for, keep on reading, spirited traveler!

Uh, what do you need from me

Simple! Just latest Windows 10 and any Bluetooth USB device or integrated card (like those you commonly find in portable computers, a.k.a. Laptops) running stock (a.k.a vanilla) drivers! No SCP, no AirBender, just the defaults (well, not quite, but keep on reading 'till the bottom of the page! )

Sweet, give me! How to install

Download Setup for Windows 10

Grab and run the setup, it will tell you everything you need to know, just click through it

Now is the time to plug in your Bluetooth dongle, if you haven't already

If you have an integrated card - like on laptops - make sure it is turned ON before you continue!

If you don't, setup will be very sad and will abort mission.

So play along and ensure it's happy, will ya

Alright, that was scary, what to do next?

Fear not, we're almost at the finish line! Now comes the part that's a bit rough but together we shall succeed!

Get all the files

Download and store all the fun listed here somewhere on your battle station

  • Get the latest Shibari.zipfrom here (always pick the highest version number from the bottom for most recent release)
    • This plays the 'middle man' between all those drivers you'll install
  • Get the latest FireShock.zipfrom here
    • This is required for USB connection and automatic pairing
  • Get the latest ViGEm Bus Driverfrom here
    • This is required for presenting the devices as either Xbox 360 or DualShock 4 controllers to games

Install drivers

Fake Xbox 360 Controller DriverGucci
  • Extract the FireShock archive somewhere and simply execute the dpinst (or dpinst64) tool included which will install the USB driver
  • Run the ViGEm Bus Driver setup and simply click through it until finished

360 Controller On Pc

Ready for some action

You made it this far? Great! Remember that Shibari archive from earlier? Extract that somewhere and have a look into the resulting folder. Simply fire up Shibari.Dom.Server.exe in there and your connected DS3 should spawn a virtual Xbox 360 and DualShock 4 controller which your games can pick up. Keep Shibari running for everything to work properly! Check the following F.A.Q. to see how to make it run permanently. Enjoy!


Have you gone insane?

Maybe! When you stare into the kernel for too long, the kernel stares back

Is this some official Sony thing?

Well, obviously not, as clearly stated literally everywhere! It's a research project I started for fun and pushed towards becoming production-ready and thought it might be of use to my fellow gamers!

Does this thing phone home? I see some network traffic once a day...

I ship a self-updater with my drivers since pushing security/stability critical enhancements is vital for drivers. The updater checks updates.vigem.org once a day and remains silent if you're sporting the most recent version. There's a scheduled task called BthPS3Updater you can disable/delete by hand if this makes you nervous.

Not a thing anymore since v1.3.x of BthPS3.

Why don't you cover Windows versions lower than 10?

Production-signing is unfortunately fairly annoying and unnecessary complicated for drivers targeting multiple major revisions of Windows so to keep my sanity I went for Windows 10 only. The code of BthPS3 is - as we speak - technically compatible from Windows 7 to 10 so it could be back-ported in the future with little efforts.

Starting with this commit Windows 7 support is no longer given due to the introduction of a dependency not present in older OS versions.

Why is this Shibari thingy necessary to run this clutter?

I have plans for getting completely rid of this requirement, but that requires additional drivers which I've started working on but currently don't have the drive or capacity to deal with. Maybe if support and interest from the community rises above a certain threshold I'll tackle that topic some day again!

No need, use DsHidMini instead of Shibari and FireShock!

How do I get pressure sensitive buttons in PCSX2 with this?

That is possible but out of the scope of this project. DsHidMini can do that for you!

Can I use the motion capabilities of the PS3 controllers?

That is possible but out of the scope of this project.

I want some battery charge indicator, like SCP!

That is possible but out of the scope of this project. DsHidMini can do that for you!

Can I have all SCP features like quick disconnect combo etc.?

That is possible but out of the scope of this project. DsHidMini can do that for you!

Fake Xbox 360 Controller Driver Download

I sometimes need to power on the controller twice or more until it stays connected...

That's due to how certain connection details get stored within the Microsoft Bluetooth DDIs and when the driver attaches, there's no way around that other than just powering the controller on again!

The setup version doesn't match the driver version it installs...

That's intentional; not every tweak and fix the setup itself receives necessarily requires an update of the driver binaries. So all fine there!

I want a DualShock 4 emulated, not an Xbox 360 controller!

Open settings.json in your Shibari folder and check out the comments in the 'sinks' section

Ever since I've installed this, my DS3 isn't working anymore in PSNow!

FireShock and Sonys official sixaxis driver they ship with PSNow unfortunately can't coexist on the same system, if you want 'traditional' USB support back you need to uninstall FireShock:

Use DsHidMini instead to get that feature back!

Ever since I've installed this, my DS4 isn't connecting anymore at all!

This is a bit tricky at the moment; I've added a workaround to combat this where you should be able to use it like before without any troubles if you simply power it on, let it shut off after one or two seconds and then within a time span of ten seconds power it on again and it should work.

How can I keep Shibari running in the background?

Shibari can easily be installed as a Windows Service running in the background without the need to start it every time you'd like to use your devices and have an additional Window open all the time.

Fire up PowerShell as Administrator and run the Shibari.Dom.Server.exe file with install as an argument, like so:

The path to the executable file has to match the one on your machine of course 😉

Right after that start the service:

Check that the service is running:

Done, delightful 😃

My controller is randomly pressing buttons or axes jitter, bug!!1!

Nope, this isn't and never was a software issue. Any misbehavior in regards to reported inputs comes from the controller hardware itself, not my tools. In short: your device is damaged or reached the end of its lifespan, sorry! Time to replace! 😔

If you sport some of those lovely fake aftermarket devices from questionable stores from far away costing only a dime or two then you might have been screwed over and my software is not here to fix hardware manufacturers cuts, get proper genuine hardware or at least higher quality replicas

Copyright (C) 2018-2021 - Nefarius Software Solutions e.U.

This is a community project and not affiliated with Sony Interactive Entertainment Inc. in any way.

'PlayStation', 'PSP', 'PS2', 'PS one', 'DUALSHOCK' and 'SIXAXIS' are registered trademarks of Sony Interactive Entertainment Inc.