DS4Windows Setup Guide

DS4Windows solves one specific problem: some PC games only understand Xbox-style input and will completely ignore a PlayStation controller. DS4Windows fixes that by presenting your DualSense or DualShock 4 to Windows as a virtual Xbox controller, so those games see something they recognise.

It's the standard tool for this job, it's free, and setup takes about ten minutes. It also has two well-known failure modes — double inputs and Steam conflicts — that this guide covers properly, because they're where most people get stuck.

Do you actually need DS4Windows?

Try without it first. Windows and Steam both support the DualSense and DualShock 4 natively now, and most modern games read them without help. Installing DS4Windows when you don't need it adds a layer that can only cause conflicts.

You need DS4Windows when:

• A specific game ignores your PlayStation controller entirely but works with an Xbox pad
• You want system-level button remapping outside of Steam
• You want gyro-to-mouse conversion in non-Steam games
• You're playing games outside Steam that need XInput

You don't need it when: your games already work, or all your games are on Steam, where Steam Input does the same translation job without a separate tool.

The underlying issue is the XInput/DirectInput split — PlayStation pads aren't XInput-native, which is why translation is needed at all. Our XInput vs DirectInput guide covers why.

DS4Windows setup: installation

Installation is three components: the .NET runtime, the ViGEmBus driver that creates the virtual controller, and DS4Windows itself. The installer handles most of this, but the driver step is the one that fails most often.

Step 1 — Download from the official source only. Get DS4Windows from its official GitHub releases page. This matters more than usual: this tool's name is heavily targeted by fake download sites bundling malware. If a download page has an ad-heavy installer or asks you to run a "download manager," you're on the wrong site.

Step 2 — Extract and run. DS4Windows ships as a portable archive rather than a traditional installer. Extract it somewhere permanent — not your Downloads folder — and run the executable. It will ask where to save settings; either option is fine, but AppData is tidier.

Step 3 — Install ViGEmBus. On first launch, DS4Windows prompts you to install the ViGEmBus driver. This is the component that creates the virtual Xbox controller, and DS4Windows cannot work without it. Accept and let it install. If this step fails, install ViGEmBus separately from its own project page before continuing.

Step 4 — Install .NET if prompted. Recent versions require a specific .NET runtime, and DS4Windows will link you to it if it's missing.

Step 5 — Connect your controller. Plug in via USB or pair over Bluetooth. It should appear in DS4Windows' Controllers tab within a few seconds.

PS5 controller on PC: connecting a DualSense

Wired: connect with a USB-C cable that carries data, not just power. This is the single most common setup failure — many USB-C cables are charge-only, so the controller charges while Windows never registers it as an input device. If DS4Windows shows nothing, swap the cable before troubleshooting anything else.

Bluetooth: turn the controller fully off first, then hold the PS button and the Create button (upper-left of the touchpad) together for about five seconds until the light bar flashes rapidly. Add it from Windows Bluetooth settings, where it appears as "Wireless Controller."

PS4 controller on PC: the DualShock 4 works identically. For Bluetooth pairing, hold Share and the PS button until the light bar flashes.

Wired is the more reliable choice for DS4Windows specifically, and it avoids the Bluetooth bandwidth limitations that can affect rumble.

Hide DS4 controller: fixing double inputs

This is the problem everyone hits. Once DS4Windows is running, Windows sees two controllers: your physical PlayStation pad and the virtual Xbox controller DS4Windows created. If a game reads both, every button press registers twice.

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

Option 1 — DS4Windows' built-in hide toggle. In DS4Windows' Settings tab, enable "Hide DS4 Controller." This works, but it's known to reset after reboots or Windows updates on some systems, so you may need to re-enable it periodically.

Option 2 — Hide (more reliable). HidHide is a free, separate utility that hides the physical device at the system level and persists properly. Install it, add DS4Windows to its whitelist so it can still see the controller, then add your controller to the hidden devices list. This is the setup most long-term DS4Windows users end up with.

Important: whitelist the applications that should still see the physical device. Getting this wrong means DS4Windows itself can't read your controller, which looks like a total failure.

If you're getting double inputs and hiding hasn't fixed it, the cause is usually Steam — covered next.

DualSense on Windows 11: stopping the Steam conflict

Steam and DS4Windows actively interfere with each other by design, and this catches a lot of people out.

Steam deliberately ignores PlayStation controllers when it detects DS4Windows running, on the assumption that you're emulating an Xbox pad and it shouldn't double up. Usually that's helpful. Combined with certain settings, it produces games that receive nothing, or receive everything twice.

The rule: pick one input path per game, never both.

Setup: What to do: Using DS4Windows for a game Disable Steam Input for that game Using Steam Input for a gameClose DS4WindowsNon-Steam gamesDS4Windows only

To disable Steam Input per game: right-click the game in Steam, open Properties → Controller, set the override to Disable Steam Input, and relaunch. Many games only detect controllers at startup, so changes made while running appear to fail.

Enabling rumble and other features

Rumble works through DS4Windows via the virtual controller, and is enabled by default. If it isn't working, check that rumble is enabled in your active profile, that the game itself supports rumble, and that you're connected via USB — Bluetooth bandwidth limitations can affect it. Confirm the motors themselves are fine with a vibration test.

Light bar control is available in DS4Windows' profile settings, including battery-level colour indication.

Gyro to mouse is one of DS4Windows' genuinely valuable features. In your profile, map the gyro to mouse output with adjustable sensitivity, which gives you motion aiming in games that never supported it.

Touchpad as mouse is enabled by default on DualSense and DualShock 4.

What you lose: adaptive triggers and the DualSense's advanced haptics do not survive emulation. You're presenting the controller as an Xbox pad, and Xbox pads have neither feature. If a game supports DualSense features natively, you're better off without DS4Windows for that title.

Profiles and remapping

DS4Windows' profile system lets you save different configurations per game. Create a profile in the Profiles tab, remap any button, adjust stick deadzones and curves, configure gyro, and set the light bar.

On deadzones specifically: DS4Windows applies its own deadzone on top of whatever the game applies. Set DS4Windows' deadzone to match your stick's actual resting value rather than stacking arbitrary values, or you'll lose more precision than you intended. Measure it first with a deadzone test.

You can auto-switch profiles per application in the Auto Profiles tab, which is worth setting up if you use different configurations for different games.

Troubleshooting

Controller not detected at all. Charge-only USB cable is the leading cause. Swap to a data cable and use a rear motherboard port. If still nothing, reset the controller with the recessed button on the back, held about five seconds with a paperclip.

Double inputs. Hide the physical controller with HidHide, and disable Steam Input for that game.

Works in DS4Windows but not in games. Steam Input conflict, or the game needs relaunching after your configuration change.

Rumble not working. Check the profile setting, try wired, and confirm the motors work independently.

Everything broke after a Windows update. Reinstall ViGEmBus, re-enable hiding, and check DS4Windows for a newer release. Updates commonly disturb virtual driver setups.

Controller lags. Test wired versus Bluetooth to isolate it. Our input lag test gives you a comparative measurement rather than a guess.

The short version

DS4Windows presents your PlayStation controller to Windows as a virtual Xbox controller, which makes it work in games that only understand XInput. Try your games without it first, since Windows and Steam both support these pads natively now. Download only from the official GitHub project, install the ViGEmBus driver when prompted, and connect wired with a genuine data cable. The two problems everyone hits are double inputs — fixed by hiding the physical controller, ideally with HidHide rather than the built-in toggle — and Steam conflicts, fixed by disabling Steam Input per game. Accept that adaptive triggers and advanced haptics don't survive emulation.