Some games and apps check for "DS4Windows.exe" and ignore or block PlayStation controllers when they detect it. Running DS4Windows under a different executable name can fix that so the game only sees the virtual Xbox controller.

In this article

When This Helps

  • Shovel Knight – can ignore DS4 controllers when DS4Windows is running.
  • Yuzu / Cemu – can ignore PlayStation controllers when DS4Windows is detected.
  • Steam Big Picture – may not interact correctly with PlayStation controllers if it detects DS4Windows.
  • Steam Input – some behavior is tied to the DS4Windows process name.

By renaming the process (via the custom .exe feature), these apps no longer see "DS4Windows" and your virtual Xbox controller works as usual.

How to Use a Custom .exe Name

  • Open DS4Windows and go to Settings.
  • Turn off Run at Startup (so you don't start two copies later).
  • Find Custom Exe Name (or similar) and enter a name, e.g. DSForW (no .exe).
  • Click Stop, then Start in DS4Windows. Exit DS4Windows completely (including system tray).
  • In the DS4Windows folder you'll see a new DSForW.exe (or the name you chose). Run that instead of DS4Windows.exe.

From then on, launch the custom .exe when you need DS4Windows. Check Task Manager to confirm the process name is the new one.

Reverting to the Original Name

Exit DS4Windows (and the custom .exe) fully. Start the original DS4Windows.exe. In Settings, turn off Run at Startup, clear the Custom Exe Name field, click Stop then Start, then close DS4Windows. You can turn Run at Startup back on if you want. Use DS4Windows.exe as before.

After Updating DS4Windows

Updates replace the main folder. The custom .exe is generated from the current build. After updating, open DS4Windows.exe once, set the custom name again if you use it, then use the new custom .exe from the updated folder.