The Xbox 360 controller uses 3 Axis and 2 Rotations as input for its two analog sticks and 2 triggers; the triggers both share the Z-Axis. The Dualshock 4 on the other hand uses 3 Axis and 3 Rotations for the same. According to Windows' very own Game controller settings: The Xbox 360 offers a total of 10 buttons3. Well, if you only need one working, and prefer the DS4, let's work on getting that working. Firstly, I'd suggest uninstalling everything and anything related to the DS4 and Xbox 360 controllers. Drivers, files, registry. We want a fresh start. After that we'll try and go step by step to install the DS4 properly. Never cared for the 360 controller all that much but I did enjoy using it more then the Xbox controller. DS4 is awesome and I still liked the DS3 (must be from using the DS and DS2 controllers for 15 years).

• When installing DS4Windows, the link provided to download the Xbox 360 Driver is no longer valid. I know this is a really minor issue, I just wanted to make you aware.
• Click on “ Step 1: Install the DS4 Driver” button to install the needed PS4 drivers on your Windows 8.1 OS and later computer. Click on “ Step 2: If on Windows 7 or below, Install 360 Driver” button only if you have a Windows 7 or older OS since this OS doesn’t come with the 360 drivers needed to run the DS4 drivers correctly by default.

Microsoft Xbox 360 Controller Driver

Never cared for the 360 controller all that much but I did enjoy using it more then the Xbox controller. DS4 is awesome and I still liked the DS3 (must be from using the DS and DS2 controllers for 15 years). Step Three: Install the Virtual Bus Driver. This is the magic step, the one that fools Windows into thinking the DualShock 4 is an Xbox 360 controller. Open the Virtual Bus Driver folder in the extracted folder and run ScpDriver.exe. Click Install and wait for the program to finish.

Getting Windows 10 and the DS4 controller to work with x360ce

DS4 controller works properly now!

I've rewritten this post to reflect my newest findings. I can't edit the post's title, sadly.

• DS4Windows 1.4.27 workaround
  Might be a little outdated
  The newest version of DS4Windows includes a built-in way of connecting the controller exclusively. It makes use of the explorer.exe workaround. This one's recommended if you want the extra functionality and if you're fine with having to use the workaround.

• SCP Toolkit
  This is a fairly new continuation of the original SCPServer. This new release apparently fixes a Bluetooth input lag issue. This solution should work across all games. I recommend checking this out, as the forum post and the how-to's for this solution are really clear. Also, this solution completely bypasses the exclusivity bug. The downside is that you don't get the extra functionality DS4Windows provides, such as being able to use the touchpad as a mouse.
  As suggested by: /u/itsjase

• DS4Windows + x360ce
  You get to keep touchpad functionality, but you'll have to put the x360ce files in all the main directories of the games that you're having problems with.

Hey there guys.

Recently there was a post regarding how the DS4 controller didn't work with Windows 10). This was due to DS4Windows not being able to hide the DirectInput version of the PS4 controller which then causes issues in some games that try taking input from DirectInput devices.

Note that this doesn't mean that the DS4 controller doesn't work at all. It's rather that some games in particular don't work well with the controller.

I've tried out several different programs: SCP Server, DS4Windows, InputMapper, and x360ce. DS4Windows and InputMapper both suffer from the same problem regarding the exclusive mode. With a little work SCP Server and x360ce both work. /u/MrHuk recently mentioned a solution which also works. Since that solution is relatively clean and not as intrusive as SCP Server in terms of driver installs this is currently the recommended solution. Using SCP Server will also work, but this involves a driver replacement which is a bit more intrusive.

Note that this advice might be a little outdated. DS4Windows is currently at version 1.4.32, and in version 1.4.3 they removed the exclusive connection button if you're running the newest Windows 10 build.

The newest version of DS4Windows includes a built-in way of connecting the controller exclusively that was initially linked by /u/MrHuk in this post. For reference, this is the explorer.exe fix.

(Windows 10) Thanks to another workaround found, it has been added to DS4Windows, there is a button on the main tab, to connect your controller exclusively, this will temporarily kill explorer (The taskbar) and bring it back once a controller is connected

To use that workaround you need to do the following:

1. Make sure your DS4 Controller is not connected yet.

2. Enable the Hide DS4 Controller (Exclusive Mode) option. This makes the 'Connect DS4 exclusively' button appear in the Controllers tab.

3. Click said button. Explorer.exe will be killed temporarily.

4. Follow the instructions in the terminal window. That is, connect your controller.

5. Done! Be sure to have your 'Network List Service' set to its default setting (manual) in services.msc if you have changed this with other workarounds. Also make sure that you start from a clean slate. If you've used Zadig and replaced a driver, remove the device together with the driver in the device manager, then disconnect and reconnect the device.

Check out this forum post. It features several links with very clear how-to's on how to install your controller. This release should fix Bluetooth input lag.

The previous SCPServer solution required you to use Zadig to replace a controller driver. If you want to revert that you'll find the instructions down below.

Reverting from the Zadig driver replacement - In case you want to switch back

1. Go into Device Manager.

2. Find the Wireless Controller that corresponds to your DS4 controller.

3. Right click > Uninstall, and be sure to also uninstall the driver.

4. Disconnect and reconnect your controller. Windows will reinstall the device with the default drivers.

This is the old workaround I started this thread with initially. I've now expanded it a little bit. X360ce is an interesting program which essentially converts the output of DirectInput devices into Xinput output. If you combine DS4Windows with x360ce you can keep the touchpad functionality while also being able to use the controller normally.

Changing DS4Windows settings

While this step isn't absolutely necessary, it might prevent some weird interference between Xinput and DirectInput.

Xbox 360 Controller Driver Download Windows

1. Open the Profiles tab and edit the Default profile (or whatever profiles you use)

2. Check the Use Dinput only option. This removes the emulated 360 controller.

3. Save your profile.

Setting up x360ce

1. Download x360ce here. Download the 32-bit version for 32-bit games, and/or the 64-bit version for 64-bit games.

2. Extract the executable from the archive into the game directory. You should put it in the same directory as the game's executable.

3. Make sure your controller is connected. Then run the executable. It will attempt to generate two files: x360ce.ini and xinput1_3.dll. Let x360ce do this.

4. It should show you that it detected a new controller*. Just follow the instructions and let x360ce search for settings automatically.

5. Fiddle around with your controller a little. It should display your controller inputs on-screen.

6. Click on Save and see if your game works properly now.

Download Xbox 360 Controller Driver

*(If you've enabled the Use Dinput only option x360ce will only detect one controller per DS4 controller. Otherwise it will detect two.)

I hope this guide works for you guys. Also, I will change this whenever it's needed. This is very much a work in progress thing, so if there are new developments / discoveries do let me know. I'll try it out and adjust the guide accordingly.

• /u/mmaruda pointed out in this post that if you use DS4Windows and connect your controller via Bluetooth Windows will actually prioritize the emulated Xbox 360 controller. Go ahead and give it a try.

• Apparently disabling the 'Network List Service' (via services.msc) fixes the exclusivity issue. It, however, also breaks the start menu. If you permanently disable the Network List Service and reboot the start menu won't take any input from your keyboard. Some people will mention that disabling the 'DHCP Client' service also fixes the problem, but this is because disabling this service stops several other services as well, including the 'Network List Service'.