/
/ hbashton

DS4Windows Downloads

hbashton DS4Windows Download & Setup

Download the hbashton DS4Windows community fork from GitHub, compare installer and portable packages, and follow its matching VIIPER setup.

The foundation of Nexus

DS4Windows Nexus is based on hbashton/DS4Windows. Its controller engine and many advanced capabilities come from that fork and the wider DS4Windows community. Nexus adds its own interface, guided setup, profile review and diagnostic workflows. The hbashton download is a separate upstream project, not an older Nexus release.

SEPARATE COMMUNITY FORK

Download from hbashton’s GitHub Releases

The author’s GitHub name is hbashton. Use the project’s own release list for download packages and version-specific notes.

Choose the installer or portable package from the release you want. Read its release-candidate status, requirements and known issues before installing. This is a separate build from Nexus.

Installer or Portable?

Windows x64 Installer

Use the release’s Setup EXE for guided installation. Follow its bundled driver setup and restart if requested.

Portable ZIP

Extract the complete DS4Windows_VIIPER_x64.zip into a dedicated writable folder. Portable still needs the relevant drivers; do not copy only the EXE.

Set Up and Test

  1. Back up profiles and close games, other DS4Windows instances and conflicting VIIPER instances before installation.
  2. Use the matching backend and driver components supplied with the chosen release. Current project documentation describes VIIPER and USB/IP; do not substitute ViGEmBus simply because an older guide mentions it.
  3. Configure optional HidHide when needed to prevent duplicate physical and virtual input. Ensure the mapper remains allowed to read the controller.
  4. Connect your controller, select a profile and choose the game-facing output.
  5. Test basic input before configuring advanced feedback. Native feedback depends on the game, controller, output and connection.

Use the fork’s official setup guide for version-specific instructions. Keep its update path separate from Nexus.

Project and Help Links