Frequently Asked Questions

DS5 Windows

Everything you need regarding DSX/DS5Windows compatibility, system specs, and features is right here. Still have questions? Reach out to our official support team anytime.

Is DS5Windows the same as DualSenseX?

Not officially, no. There’s no application that actually ships under the name “DS5Windows.” It’s a search term, not a product name, and it caught on because it mirrors “DS4Windows.” When people search for DS5Windows they usually end up needing DualSenseX (DSX), the tool built by Paliverse specifically for the DualSense controller. On this site we use DS5Windows and DSX interchangeably for that reason, but the actual download is DualSenseX. If you haven’t installed it yet, our Get Started guide covers the full setup.

Yes. DSX doesn’t include malware or spyware, and it only touches the controller drivers and system components it actually needs to function. It doesn’t read your files or change anything unrelated to controller input. The main risk isn’t the app itself, it’s where you download it from. Stick to the official Steam page or a source you trust, and skip random third-party mirrors.

It comes down to your controller and what you want from it. If you’re on a DualSense and care about adaptive triggers and full haptic feedback, DualSenseX is built for exactly that. If you’re on an older DualShock 3 or 4, a Switch Pro controller, or Joy-Cons, DS4Windows covers more devices, though its DualSense support is more basic than DSX’s. Check our Supported Controllers page for the full breakdown by device. Don’t run both at the same time, they’ll fight over the same input.

Yes, it runs in the background regardless of launcher. One thing to change if you’re on Steam: turn off PlayStation Configuration Support in Steam’s controller settings first, otherwise Steam and DSX both try to remap the same controller and you’ll get conflicting input. Our Install Guide walks through this setting step by step.

This happens more often than people expect, and it’s usually not DSX’s fault. Windows updates sometimes reset driver signing rules or quietly reinstall a generic HID driver over ViGEmBus. If your controller worked fine before an update and stopped right after:

  • Check Device Manager for a warning icon next to any controller entry
  • Reinstall ViGEmBus completely rather than repairing it
  • Restart before reconnecting the controller

See our Drivers page for the full install order if you need to start from scratch.

Start with the physical connection. If you’re on USB, make sure the cable actually carries data, a lot of USB-C cables are charge only. If you’re on Bluetooth, try removing the pairing and reconnecting from scratch. If it’s still not showing up, this is the sequence Paliverse themselves recommend: disable Steam Input in DSX’s properties, fully uninstall ViGEmBus and HidHide, reboot, then reinstall both from inside the app when it prompts you (choose not to restart after each one, then restart once after both are done). The full walkthrough is on the Troubleshoot page.

This trips a lot of people up. The old standalone version (v1.4.9) on GitHub was free, but Paliverse stopped updating it when DSX moved to Steam. The Steam version is a paid app now, it’s what actually gets ongoing updates, new features, and support. If you’re still on the free GitHub build, it still technically runs, but you won’t get fixes for anything that breaks on newer Windows versions or controller firmware going forward.

It checks in periodically to verify your purchase, and that check is cached for about two weeks, so you don’t need to be online constantly. If you’re offline for longer than that and try to launch DSX, it may get stuck waiting to verify ownership before it’ll start.

DSX+ is a separate paid add-on, not part of the base DSX purchase. It adds Virtual DualSense emulation (useful for games with native DualSense support that don’t work well through Xbox or DS4 emulation) and Bluetooth audio/haptics. If you’re mainly using Xbox emulation mode and don’t need native DualSense passthrough, the base DSX app covers most people’s needs without it.

This is one of the most common issues people run into, and it’s almost always Steam Input and DSX both trying to control the same controller at once. In DSX’s own properties, disable Steam Input, then set up HidHide so only DSX’s virtual controller is visible to games. Running both active on the same controller at the same time is what causes the double response.

If you’re on the Steam version, updates install automatically the same way any other Steam app does, there’s nothing to check manually. If you’re on the older free GitHub build, that one doesn’t auto-update at all, and as covered above, it’s no longer receiving new updates from Paliverse either way.

No, DualSenseX is closed source and maintained privately by Paliverse. DS4Windows is the opposite, it’s open source under a GPL-3.0 license, so if having access to the code matters to you, that’s the one to look at instead.

 

Partially. Basic rumble works fine wirelessly. Audio-based haptic feedback, the more detailed vibration that responds to in-game sound, only works over a wired USB connection. If haptics are the main reason you’re using DSX, USB is worth the extra cable. Connection specifics for both are in our Install Guide.

They control how much resistance the L2/R2 triggers give you, and DSX lets you adjust this per profile. In a supported game this might mean a bowstring that gets harder to pull the further you draw it, or a trigger that locks up when a weapon jams. Support depends on the game though. Most titles that weren’t built with DualSense in mind will just treat the triggers as a normal button press regardless of what DSX is doing.

Yes, DSX supports multiple controllers connected at once. Each one gets its own profile and emulated device so they don’t interfere with each other. Full device-by-device support details are on our Supported Controllers page.

Not noticeably beyond what the controller normally uses. Adaptive triggers and haptics do use more power than a basic Xbox controller’s rumble motor, so if you’re already running those features heavily in a game, that’s the battery drain you’re seeing, not DSX adding overhead on top.

Xbox 360 emulation is the safer default. Most PC games are built expecting an Xbox controller and will recognize it without issue. DualShock or DualSense emulation is only worth switching to if a specific game has native PlayStation controller support and behaves better that way. When in doubt, start with Xbox mode, our Get Started guide covers how to set this during first-time configuration.

You can skip it, DSX will still run. What you’ll likely run into without it is double input, where a game reads both your real controller and DSX’s virtual one at the same time and every button press registers twice. HidHide is what stops that. It’s optional in the sense that nothing breaks right away, but most people end up needing it eventually. Setup steps are on our Drivers page.