XBCD – Original Xbox Controllers with Win10-8

XBCD – Getting those old controllers working again!

XBCD is an abbreviation for the “X-Box Controller Driver” Which has been around for almost as long as the Original Xbox Controllers themselves (approximately 2001-2003). As of 5/4/2017 the guide was updated to illustrate ways of installing these drivers which hopefully will answer the many questions that we get about them. This new method also no longer requires the testsigning feature which also eliminates the requirement for UWD.exe which should make some of our subscribers happy.

(Especially YOU TimmyP! Yeah, I didn’t forget you! UWD.exe is gone! Your welcome!)


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 – Link – This is the newest video standard, works great on Opera, Firefox, Chrome, and newer android phones, not good for Safari, IE, Apple.
  • MP4 – Link – The most compatible codec but also rather large in file size. May take a while to download.
  • OGV – Link – The fallback codec for older PC’s and Linux USB stick OS’s. 1st generation web video streaming based on Ogg-Vorbis encoding.


It should be noted like any hardware or software hack that we are not responsible for any physical, mental, financial, or psychological damage which may happen when following this tutorial. The drivers and software provided are intended to work in an AS-IS bases. We provide no guarantees if it will work with your product. This tutorial also contains internal links for binary files to which we highly suggest that you invest in a good virus checker prior to downloading anything off of the internet. Trust no one! For additional and general questions refer to the FAQ of this site.

History time!

Back in the days when Microsoft got involved with the console wars. They made a bunch of controllers for their X-Box units which people began to realize that if you just splice a USB cable on the end of the proprietary connection then you could use the Xbox Controller on your PC. Microsoft at the time really didn’t want to associate hardware from their console with hardware with their PC because a few corporate people back then felt it would disenfranchise their user base from actually purchasing an Xbox.

Xbox 360 and onward.

It wasn’t until the introduction of the Xbox 360 that Microsoft gave support for their users to use their beloved controllers on their PC’s and other devices. Even then Xbox 360 controller support for PC users came incredibly late throughout the production run of the Xbox 360. As of the Xbox One the controllers can work with Windows 10 games provided of course you buy their proprietary wireless receiver or you hook a USB cable direct to your PC and hope that mini-USB interface does not break or else you will never be able to charge said Xbox One controller.

XBCD development cycle.

Like all things, XBCD development stopped as many thought it wasn’t necessary to develop. I even posted a blog article talking about the Wireless Xbox 360 receivers and controllers and how awesome they were. Windows XP was the last official supported version of XBCD 0.2.7 with some 32 bit work for Windows Vista . However, for those users that want to keep their controllers going in the year 2016 there’s a way to keep on rocking with these controllers.

Hardware Prerequisites for XBCD and how to hook it to your computer.

Lets get the hardware section out of the way first. If you ever picked up an original Xbox controller you will notice right away its proprietary connector that is attached to the joysticks. We need to convert that connection into something a little more usable for our PC.

You could buy a converter cable.

Ebay – has a large assortment of cables under $10 easy.

Amazon – also has these cables available as well!

Thanks for Mantis Toboggan M.D.4 for finding links and the proper name for these cables. Either link you choose to buy a cable just know that we don’t many any money providing Ebay or Amazon links and just do it as a service for those interested in purchasing the adapter versus building one.

Make your own Xbox to USB adapter.

Lucky for us , the wiring of the Xbox joysticks is very easy, simply strip the wires down, find a USB cable you don’t mind destroying, strip that down, and match the colors within the cable to the appropriate selection. The only cable you do not connect is the yellow clock/timer chip. You could use a USB A Male to Xbox female connector out of a destroyed Xbox unit like I did to preserve your original Xbox Joysticks. Or if you no longer care about authenticity and just want to get that ultra cheap controller working then you can simply cut the cable on that joystick and add the USB cable right onto it.

You could just wire twist them on and shrink tube it together, or solder it together and then use shrink tube (preferred). Does not matter so long as the cabling is secure as we don’t want this to come apart as we’re playing a game. It should also be noted that if you do have an original Xbox that by splicing a Xbox male connector and USB female that you can hook things up like usb stick (limited compatibility restricted to 2gb) for save games as well as hooking up keyboards for some of the home-brew titles that exist out there.

Back in the day when you upgraded your Xbox Original case sometimes the vendor didn’t feel like removing anything from the front panel such as the control panel buttons and the Xbox connectors that they wanted users to transfer their guts over as quickly as possible. Since these were held in by a few screws they were easy to extract and easy to plug into my own little case for it. Using a Cheap USB hub it can be soldered all of the connectors into a single box so you have a breakout box for party games.

Software Prerequisites.

Now we can finally talk about the software side of things to get it all working on your Windows box. Some of you may wonder why we host the files directly versus referring you off to a forum or another site. The answer is simple:

A tutorial should not infect your computer with spyware!

When visiting the forums which contained this driver we were getting redirected to an ad.fly pay-per-click service. This service refused to let us download the binary until we turn off ad-block. Upon turning off ad-block ad.fly then produced a pop-under window which immediately began an attempt to install a Trojan onto an unsuspecting users PC. This is what happens when you don’t pay for storage. Eventually someone else will pay for it and you won’t like what they will do to your good name! Infecting peoples PCs wish spyware/malware/ransomware is totally counterproductive to what you are trying to do which is make a old piece of hardware work on a modern computer.

Unlike other sites which will route you through hell and endanger your PC. We are not going to do that to you. Because we love you too much.

Direct link to the XBCD Software:

I have provided a direct link for everything that you need for XBCD.

Inside this archive:
  • A Driver folder which has the same files that the XBCD script installs into C:\Program Files(x86)\XBCD\ . These are here for people who don’t want to use the XBCD utility.
  • A shortcut folder which has a shortcut to the XBCD utility since the installation script may not generate this shortcut automatically.
  • x360ce-x32 and x360ce-x64 folders. These are utilities which help certain games acknowledge the fact that a legit xbox 360 controller is hooked up when in fact it is not. Respectfully these are later versions then what XBCD installs into C:\Program Files(x86)\XBCD\ and can be used for games that require the presence of a true Xbox controller. All DLL files for windows 10 are rolls into those folder too.
  • disable.bat and enable.bat for turning off integrity checking within Windows 10 64-bit edition.
  • XBCD_Installer_0.2.7.exe – the binary file itself!

Click on the download link on the right hand side to go grab the file. Credit goes off to RedCl0ud for this wonderful software. Everything is open source and free for anyone to add/modify to it so go nuts.


Using your favorite file extractor; Unzip all of these files to a folder you can remember. This tutorial is going to use C:\xbcd\ as the reference from here on out.

Hardware verification:

It’s always a good idea to verify the hardware that is being installed whenever you are plugging in something new into your PC. This should be a habit that everyone does because it could save you hours of headaches installing drivers on the wrong device or if the device is not even detected properly. To access this either right-click on your start button and open device manager. Or press the windows + r key and type in the following.

mmc devmgmt.msc

The device manager window will open up. Plug in your Xbox controller now and you should see Device Manager flicker attempting to identify the USB device. It will ultimately list the device as “Unknown device” in the “Other Devices” catagory. Right-Click on the Unknown Device and click “Properties”. Click on the Details tab and under the property drop-down box select “Hardware Ids” In the window above we have USB\VIS_045E&PID_020&REV_0100. A VID_045E. This game-pad is a Microsoft Xbox and a product ID of 0202 which is the Original Xbox “Duke” controller. Vendor IDs will change if you plug in third party controllers like Madcatz or Pelican controllers. Product IDs will also change with third party. But can also change if you plug in the original Xbox “Duke” Controller versus the original Xbox “S” Controller. As long as it produces an ID is the only thing we are looking for here.

If you see a VID_0000&PID_0000 or VID_???&PID_??? . Then your computer cannot detect the controller and you need to stop right here and identify what is wrong with your Xbox controller such as possible bad wiring or if it needs more serious repair. Installing the driver will not help if you if you one of those two Hardware IDs.


Installing XBCD.

Great, I have the files, I can just launch XBCD_Installer_0.2.7.exe and I’m good to go right?

If you are running Windows 7, or Windows 10 32-bit then yes. This tutorial ends for you right about now. Windows 32-bit edition does not rely on heavy driver verification.

For the majority of users running windows 64-bit edition this is the error that you will more then likely see if you attempt to run the setup file without doing anything. From the setup file it doesn’t really tell you why the installation failed. For that we go back into device manager.

If you attempt to install the XBCD driver from C:\XBCD\driver via device manager. We get a more precise error as to what is going on. Which simply put our driver does not have an online certificate which costs $200+ dollars a year to make windows 64 happy. In order to get around this error we are going to have to disable some of the security which is installed into Windows 10 64-bit.

Disabling integrity checking in Windows 10 64-bit.

We have provided a file named disable.bat within the archive which attempts to automate this process for you by elevating itself to administrator status and passing all of the commands into the windows bootloader so that it can boot with integrity checking disabled. If you don’t trust my batch files which you have no right to trust. Simply open a command-line with administrative access and pass the following commands.

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set nointegritychecks ON

And reboot the PC.

Script fails and still cannot install drivers. Disabling integrity checking manually.

Sometimes windows 10 gets especially obnoxious about drivers and we will continue to get digital signature errors. Here is how to totally disable integrity checking manually one time so we can install the driver.

Click the windows button then click on the power icon right above. While holding down your shift key and left-click the restart option.

If you held down the shift key and pressed that restart button correctly you will be presented with a menu of something like what is above. Select Troubleshoot.

Select Advanced options.

Select Start-Up Settings.

Finally Select the “Restart” button and the computer will go into boot selection mode.

You will not have a mouse in this mode. simply pressing the 7 key will be enough for the OS to reboot once more allowing you to finally be in the mode that we want to install the driver.

It should also be noted that manually disabling driver signature enforcement is only good for one reboot versus the script or command-line method which is a more permanent approach towards disabling signature enforcement.

If you only choose the manual method of disabling integrity checking then the next time you need to install a driver you will have to go through the manual process again.

Installing the driver for XBCD

Now that we have straightened out integrity checking you may not want to run the XBCD wizard again. After-all the XBCD control panel is installed and the driver installation wizard isn’t all that helpful. So lets do this manually. Go back into device manager and right-click on our unknown device which we confirmed it was our Xbox controller earlier. Select “Update Driver Software.”

We wish to select “Browse my computer for driver software”

In general we don’t trust Windows in doing anything right. Select “Let me pick from a list of drive drivers on my computer.”

The default selection of “Show All Devices” is fine. Click Next to continue.

Select the “Have Disk…” button to continue.

You can click the “Browse” button to find the folder that our driver is in. You may use the provided driver in C:\xbcd\Driver or you may also use the driver that the XBCD installer provides in C:\Program files(x86)\xbcd\Driver\ it does not matter.

Once have you have selected your folder click “OK” to continue.

It finds out controller which is good. If it does not then check your Hardware ID of your unknown device. Click Next to finally install this driver.

Now that driver integrity checking is disable we are welcomed with something a little more retro which is this window warning us that it can’t verify the driver. This is very good. Click “Install this driver software anyway” and it should begin loading the XBCD driver into your Windows 10 64-bit box.

Driver installation is now complete.

The XBCD Xbox Controller driver now takes it’s place in the Human Interface Device catagory of device manager. Installation is complete and onward to the testing.

Testing the XBCD joystick..

To pull up the window above. You can press the window key + R to bring up a rum prompt and type in:


Then click on the properties button.

Alternatively, you can click on your windows logo and click on settings, devices, connected devices, and scroll down to devices and printers.

From here you can right-click on the XBCD Xbox Controller and click properties.

But you’ll notice something is different from a regular Xbox 360 controller, it is recording a lot of buttons, and the shoulder buttons are recognizing as digital buttons which could mess you up in certain games that assume that every player out there has a Xbox 360 or Xbox One controller hooked up to their PC.

Since the XBCD installation utility is very old it may not generate the necessary shortcuts for you in windows 64. I have made my own shoutcut under the C:\XBCD\shoutcut folder that you can copy out to the desktop. Once you have it on your desktop. Right-Click on it and Run as administrator. If you fail to run this program as administrator it will error out on you.

Once you have the XBCD utility launched you can then select a profile of XBCD 360 Emu and click the Apply button. It will then change the personality of your default classic Xbox controller into something more like the Xbox 360 controller for games on windows. This utility is insanely powerful as you can remap buttons and even accesses to digital pads which is very useful if you so happen to have any Dance Pads as you cannot hold both left-right pots down simultaneously with the default windows joystick mapping.

Now if you go back to your windows joystick test program, you will see that the layout is behaving more like a standard Xbox 360 controller and your shoulder buttons are back with their analog hat feel to them.

Disclaimers, security and integrity concerns about Windows 10:

But S, isn’t it dangerous to run windows 64 bit with the integrity checking disabled and test signing on?

I’m no MCSE expert but I’m going to say “Yes.” However, it makes you about as vulnerable as a windows 7 box. Microsoft keeps adding more and more layers of security to their OS in the hopes of keeping bad things out such as malware and ad-ware affecting the very core of your operating system. To turn off those sections could invite some of those in maybe. But if you are like me and have a dedicated PC assigned to couch gaming or emulators which if something or someone breaks into it it’s a low-risk item and thus you can simply USB stick reload it and get back to normality.

If you are on a PC with highly sensitive data then you probably shouldn’t be doing this level of hacking/modding to your windows 10 box. Please consider purchasing an Xbox One controller and receiver if you are uncomfortable with hacking and want a controller that can integrate seamlessly into windows 10.

Public Driver Signature.

Going through the grueling process of getting the XBCD driver publicly certified underneath windows 10 is one option available to avoid going through all of the hacking with “Test Mode”. Also, allowing the driver to install just like windows XP and 7.

S, can you make a publicly signed version of this driver for us?

Costs money to do it. The last time I checked it costs around $200(usd)/yr to maintain a valid domain signature to assign to drivers that are personally made. The team the developed XBCD is all open source. So if someone wants to get the public certification to do it by all means! It would save me from having to write out all of this!

Devices compatible with XBCD.

Pulling directly from the xbcd.inf file is a list of vendor ID’s you may find within device manager that will verify that your controller does indeed work with the XBCD driver. Keep in mind these are only the drivers detected. If you have a controller not listed here you can manually install but success may not be guaranteed. For example, my Pelican Wireless Controllers and my Pump-It-Up Dance Pads for Xbox I had to manual install and it works despite not being on the drivers listing.

Original Xbox Controller for XBCD

Vendor/Product ID Control Type Description
USB \VID_044F&PID_0F07 GamePad Controller Thrustmaster Controller
USB \VID_045E&PID_0202 GamePad Controller Microsoft Xbox Controller
USB \VID_045E&PID_0285 GamePad Controller Microsoft Xbox Controller S
USB \VID_045E&PID_0287 GamePad Controlelr Microsoft Xbox Controller S
USB \VID_045E&PID_0289 GamePad Controller Microsoft Xbox Controller S
USB \VID_046D&PID_CA8A GamePad Controller Logitech Cordless Precision
USB \VID_046D&PID_CA88 GamePad Controller Logitech Thunderpad
USB \VID_05FE&PID_3030 GamePad Controller Chic Controller
USB \VID_05FE&PID_3031 GamePad Controller Chic Controller
USB \VID_06A3&PID_0201 GamePad Controller Saitek Adrenalin
USB \VID_0738&PID_4516 GamePad Controller MadCatz 4516
USB \VID_0738&PID_4520 GamePad Controller MadCatz Control Pad Pro
USB \VID_0738&PID_4526 GamePad Controller MadCatz 4526
USB \VID_0738&PID_4536 GamePad Controller MadCatz Microcon Xbox Controller
USB \VID_0738&PID_4556 GamePad Controller MadCatz Lynx Wireless Controller
USB \VID_0738&PID_4586 GamePad Controller MadCatz MicroCon Wireless Controller
USB \VID_0738&PID_4588 GamePad Controller MadCatz Blaster
USB \VID_0C12&PID_0005 GamePad Controller Intec wireless
USB \VID_0C12&PID_8801 GamePad Controller Nyko Xbox Controller
USB \VID_0C12&PID_8802 GamePad Controller Nyko Air Flow
USB \VID_0C12&PID_880A GamePad Controller Nyko Xbox Controller
USB \VID_0E4C&PID_3510 GamePad Controller Radica Gamester
USB \VID_0E6F&PID_0008 GamePad Controller After Glow Pro Controller
USB \VID_0F30&PID_0202 GamePad Controller Big Ben XS Xbox Controller
USB \VID_FFFF&PID_FFFF GamePad Controller PowerWave Xbox Controller
USB \VID_044F&PID_0F00 Steering Wheel Thrustmaster Wheel
USB \VID_044F&PID_0F03 Steering Wheel Thrustmaster Wheel
USB \VID_044F&PID_0F10 Steering Wheel Thrustmaster Modena GT
USB \VID_062A&PID_0033 Steering Wheel Competition Pro Steering Wheel
USB \VID_06A3&PID_0200 Steering Wheel Saitek Racingwheel
USB \VID_0E8F&PID_0201 Steering Wheel Gamexpert PS2/GC/Xbox Steering Wheel
USB \VID_3767&PID_0101 Steering Wheel Fanatec Speedster 3 Forceshock

Xbox 360 Controllers for XBCD

Vendor/Product ID Control Type Description
Vendor/Product ID Control Type Description
USB \VID_045E&PID_028E GamePad Controller Microsoft Xbox 360 Controller
USB \VID_046D&PID_C242 GamePad Controller Logitech Chillstream
USB \VID_06A3&PID_F51A GamePad Controller Saitek P3600
USB \VID_0738&PID_4716 GamePad Controller Madcatz Xbox 360 Controller
USB \VID_0738&PID_4718 Stick Controler MadCatz Street Fighter IV Fight Stick
USB \VID_0738&PID_4726 GamePad Controller MadCatz Pro for Xbox 360
USB \VID_0738&PID_4728 Stick Controller MadCatz Street Fighter IV
USB \VID_0738&PID_4736 GamePad Controller MadCatz 360 MicroCon
USB \VID_0738&PID_4738 Stick Controller MadCatz Arcade Gamestick (Street Fighter IV Fightstick TE)
USB \VID_0738&PID_B738 Stick Controller Madcatz Arcade Fightstick Tournament edition.
USB \VID_0738&PID_BEEF GamePad Controller Joytech NEO Se Advanced
USB \VID_0E6F&PID_0201 GamePad Controller Pelican XSZ Wired Controller (Model #PL-3601)
USB \VID_0F0D&PID_000A Stick Controller HORI DOA4 Stick
USB \VID_0F0D&PID_000C Stick Controller HORI Pad EX Turbo
USB \VID_0F0D&PID_000D Stick Controller HORI EX2 Fighter Stick
USB \VID_162E&PID_BEEF GamePad Controller Joytech SE for 360
USB \VID_1BAD&PID_F016 GamePad Controller Mad Catz Xbox 360 GamePad
USB \VID_1BAD&PID_F501 Stick USB \VID_1BAD & PID_F900 Controller HORI Pad EX2 Turbo
USB \VID_1BAD&PID_F502 Stick Controller Hori HRAP VX-SA
USB \VID_1BAD&PID_F900 GamePad Controller Afterglow AX.1 Wired controller
USB \VID_046D&PID_CAA3 Steering Wheel Logitech DriveFX Wheel
USB \VID_1430&PID_4748 Guitar Controller RedOctane X-plorer Guitar
USB \VID_0738&PID_4540 StepPad Controllers MadCatz Beat Pad (w/ Handle)
USB \VID_0738&PID_45FF StepPad Controllers MadCatz Beat Pad (w/ Handle)
USB \VID_0738&PID_4740 StepPad Controllers MadCatz Beat Pad 360
USB \VID_0738&PID_4743 StepPad Controllers MadCatz Beat Pad Pro
USB \VID_0738&PID_6040 StepPad Controllers MadCatz Beat Pad Pro
USB \VID_0C12&PID_8809 StepPad Controllers RedOctane Ignition Pad
USB \VID_12AB&PID_0004 StepPad Controllers Konami DDR Pad
USB \VID_12AB&PID_8809 StepPad Controlelrs Konami DDR Pad

Unsupported devices by XBCD

Vendor/Product ID Control Type Description
USB \Vid_045E&Pid_0719 GamePad Controller Microsoft Xbox 360 Wireless Controller

You can simply visit the blog about wireless controllers if you have a problem with the wireless Xbox 360 Controllers.

Related blogs:

This may be helpful for those looking for other solutions to gaming or for those wondering why would you even get gaming controllers to work on the PC in the first place.

Looking for games to play with your controller? Click here!
Have an Xbox 360 wireless controller and want to get it working? for 5-10USD you can. Click here.
Want to see the original documentation on how to XBCD working? Click here.

Final thoughts.

It’s still amazing that you can get controllers from almost 15-16 years ago operating on the latest operating system and computers. It’s a perfect solution for those who are looking for cheap controllers. You can find these controllers at various thrift stores and other surplus stores ranging from $1-5 USD. The value can of course change as time moves on and these controllers start to build collectors value. You can also mess with people by showing them the original Xbox controller named “The Duke” because you needed man-hands to use it!:)

I compiled this tutorial because we was getting tired searching through dead end forums over and over again. I hope you find it useful.

Until then, have fun, server protect you.


131 thoughts on “XBCD – Original Xbox Controllers with Win10-8

  1. i followed the steps but i cnt install from disk
    ”the folder you specified doesn’t contain driver software for your device.Select a folder that contains your driver software.”

  2. whenever i try to update the driver software, windows says it encounters a problem because the “hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.” i have a Lenovo running 64x Windows 10. im new to this stuff so if anyone could help that would be great.

    • I guess my first question is are you in test mode? Did you run the disable.bat file and restarted your system? The drivers will not load if you don’t turn off some of the security features of windows 10. If the disable.bat script is not working then you may have an issue like others have posted where your harddrive is locked with UFEI secure boot like some of the Dell and HP units out there. You can visit this YouTube link on how to disable UEFI secure booting.

  3. Please help me, i have this problem:
    specified folder does not contain any driver software compatible with the device. If it contains a controller , check that is designed to work with Windows based systems

  4. How much money? I wouldn’t mind putting money into a Kickstarter for you.

    PS: Thanks so fucking much for this. You are a saviour.

    • You should be able to re-run the uwd.exe and instead of the install button present there will be an ‘uninstall’ button there for you to restore your watermark. The program will then undo the register as well as restore the two system files within windows 10.

  5. everytime I try to open your shortcut it gives me an error sound… cant find the xbcd setup utility, i could only find the x360ce

    • sorry i forgot to run as admin,,, how stupid of me..
      now for the next part
      how do i use my wired xbox 360 controller with it?

      • again, I figured things out, thx to your instruction and boot windows with disabled driver signature enforcement, I was able to use the driver on my xbox 360 controller and get it to work like a charm. thx man, you’re a hero.
        now I can finally invert the x axis on GTA V, yep that’s right, it’s been like 24 hours searching for a way to get the x axis inverted in GTA V, and you gave me just what I need, can’t thank you enough man. you’re a hero.

  6. Hi thx for this amazing work !

    But When I’m trying to update manually the driver, Windows tell me that there is arleady the best driver for the controller. The controller doesn’t appear as an unknow device….

    • What controller are you using? For example, If you’re using an Xbox 360 wired controller or a Konami DDR Dance Pad for Dance Dance Revolution Universe for Xbox 360. Then there may be a little bit of driver fighting as Windows 10 will try to pull default drivers off of the update server. You can easily override this by selecting to choose a driver manually when you update your driver and then looking for the driver location with “Have Disk”.

      Also what is the device description in device manager? If it already has the “XBCD Xbox Controller” installed then you should be alright and it’s just a matter of seeing if your controller is out there via control panel.

  7. Hello there! I did everything as in the tutorial, but when i connect my xbox one wired controller, it doesn´t install as an unknown device. So at the end, it always updates to the xbox controller default driver, even if i try to install xbcd driver manually. Any way i can get around that?

    • Your the first user I’ve heard trying to use the XBCD driver on an Xbox One controller. So not even I know if you can force a driver similar to a wired xbox 360 wired controller. With the 360 wired you have to wait for windows to install the default driver, and afterwards run the disable script and then manually pick the XBCD controller driver by doing the manual installation and ‘have disk’ routine.

      I suppose I’m going to have to actually get an Xbox One controller myself and see if it can be done!:)

  8. Yeah, i know it´s awkward, but since not all games provide an inverse X axis option (yeah, that´s the way im used to play… i know it´s weird), i had to hack my own original controller to get the reverse X axis done with a x360ce simulator. I actually managed to install the XBCD driver a couple of times, but every once in a while, a new windows uptade scrambles it back to the Xbox Controller driver. I was looking for a definitive solution, but i guess i´ll just have to keep looking… I appreciate any help anyways. Thanks a lot!

    • Nah, it’s not weird. in fact one of the commenters use XBCD for just that. Inverted axis is almost like a blast from the past to me. dating back to the Nintendo with James Bond. Also default key-layout for Unreal (before the tournaments) was inverted axis on the mouse. Anyhow, got an Xbox One controller on order along with the wireless PC dongle so i can test in both wired and wireless to see what works and what doesn’t on the Xbox One. If I find anyway of getting XBCD going I’ll update the post and let you know.

      • That’s awesome! Thanks a lot! The x360ce simulator works pretty good, actually, for the inverted X axis situation. But without the XBCD driver, the 2 triggers won’t work separetely. So i fix one problem and get a new one. That’s why i need both simulator and driver working fine. Untill microsoft comes up with a controller remapping update for pc, i need all this big mess to play and actually have fun, hehe. I appreciate any effort on solving this 0,5% of the worldwide game players issue, haha. We’re weird, but we’re good people.

      • Any news? I tried reseting and deactivating driver sign enforcement, i actually managed to run the installer and install the setup, but when i plug the controller, it just downloads the official xbox driver, and there´s no way i can manually update it to the XBCD driver. I have no ideia how i got it to work previously, it was a big fucking luck.

        • Sorry about not getting back right away here. I am having some issues with getting it going to. Mostly with the way Windows 10 treats the Xbox Controller special versus every other joystick device you hook up to the system. Especially with how insistent it is on using its Xbox driver and using the Xbox Accessories tool off of marketplace. When forcing the driver on my side I keep getting blue screened. It really hates the XBCD.sys file when replacing the Xinput interface. This may be a dead end on this one due to what Microsoft decided to do with making the controller easier to install on windows 10.

  9. i have extra blue wire in the cable
    i done all steps but its not working
    its tell me
    windows found driver software for your device but encoutered an error while attempting to install it

    • Well, first thing I would check is to see if you got a hardware ID in device manager. If it’s all question marks then perhaps the data cable may be that blue lead. you can make a multi-meter to the other side of the connector that you cut off to see where that blue lead runs off to. Also what kind of controller is it? I never seen one with a blue cable inside before.

  10. UWD should not be used in any circumstance. Breaks search in Windows 8\10, leads to many Windows update problems, and a few other issues.

    • UWD can be run again to re-enable the watermark and continue with updates whenever necessary. I don’t like using it. But no one including Microsoft is providing a better solution towards keeping test mode quiet.

      Also if you have a solution to pass the drivers in windows 64 as a trusted driver I along with many others would be happy to hear. It would make this blog entry a lot shorter.:)

    • I just want to give an update about the whole UWD thing. I decided to reload my test PC station with a base image of 10. turned on UWD and let it go through its service pack update and all of the others through windows updates. Nothing locked or didn’t install property. Also, windows search which I never really used because Cortana is just legalized mal-ware that monitors you. But in this scenario I turned it on as well and was using it with UWD enabled and everything was working fine.

      So, I’m not saying UWD is great. But there could be a lot of different variables behind UWD and the failures of updates and search. Just as one example, if people are using it as a way to subvert paying for a license key. Then they kind of get what they deserve. Hiding the watermark does not magically give full activation. Also as stated in my blog. This procedure is not for highly sensitive windows 10 environments because you are knocking down many levels of security to get the XBCD driver installed.

  11. Hey man, thanks for the work, but i have 2 problems
    1. When i plug the dance pad (it’s a MadCatz Beat Pad [w/ Handle]) Windows tell me that there is already the best driver for the controller (Says: “hid-compliant game controller”)
    2. When i tried to override the driver to a “XBCD Xbox Foot Pad”. My PC crash with error “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” (Error code:0x1000007e)

    • I don’t have a matcatz pad. best i can do is try to hook up the xbox 360 DDR:universe pad which should detect and install it as a generic xbox 360 controller and i can see if i can flip with XBCD on that.

    • This may exceed what this blog is originally intended to do. But device manager should open regardless if DISABLE_INTEGRITY_CHECKS is marked or not. If ctrl+X and device manager in power user mode doesn’t work. I’d try some other commands like the task manager. If for some reason you are locked out a bunch of systems then there may be some virus activity going on. As I have no idea on how virus or firewall protection this is the best I can reply with.

  12. Hi. The download link for the .zip containing XBCD and the modified drivers takes me to the broken links/anti-hotlinking page, so I can’t use this guide at all because of it. Could you please put it on the Downloads page?

    I tried copying the commands stated in the disable.bat myself, but I must have botched something because the driver installation still failed.

    • hot-linking protection got messed up due to the upcoming implementation of SSL. Apologies for that. You should be able to download it now. I verified this by going through a netherlands proxy via ToR. The download link in this blog should work fine now.

      • Thank you. It works perfectly now.
        I may have a much-easier-to-set-up PS3 controller for most games, but the way a good old bulky Duke places the Black/White buttons makes it perfect for Nintendo 64 games (Y/B/Bl/Wh = C-left/C-down/C-right/C-up) and 6-button fighters (X/Y/Wh = LP/MP/HP, A/B/Bl = LK/MK/HK), not to mention Sega Dreamcast games since the Duke was based on the DC controller in the first place. So I appreciate having it as an option.

        It’s still strange that Microsoft would go to such lengths to block something that they made themselves, though.

        • Great to hear it’s working out for you!

          As for the Microsoft thing. “Planned Obsolescence” is the best way to describe it. Microsoft could have later on made a USB adapter for the original xbox controllers and just slip-streamed the drivers into the OS. They could’ve sold Xbox 360 receivers individually instead of “PC_bundling” them with a controller but instead they let the Chinese market run with it. Hell, they could’ve even made Xbox360 controllers work with the Xbox One to boost the sales for party games . But that’s simply not the Microsoft way.

          Having all of Microsoft’s controllers I will say the Xbox One is the first controller I’ve had from them that actually has a worthy D-Pad to go against the Playstation. Took them 20+ years! But they did it finally! So the Xbox One Elite controller does stand on its own for people who just have cash to burn. But for me I won’t cry when my nephews destroy a $2.99 Xbox “S”Controller I got from Goodwill.:)

  13. Tanks for this tutorial! anyone knows how i can make vibrate the control? or i do some wrong installing the drivers? (if you see,my english its not very good,but a make it xD)

  14. Hi S! Im using the same pc for work and gaming. Can i just enable (using the dat file) after playing and disable it again if i want play? you know, for the security thingy… Thanks! Great tut!

    • Yes, it’s why I put the enable.bat file in there. In case any user wants to revert any settings and bring driver signature enforcement back to windows 10. Understand that if you do run enable.bat the XBCD driver will remained disabled in device manager until you run disable.bat again.

      Thanks for checking out my blog!

  15. While attempting to select the driver I’m getting an error that states “Windows found driver software for your device but encountered an error while attempting to install it. The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.” I can’t seem to find a way around it. Thoughts? (I have a screen shot if you need it.)

    • If you’re installing this on a windows 10 64-bit machine then you may have missed a step about disabling integrity checking and enabling test mode. The reason why windows 10 is saying this is the version number had to be modified in the xbcd .inf file in order for windows 10 to see it properly. So it is right! It has been tampered with. But not in any malicious fashion like windows 10 wants you to believe.

  16. Hi man. Awesome work putting all this information in one easy to find place. I’ve been trying to get my original controllers working on Win10 for ages, and finally now I can. Only one problem I’m having – In games like Rocket League or Ultimate Chicken Horse, they automatically detect when an Xbox 360 controller is connected to the PC and switch to controller mode, but with this controller I can’t use it in these games (really the only ones I use a controller for) as it doesn’t register as “Controller 1” for example, it’s just another gamepad as far as windows is concerned and I can’t seem to get it to register in these games. Much appreciated!!!

    • This is your second time warning us. I don’t want to sound like a dick here. But we need you to provide legitimate data to back your claim. Otherwise its as baseless of an accusation as me saying “Windows 10 in itself is a major problem.” I’ve placed the potential disclaimers on this article. It really is up to a user to decide and not some corporation.

      Also, if you have a method of removing the test mode watermark while integrity checking is disabled I would be more then happy to hear it and if it works we will happily strike UWD.exe from this article. Some people consider the “Test Mode” watermark an annoyance and a solution must be provided. d

  17. Hi S, I haven’t try this yet but I have a question, If my computer will always be on test mode, is there any problem? any program that shouldn’t work properly? Sorry for my bad english

    • Programs should operate just fine in test mode. And always understand that you can run the enable.bat script to turn test mode off. It’s a layer of security windows installed to keep malicious drivers from getting into your operating system. Windows XP/7 does not have this layer which is why I had to write this article up on how to disable it.

  18. i did all steps and in the device manger > my xbox controller name is (xbcd xbox controoler) but in devices and printer the name is( unknown usb device configuration descriptor request failde and my xbox s controller not work help please

    • Device descriptor request failed – This error is caused from your USB port not being able to read what kind or type of controller chip that is inside of your Xbox controller. Now this could be a simple problem with the wiring of the controller where the data leads are inversed. Or it could be more serious where the controller itself lost its programming. You can try other ports to see if it clears up. If your controller has a detachable cable you can replace that since I know some of these xbox controllers are getting up there in age. But that’s about it.

  19. now it work 5 second only(when connect usb to pc it work 5 second only) and donot work again i must unplug usb and reconnect it to pc. after that work again about 5 second only

  20. i did all steps and my controller work fine but for 3 minute only and stop again. i must disconnect the controller and then reconnect. what is the problem. i have win 10 64 bit and my controller is the duke

  21. Hello.
    I detected an error
    USB\VID_046D&PID_CA84 ; Logitech Cordless Precision
    USB\VID_046D&PID_CA8A ; Logitech Cordless Precision

    Please correct it
    Regards from Poland !! :)

  22. Thanks for the tutorial. I got it working in the XBCD setup utility like you said. However, I could not get any game to recognize my Big Duke as an Xbox 360 controller. Even with 360ce, this was a bust. Looks great in the setup program, but doesn’t work anywhere else.

    • I’m starting to see the problem. For some reason the Xinput still works for older games like Jamestown and emulators. But when you go to newer games that use the directx inputs for 360 controllers it dies. And at one point x360ce used to work! But now in windows 10 it does not even when downloading the latest version from their site. So part of the x360ce is broken now instead of the core driver itself. Hopefully a newer version of x360ce will correct this issue.

  23. Came here to say the same Barlowe, just installed it, and it works great, except it isn’t recognized as a 360 pad. I guess I could map keys to it in xpadder, but then I’d lose analog movement, which is why I use a controller in the first place. Driving and flying with a kb/m is tough.

    S, this tutorial was great, thanks so much. No way I ever would have pulled it off without the clear step by step directions with pictures included. People like you amaze me, you spend all this time helping anonymous people out for basically no personal gain, again thanks so much.

    Hopefully a new version of whatever x360ce is comes out and fixes it so that my Duke can be used as a 360 controller. It’s still pretty sweet now, thanks again for the tutorial.

    Random side note, if you don’t want to do the wiring stuff in the first part of the tutorial, the converter sold on amazon does indeed work with these steps, I used it to do so. This is the page https://www.amazon.com/gp/product/B000RT2868/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1. If the link eventually breaks, it’s listed as Xbox Controller to PC USB Adapter Cable.

    • Hello there!

      Thanks for the update about the cables. I have included the link to your Amazon as well as Ebay into the primary blog entry for those who want to buy the cable. I still have to play with it a little more because i’m wondering if the XBCD utility is interfering with the x360ce tool for windows 10. Of course this will mean doing a manual install of the driver and a re-write of this entry. If it works or someone has a better way I’ll be more the happy to spend the time re-writting it.

      I just want to help people get more life out of controllers. The hardware is perfectly good. It just needs software to back it all up!:)

      Thanks for checking out my blog and take care!

      – S

  24. Nevermind Xpadder won’t recognize it either, and games won’t detect the buttons so I can’t program the buttons and sticks manually. Still this is a great tutorial, hopefully whatever the problem is gets fixed soon.

  25. Thx for great tutor!

    I have a small issue: triggers are not working – I can’t make them work in x360ce – have tried different axles, recording – no luck.
    Any ideas how to fix?

      • yeah, with windows 10 the XBCD sort of dominates all leaving the x360ce program out.. I kind of wished it worked opposite because then we can get some xinput games working again.

  26. How do I get Steam Big Picture working with XBCD? Because x360ce dosen’t work with steam anymore due to it replacing xinput_1_3.dll every time it starts. It seems to me that the directinput is a bit broken in some applications like the after mentioned Steam and stuff like World Of Joysticks(btw have you ever heard of this? Its basically x360ce system-wide solution that emulates an actual xbox360 controller) and it dosen’t work there either
    I’m using XBCD to just separate the triggers on my 360 controller for old games, it works great with games such as Need For Speed Undergound and some others however I can’t just get it working on these other programs :(
    Any solutions?

  27. Thank you for the guide. Everything is working–in the setup utility. I’m a bit confused, as I’m trying to use XBCD 360 Emu with Braid, which allegedly uses xinput. I thought that “The old XInput system is working however only older games will work with the old standard” meant that this would work?

    I then read the comments, where you say “I kind of wished it worked opposite because then we can get some xinput games working again”, which seems to tell a different story. Do xinput games not work?

    • apologies for the confusion. there’s actually different version of the XInput.dll. You have the original xinput.dll which was pre-directx. A lot of your older games such as Jamestown, MAME, and other emulators used this because even though it was a harder DLL hook to implement into your program that your program would literally work with every windows OS dating back to windows 95. Microsoft then decided to roll updates into directX which is where you can XInput_1.1.dll through XInput.1.3.dll and these made it a lot easier for developers to drag and drop input support into their games like anything made with unity without really typing a single line of code. the program x360ce is designed to take very old or generic joysticks that do not use the modern xinput drivers and bridge them together. however, the XBCD utility gets in the way of later versions of x360ce which is why it’s partially broken on windows 10 now.

      • Thank you for the reply. I provided an email address when commenting but I never got notified so I didn’t read it until months later.

        I think I don’t understand still though. XBCD gets in the way of x360ce only for games with pre-directx xinput.dll? Or just a random subset of xinput games, old and new? Or completely in the way so that we can’t use XBCD for any xinput games?

        And all the mentions of x360ce in the comments… does x360ce.exe need to be run at all? It’s not mentioned in the tutorial. Is it indicative of anything that x360ce.exe recognizes my original controller or is x360ce still just as broken? That utility says to “Run this program from game executable directory”. Should this be ignored since it comes bundled with XBCD and I’m using “XBCD 360 Emu”? Should it be followed?

        I think a simple diagram would explain most of it. I’d draw one if I could just understand what’s going on.

        Perhaps in my case it’s easier to just put the controller back in its drawer :-)

        • XBCD and x360ce operate a little differently from each other. Both are joystick mapping utilities. XBCD however maps the joystick buttons directly within the windows registry (hence the requirement to run this program in administration mode) and x360ce takes a different approach by injecting DLL files into the root folders of games in order to take control of the joystick mapping (less evasive and does not require admin-rights.) You tend to hear x360ce a lot because the beauty of that utility is it’s supposed to emulate an Xbox 360 controller for games that are looking for the more advanced input drivers. XBCD, although it has an option for “XBCD 360 Emu” simply maps your controllers to the right analog and digital buttons that most older games expect to see an Xbox controller.

          To answer your question “Does x360ce.exe need to be run at all?” If your game is totally totally fine without running it then you don’t need it. Since each developer compiles their game in their own way x360ce.exe should be viewed like a supplemental program in case you have a game which is refusing to see your controller or expecting an Xbox 360 controller explicitly. There’s a few steam games that I have where even using x360ce it still rejects seeing the controller. it’s annoying we know. But since we like to run emulators, Stepmania and older games it works out for me.

  28. I can’t get this to work for rocket league. the buttons all work fine in xbcd or the windows test utility, but nothing in rocket league

  29. Okay, so now I figured it out, its working, but the Left trigger activates the steam community whenever i’m in game. I can’t seem to disable it

  30. I was able to install the driver without having to use Test Mode, by booting Windows while driver signature enforcement was disabled, as described here: https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ (Option 2)

    I rebooted using the Advanced Boot Option, ran XBCD_Installer_0.2.7.exe, let it install, then used the utility to set the triggers to be analog. I don’t remember if I used your download, I might have used this one: http://vba-m.com/forum/thread-668.html

    I had to fiddle a bit with x360ce, setting the triggers to be inverted half axises and whatnot, but it works great! It’s even survived the Windows Creator’s Update. Thanks for the guide!

    • Hey thanks for the input. This binary seems a little different from the one I got from the XBCD site years ago so let me try it out. If it works I will update the blog entry and host the binary here so people don’t have to go through that ad.fly nonsense.


      I tested out the exe on that forum and it’s interesting. even though the driver ID matches perfectly this file negates the need to port certificates into windows. and i can remove the test signature part of the enable/disable.bat file leaving the disable-integrity-check active. and since we do not have the annoying test-mode background anymore UWD.exe is no long nessecary. Also, the latest version of xb360ce works on windows 10. I still have some compatibility issues with certain games such as broforce. but it’s at least a step in the right direction towards simplifying the install process.

      I will repackage the zip file in the next few days and update this entry to get rid of those steps.

  31. Mil gracias, me sirvio el driver para un volante de xbox normal en una computadora con windows 8, estaba batallando mucho para que el volante funcionara en mi pc, gracias nuevamente

  32. genial muchas gracias por compartir, espero poder traducir toda la informacion y renovar mi control que he estado utilizado con una version anterior de tu software.Gracias y saludos desde colombia

  33. Hello, Probably its too late. But, i have everthing done but when I start the XBCD Steup Utility my controller doenst appear. Hellp :C

    • The XBCD utility needs to run as administrator rights. It needs to access your device manager in a more direct fashion then windows 10 likes to do. Of course it’s a good idea to check to see if your controller is installed correctly in device manager and also to run the “joy.cpl” program and see if your joystick is at least detected and working with the stock joystick utility windows provides. Hope that helps start with troubleshooting with your joystick.

      – S

  34. Hey S-Config,
    First of all I just wanna say thank you for taking the time to make a tutorial on something that may seem kind of antiquated. I have heard say that the Xbox Controller F(Fatty) was one of the worst designs for a controller ever, but, I’ve always disagreed. I love the way it feels heavy and substantial and the triggers have a really stiff pull to them. I do think the Black and White buttons could’ve been in a better location but, hey, i made it work for 10 years and now I want to use it on my PC games.
    So, my question is this, I’ve watched the tutorial video and followed it to a T. After I run the “disable” batch file and reboot I log back in and go into DM and manually input the xbcd.inf. But, I still get the warning about it being an unsigned driver. Could there be something I have to change in administrator’s rights to get this to work properly?


    • Depending on how strict the security is on your windows 10 box even using powershell commands to force admin mode which is what disable.bat may not be enough. Found this out on a IBM laptop a few weeks ago.

      Follow the instructions in this blog titled:

      “Script fails and still cannot install drivers. Disabling integrity checking manually.”

      and for some reason using the GUI mode disabled integrity checking long enough for me to install the drivers.

      And I use the Duke controller more-so then the “S” controller. So totally get what you’re saying.

      anyhow. good luck on getting your controller installed!

      – S

  35. Man this is a great guide !!
    I just resurrected an old xbox controller to make an analogue handbrake for my racing sim project.
    Fantastic many many thanks for spending your time with this.

  36. When I set up my controller 3 years ago it took me about 4 hours of troubleshooting to figure it out. Thanks to this guide it only took me 10 minutes. Thank you so much!

  37. When I try to install the drivers I got a window saying
    “Windows found driver software for your device but encountered an error while attempting to install it.
    XBCD Xbox Controller
    Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.(Code 39)”

      • My bad, I’m using an Original Xbox Controller S. The hardware ID is USB\VID_045E&PID_0289 and I am running Windows 10 Home 64-bit. Thanks for responding so quickly.

        • Okay, I have not tried this yet to replicate the problem that you’re having. But it seems like Windows 10 is totally blocking your driver which a feature in windows 10 known as “Secure Boot” is capable of generating this problem.

          I think this whole secure boot business comes from dells and HP’s where they load the system themselves instead of like what I did where I started from a stock USB load of windows 10.

          https://www.youtube.com/watch?v=WWGlJVV3djw – there’s a video online on how to deal with disabling secure boot.

          and then afterwards you can follow my instructions on turning on test mode and installing the joysticks.

          I shall enable secure boot on my test box to see if i can replicate the error you are having.

          • I do indeed have a Dell (Alienware). I attempted that fix with no change in the driver status from before I disabled secure boot. Device manager does list my controller as XBCD Xbox Controller but has it in an error state.

            The device status in addition to the error mentioned above says Object Name not found.

            “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

            Object Name not found.”

            Thanks for the assistance!

          • Okay, before we start digging into the registry like this article suggests about code 39 errors. There’s one more thing you can try. I updated this article a while back because people didn’t like keeping test signing on for unauthorized drivers and also using questionable programs like the universal watermark disable tool to hide the ‘windows 10 test signing’ watermark at the lower right-hand corner. I revised the tutorial in the hopes of eliminating that step however it may not have been effective in everyones case.

            https://www.s-config.com/archived-xbcd-old-instructions-win10-8/ – in the original XBCD blog entry which covers test signature and also has a different executable then the current blog. But if you wish to try out what the script in the old blog does. simply open a command prompt in admin mode and type in the following:

            bcdedit -set TESTSIGNING ON

            Then reboot your computer. You will know it worked if you see text in the corner of your desktop saying “Test Mode – Windows 10 – Build XXXX”

            The only thing that worries me is although strict enforcement of drivers produces a code 39 error. the reason code give an error stating “the drivers are not signed” and not “object not found”.

      • I successfully got into test mode (watermark and such) but it didn’t change the problem, also followed the instructions on the first link you gave for code 39 errors in the registry but that didn’t work. I didn’t have either the upper or lower filters entries he suggested be deleted. One of the comments he left on that post suggested that it could be the usb port somebody was having trouble with, so just for giggles I did move the controller to the other usb plug, no dice. For the same reason I swapped controllers but that also had no impact.

        • I am also on an Alienware computer. I couldn’t disable secure boot(I got an error message then the pc would restart), and I didn’t have upper or lower filters. Could the hardware itself be the problem?

          • I don’t think the hardware itself is the problem. Because it is identifying in device manager. The XBCD driver knows exactly what to do. But there is something going on where it knocks out certain files from entering your system32 folder during installation. Usually if it’s a virus checker or firewall program doing this they tend to be very vocal towards the user letting you know what’s going on. It could be a windows patch causing this for all I know but if that was the case my fully updated test unit would be exhibiting the same behaviors that you are experiencing. The code 39 error is hard for me to troubleshoot since so far I’ve not been able to replicate this problem with the two windows 10 pc’s I use for my tutorials. I don’t want to say ‘reload the operating system’ as that’s really excessive for just a joystick. But I’m also running out of ideas as to what is causing this code 39 error as well.

        • I know this sounds trivial for me to ask but it has to be asked. During each of these steps such as swapping ports, going to test mode, etc. You have uninstalled the XBCD controller from device manager and checked the box to remove any system files as well right? Because say you disable your secure boot without reloading the drivers. The drivers will always state code 39 because something within your OS has blocked a core file from entering the system32 folder for XBCD to do its job.

          After you uninstall XBCD and remove it from device manager pass the following command:

          pnputil -e

          See if there is any inf files from XBCD or Redcl0ud that exist in your system and delete those inf files as well just to ensure that your OS is not picking up any faulty drivers from cache.

          Getting beyond this I hate to say that I’m totally out of ideas on what to do next. And I don’t want to say ‘reload the OS’ especially over something as minimal as an old joystick. I’ve reloaded one of my test stations and let it update all of its patches and drivers so I have ruled out anything coming down from Microsoft about this one. your code 39 error is specific as if there’s something that’s straight up blocking the driver from placing files where they should which sounds like something a virus checker would do. But in general virus checkers are rather vocal when they do something like this. They want to show the user that its doing something about a file it doesn’t know. So although it doesn’t completely rule it out it’s also highly unlikely as well.

          If someone else has this problem and got it solved I’d like to hear it.

          • I just want to say I really appreciate that you haven’t been treating me like an idiot this entire time, but you really should have. No I had not been doing any of that, because I had no clue what the problem actually was so it never occurred to me that I should.

            Anyway. So I uninstalled the drivers (selected the box), checked with pnputil as instructed (it was clean), then rebooted and attempted to reinstall the driver. But now it refuses to install the drivers. I am still in test mode, secure boot is still disabled, I get the following message when it is directed at the xbcd driver: Windows found a driver but encountered an error… “The third-party INF does not contain digital signature information.”

            Yay new problem?

          • I attempt to treat everyone the way I expect to be treated back. So no worries there. Installing drivers can be a frustrating process and it’s really easy to miss a few steps or have things simply not work as intended. We’ve all been there! In fact I’m still fighting such a thing with a Wacom tablet for windows 10! :)

            And the new error you got is one this blog entry can help with! This happens if your OS refuses to accept the commands:

            bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
            bcdedit -set nointegritychecks ON

            On reboot. To which you’ll have to manually disable integrity checking by holding down the shift key can click the power button to restart your computer. If you search for:

            Script fails and still cannot install drivers. Disabling integrity checking manually.

            On this blog entry it will take you to all of the screen shots of what you need to do. It should disable integrity checking long enough for you to attempt to install the driver.

            Let me know if that code 39 error clears after reinstalling the driver!

          • So I did the driver signing disable and didn’t even get a chance to uninstall and reinstall the drivers it just loaded them up striaght away and the controller works now!

            So the question now is 1. will this survive a normal reboot, 2. will this work if I exit test mode. 3. will this still work if I turn secure boot back on.

            I will give those a test to see if now that it has accepted the driver it will stick. At the very least I would like to not have the watermark.

            Thanks so much!

          • It should survive a normal reboot. The current blogs drivers have been tested so that after you disable integrity checking you don’t need to keep it disabled. The only time you may have to repeat this process is if you get a different controller that triggers a new hardware ID such as a Duke or a Matcatz/3rd party controller.

            To turn off the watermark and enable test signing just do the reverse bcedit.

            bcdedit -set TESTSIGNING OFF

            and reboot.

            Anyhow. hope it all works out for you and happy gaming!

          • I tried enabling test signing the command prompt returned an error “This value is protected by the secure boot policy and can’t be modified or deleted” When I disable secure boot windows refuses to start up. I wasn’t able to find any other cases of this. I’m going to stop trying with this machine and try a different one when I can.

            I really appreciate how helpful and concise you have been. Thank you.

          • Okay, you were saying that you were encountering errors when you attempted to disable your secure boot policy. Perhaps this is something I should record for another blog since I have a few dells and HP units that play with UEFI bios settings. But when you do an advanced restart > troubleshoot > UEFI Secure boot > and press f10 to jump to BIOS to disable the secure boot settings. what does your windows tell you after disabling secure boot mode in the bios? Getting rid of secure boot is an important step when working with older drivers such as XBCD because while it’s enabled it will stop you every step of the way.

          • When actually selecting “disable” I get a warning “Attention changing this setting may prevent your your operating system from booting.”
            After saving and rebooting windows tries to load, fails, and I receive a blue screen. “Your PC ran into a problem and needs to restart” along with the stop code: “INACCESSIBLE_BOOT_DEVICE” This repeats 3 times before windows enters “Automatic repair mode”
            When this happens I can enable secure boot and boot the computer normally.

          • Usually the symptoms your describing deal with something not being set properly in the BIOS of your machine. That after you disable UEFI that if it doesn’t throw you into the bios of your machine (Dells I think you need to press either f2 or f10 on the startup screen it changes sometimes) and then you go into advanced mode and disable your Security. i’ll show you an example on a dell Optiplex because my XE2 is weird. My BIOS may be a little different. to disable/enable UEFI Secure Book.

            Once you got the blue screen bios:

            Security > Secure Boot Configuration >
            Press F10 to confirm that you want to go into this menu.
            Set Secure Boot to: Disable
            If you have this option, Set Legacy Support to: Enable.
            Arrow back over to Main menu.
            Arrow down to : Save changes and exit.
            Select Yes to confirm your changes.

            Finally, I should note that messing with the BIOS may cause the OS to crash or not boot up. So use caution while doing this.

  38. Hi Guys,
    First of all, a massive thank you for this tutorial and downloads.

    I am using an original Xbox controller on a Windows 10 system.
    The good news is that using this tutorial, I have got my controller connected and working (well, it says that it is working via the joy.cpl command – I can calibrate and test and all that good stuff).

    However, I am now trying to map the controller to keyboard settings (I’m using Gamepad Map from sourcebinary.com), but it does not recognise the controller. I have tried other mapper software, but they all don’t recognise the controller.

    What am I doing wrong, and what is the solution/workaround?
    Many thanks

  39. Hello, i have to say great tutorial! I have a little doubt and want ti see if you can assist me a little. First of all, even when this tutorial is base on w8-10 i wanted to ask some help for W7 64bit. You said that you got your pelican wireless controlers working, i have a Pelican Blade 2.4 (PL-2062) and i modde the wireless receiver to see if this mod could work. Well my pc detects the controler as a Generic USB HUB, although following a tutorial in another page I got to see the vendor and product ID with USB View and then include it to the installed driver .inf file. In the end, when i check my device manager windows recognizes the control as an XBCD Controller however i cant use neither the XBCD Setup Utility to map buttons nor the X360 cntroller emulator. Any sugestions?
    P.D: im not a native english speaker so i apologize in advance for any mistake/misunderstanding

    • First thing I’d have to ask is what is the hardware ID that is being reported? Second question is skipping XBCD and X360ce what does joy.cpl have to say about it? Does it even acknowledge the joystick in windows at all?

      • using USB View, before installing/assign the driver to the controller, I used this report to get the vendor and product ID:
        External Hub: USB#VID_0E6F&PID_0001#5&ce4f649&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
        Hub Power: Bus Power
        Number of Ports: 3
        Power switching: Individual
        Compound device: Yes
        Over-current Protection: Individual

        Device Descriptor:
        bcdUSB: 0x0110
        bDeviceClass: 0x09
        bDeviceSubClass: 0x00
        bDeviceProtocol: 0x00
        bMaxPacketSize0: 0x08 (8)
        idVendor: 0x0E6F
        idProduct: 0x0001
        bcdDevice: 0x000E
        iManufacturer: 0x00
        iProduct: 0x00
        iSerialNumber: 0x00

        After getting th PID & VID, and inlcude them in the .inf file, I was able to install the driver through the device manager, right clicking in the device (recognized as Generic USB Hub) an then askin to update the driver. Then the controler was shown under the HID Devices with two entries, one as a XBCD Xbox Controller and the another as a HID Compatibe Gaming Device (This one is a translation so the name might be a little different in english). Anway, then i went to the Control Panel-Devices and Printers an there it was again the HID Compatibe Gaming Device, by right clickling and slecting configuration i entered the joy,cpl (I guess) and the only device was the XBCD Xbox Controller, so far so good, so lets see if windows can read the inpust, form the joy.cpl I selected properties to see if the inputs were ok, and I find myself with 24 buttons, POV Control, And the axes (left stick X/Y on the upper left side , Z axis, X rotation, Y rotation, Z rotation and Sliding control (translation) on the upper right side)

        Ok now about the hardware ID, well as I said above the device has two entries in the device manager,if ia access the HID Compatibe Gaming Device properties-Details-Hardware ID there are shown the following entries:
        on the other hand if I do the same with the XBCD Xbox Controller this is what is shown:

        Well I hope this could help you to help me. Thank you again

        • it seems you got the right device/vendor ID. But upon launching joy.cpl are you receiving any inputs when moving the analog sticks or buttons?

          Also, since I owned a xbox pelican remote a long time ago. I remembered the dongle would have a power light and upon pressing buttons or moving the analog stick that dongle would begin to flash indicating that the signal was being received. Pelican put this feature on there because you could set it to four different radio frequencies and it was a way of letting the user know that they are locked in on the right channel. Is that light flashing at all when moving the stick?

Leave a Comment to the Void