ViGEmBus for DS4Windows: Setup and Fix Guide

Why DS4Windows uses ViGEmBus

DS4Windows reads the physical controller; ViGEmBus creates the virtual controller presented to games.

A DualShock 4 or DualSense can connect without ViGEmBus, but many games expect XInput. DS4Windows translates the physical input and asks ViGEmBus to expose a virtual Xbox 360 or DualShock 4 device.

Check three layers separately: the physical controller, the active DS4Windows profile and output type, and the ViGEmBus device in Windows. This prevents unnecessary driver reinstalls.

How to install ViGEmBus for DS4Windows

Use the final official ViGEmBus v1.22.0 asset from the original nefarius GitHub repository. The file is ViGEmBus_1.22.0_x64_x86_arm64.exe, approximately 6.0 MB, and combines the supported installer architectures. The project is retired, so this is the last published release rather than an actively updated driver.

Keep diagnosis focused on the physical controller, active profile, virtual output slot, and ViGEmBus device. A failure at one layer does not prove the others need reinstalling.

1. 1

   Close DS4Windows and active clients

   Close DS4Windows and other controller-mapping tools before changing the driver.

2. 2

   Run the official installer

   Open the verified v1.22.0 GitHub asset and confirm the Nefarius publisher.

3. 3

   Restart Windows

   Reload the bus driver in a clean Windows session.

4. 4

   Start DS4Windows and reconnect

   Launch DS4Windows after reboot, reconnect the client and test controller input.

Verify that DS4Windows can use the ViGEmBus driver

Open Device Manager and find Nefarius Virtual Gamepad Emulation Bus. Open Properties and confirm Device status says the device is working properly. This is the strongest check that the kernel bus exists and is operational.

Also check Settings > Apps > Installed apps for the Nefarius driver entry. If the app entry exists but Device Manager has no working bus, the package is registered but the kernel device still needs repair.

• No warning icon appears on the Nefarius bus.
• Device status reports normal operation.
• DS4Windows started after the latest reboot.
• The active profile requests an Xbox 360 or DualShock 4 output controller.

Fix DS4Windows not detecting ViGEmBus

Keep diagnosis focused on the physical controller, active profile, virtual output slot, and ViGEmBus device. A failure at one layer does not prove the others need reinstalling.

DS4Windows ViGEmBus error matrix

Choose the smallest repair that matches the symptom. DS4Windows only needs a restart in some cases, while a missing kernel device requires driver repair.

What not to do when DS4Windows gamepad support fails

Do not assume a new DS4Windows build requires an unofficial ViGEmBus fork. DS4Windows changes independently, while the original ViGEmBus repository is archived. Use the verified final driver unless DS4Windows's current official notes explicitly require something else.

Do not delete every Nefarius or HID-related device. HidHide, Bluetooth adapters, physical pads and virtual buses have different jobs. Broad deletion can turn one DS4Windows issue into a larger controller problem.

• Do not use a similarly named EXE from a mirror.
• Do not mix an old MSI with the final EXE.
• Do not skip the reboot between removal and reinstall.
• Do not treat an DS4Windows web-login problem as a ViGEmBus problem.

Final checklist before testing DS4Windows again

Keep diagnosis focused on the physical controller, active profile, virtual output slot, and ViGEmBus device. A failure at one layer does not prove the others need reinstalling.

If the virtual controller works in Windows but not in one game, ViGEmBus is probably functioning. Check that game's controller mode, Steam Input, focus and supported controller type before reinstalling the driver again.

• Official ViGEmBus 1.22.0 installed from nefarius/ViGEmBus.
• Windows restarted after installation or removal.
• The Nefarius bus works in Device Manager.
• DS4Windows restarted after the driver became available.
• Only one intended virtual controller appears during testing.