PS4 Controller on PC: Full DS4Windows Setup

The DualShock 4 remains one of the best value controllers you can put on a PC. Full six axis motion, a touchpad, a decent d-pad, and a used one costs very little now that the PS4 generation is over.

The catch is that Windows sees it as a DirectInput device while most games expect XInput. DS4Windows bridges that gap by creating a virtual Xbox controller from your real DualShock 4. It works well, and the setup has more sharp edges than most guides admit, starting with which version you should even be downloading.

Do you actually need DS4Windows?

Worth asking first, because a lot of people install it out of habit and then spend an evening fighting double input.

If you play mainly through Steam, you probably do not need it. Steam Input has supported the DualShock 4 natively for years, including gyro, touchpad and rumble. Enable PlayStation Configuration Support in Steam's controller settings and most things simply work. You can even add non-Steam games to your library to get the same treatment.

You want DS4Windows when you play outside Steam, when you need the controller to appear as an Xbox pad to a launcher that will not cooperate, when you want gyro mapped to mouse in a game with no controller support at all, or when you need macros and shift states that Steam Input does not offer.

Running both at once is the thing to avoid. Pick one layer.

Which DS4Windows to download in 2026

This has become genuinely confusing and it matters, because searching for DS4Windows returns a large number of lookalike sites.

The original project was written by Jays2Kings and stopped receiving updates in 2016. Ryochan7 took it over and maintained it for years, then archived the repository in January 2024 with version 3.3.3 as the final release. Schmaldeo forked Ryochan7's work and carried it forward, adding button debouncing and a stick calibration tool, before archiving that repository in March 2026. Further community forks have picked it up since.

Practical advice rather than a single link: check which fork is currently maintained before you download, and get it from the project's own repository or its official site rather than a search result. Several domains exist purely to rank for DS4Windows downloads and bundle their own installers. If a download page is heavy on ads and light on release notes, that is your signal.

Whichever build you use, the dependencies are the same:

• .NET 8 Desktop Runtime, x64 for nearly everyone. The desktop runtime specifically, not the console or server runtime
• Visual C++ 2015 to 2022 Redistributable, x64
• ViGEmBus driver, which DS4Windows will offer to install if it is missing

About ViGEmBus, which is now legacy software

ViGEmBus is the kernel driver that creates the virtual Xbox controller. Without it DS4Windows has nothing to output to.

It is worth knowing that the project has been retired. Nefarius archived the repository following a trademark dispute, and the last official release, 1.22.0, dates from November 2023. It still works on current Windows 10 and Windows 11 builds, and DS4Windows still depends on it.

Two practical consequences. First, never download ViGEmBus from a random driver site. It is a kernel mode driver with system level access and repackaged installers are a real risk. Use the official final release or let DS4Windows install it through its own welcome dialog. Second, if you have multiple versions installed, expect problems. Nefarius publishes a cleanup tool called Legacinator that removes legacy driver residue, and running it before a fresh install saves time.

A quirk to be aware of: the final ViGEmBus setup removed the updater component but did not change the driver version number, so Device Manager may still show an older version after installing. That is expected and not a failed install.

Installing DS4Windows properly

Two things to get right before you start.

Do not extract to Program Files. DS4Windows is a portable application and writes its settings alongside the executable. Windows restricts writes to Program Files, so settings silently fail to save and the app appears to forget everything between launches. Extract to somewhere in your user folder instead.

Do not run it from inside the zip. Extract the whole folder first. Running the executable from a compressed archive produces missing dependency errors that look like something else entirely.

The setup sequence:

1. Extract the archive to a permanent location such as C:\Users\YourName\DS4Windows
2. Run DS4Windows.exe. On first launch, it asks where to save settings. AppData or Program Folder are both fine, and Program Folder keeps everything portable
3. The welcome dialog offers to install ViGEmBus. Accept, and reboot if prompted
4. Connect your controller by USB. It should appear in the Controllers tab immediately
5. Check the Profiles tab. The default profile maps everything sensibly

If the controller does not appear, check Device Manager for a device called Wireless Controller. If it is there, DS4Windows should see it. If DS4Windows is running but showing nothing, try running it as administrator, since it needs driver-level access.

Connecting a DualShock 4 over Bluetooth

Turn the controller off. Hold the Share button and the PS button together for about five seconds until the light bar flashes rapidly in a double pulse.

On Windows: Settings, Bluetooth and devices, Add device, Bluetooth. It appears as Wireless Controller. Pair it, and DS4Windows should pick it up within a second or two.

The DualShock 4 needs Bluetooth 4.0 or newer and works reliably only on the Microsoft Bluetooth stack. Adapters shipping their own stack are the usual failure point. Toshiba adapters are documented as not working. Some CSR-based adapters fail on their own stack while working correctly under the Microsoft one.

If Bluetooth adds noticeable input lag, there is a setting worth knowing about. In the profile settings, turning off Enable Output Data reduces latency at the cost of losing light bar control and rumble. Whether that trade is worth it depends on what you play. Our guide on reducing controller input delay covers the wider picture, including emulator-specific settings.

hide ds4 controller: fixing double input

This is the problem everyone hits and the reason most people give up.

When DS4Windows runs, your PC now has two controllers: the physical DualShock 4 and the virtual Xbox pad. Games that read both receive every input twice. Symptoms are menus that jump two entries per press, characters that move at double speed, and analog sticks that behave strangely because two devices are fighting over the same axis.

The fix is to hide the physical controller so only the virtual one is visible.

Method 1: exclusive mode. DS4Windows tries to take exclusive access to the physical device, which prevents anything else from reading it. It is built in and requires no extra software, but it fails when another process, often Steam, has already claimed the device. Close Steam entirely before enabling it, and disable PlayStation Configuration Support in Steam so it does not grab the controller again.

Method 2: HidHide. This is the reliable one. HidHide is a filter driver by Nefarius that hides selected HID devices from everything except applications you explicitly whitelist.

Setting it up:

1. Install HidHide. DS4Windows offers a download link, or get it from the Nefarius project page
2. Reboot
3. Open the HidHide Configuration Client from the Start menu
4. On the Applications tab, add DS4Windows.exe to the whitelist
5. On the Devices tab, tick your DualShock 4 to hide it
6. Enable the device hiding toggle
7. Restart DS4Windows

Three details that catch people out. HidHide whitelists applications by file path, so if you move the DS4Windows folder later the whitelist entry stops matching and everything breaks. If you have renamed the executable, whitelist the renamed file. And HidHide hides individual device instances rather than device types, so a controller you use over both USB and Bluetooth appears as two entries and both need ticking.

Once configured, games see only the virtual Xbox controller and double input disappears.

Steam settings that conflict

Steam is the most common source of trouble once DS4Windows is working.

Go to Steam, Settings, Controller. If you are using DS4Windows for everything, turn off PlayStation Configuration Support so Steam stops grabbing the physical controller. Some setups also need Xbox Configuration Support disabled, since Steam will otherwise apply its own layer to the virtual Xbox pad DS4Windows just created.

The rule is simple. One translation layer at a time. Steam Input or DS4Windows, not both.

Verify everything before you play

Once it is running, check every input rather than discovering a problem mid-game.

Run the controller through a PS4 controller tester and press everything, including the touchpad click, both L3 and R3, and full trigger travel. You are looking for two things: inputs that do not register, and inputs that register twice, which means your hiding configuration is not working.

Sticks deserve particular attention on a used DualShock 4, since the DS4 is not known for stick longevity. A stick drift test will show whether the resting position sits off centre. If it does, DS4Windows can compensate: recent forks include a stick calibration tool in the Axis Config tab of the profile editor, available when the stick is in Controls output mode. It masks moderate drift well, though it will not fix a badly worn module.

Our controller testing hub covers what a healthy result looks like for each input type.

Getting more out of it

Once the basics work, the features worth exploring:

Gyro to mouse. The DualShock 4's motion sensors can drive mouse output, which gives you gyro aiming in games with no controller motion support whatsoever. Set it up in the Gyro section of the profile editor and bind an activation trigger.

Touchpad as mouse. Useful for strategy games and for navigating menus without reaching for a mouse.

Shift modifiers. Hold a button to give every other input a second function. Effectively doubles your available bindings.

Per game profiles. DS4Windows can switch profiles automatically based on the running executable, configured in the Auto Profiles tab.

Deadzone tuning. Stick deadzones are set per profile in Axis Config. If your DS4 has developed a little drift, a small deadzone is the practical workaround, though it costs you fine control.

If your controller has drifted far enough that no amount of software compensation helps, our guide on calibrating a controller in Windows 11 covers what the operating system can and cannot correct.