DS5Windows/DlX Drivers for Windows
DS5Windows/DSX can use additional Windows drivers and software components for some of its controller features.
The two drivers most commonly associated with DSX are ViGEmBus and HidHide. They do different jobs, and you do not always need both. The drivers you need can also depend on which version of DSX you are using. Older versions of DualSenseX had different requirements from the current Steam version.
DS5Windows/DSX Drivers and Components
ViGEmBus Driver
ViGEmBus is a virtual gamepad driver that can create virtual controller devices in Windows.
The older GitHub version of DualSenseX, including DSX v1.4.9, used ViGEmBus for controller emulation. It could create virtual Xbox 360 and DualShock 4 controllers from DualSense input. The v1.4.9 release instructions specifically listed ViGEmBus as required for that version.
For example: DualSense → DSX → Virtual Xbox 360 Controller → Game
This can be useful when a game works better with an Xbox 360 or DualShock 4 controller than with the physical DualSense.
ViGEmBus does not replace the physical controller. It creates a separate virtual controller that Windows and games can detect.
Important: ViGEmBus should not be treated as a universal requirement for every current DSX installation. The current Steam version has its own system requirements and does not list ViGEmBus as a general requirement.
The ViGEmBus project is also archived, with version 1.22.0 listed as its final release.
HidHide
HidHide is a device-hiding driver designed to prevent controller input conflicts. When DSX creates a virtual controller, a game may detect both the physical DualSense and the virtual device. This can result in double input or duplicate controllers.
HidHide can hide the physical controller from selected applications while allowing permitted software to access it.
It is mainly useful when using virtual controller emulation. It is not required simply because a DualSense controller is connected to Windows.
HidHide is maintained as a separate project from DSX. Its official release page provides the current installer and installation instructions.
Windows Libraries & Frameworks
Some DSX versions also depend on standard Microsoft software components.
.NET Desktop Runtime
Older DSX documentation refers to the Microsoft .NET Framework, but the exact Microsoft runtime requirement can depend on the software version you are installing.
Do not treat .NET Framework and .NET Desktop Runtime as the same thing. They are different Microsoft technologies.
If your DSX version asks for a specific .NET Desktop Runtime, install that version from Microsoft rather than downloading individual DLL files from third-party websites.
The important thing is to check the requirement for the particular DSX version you are using.
Visual C++ Redistributable
The official DSX driver documentation also lists the Visual C++ 2015-2019 Redistributable among its Windows components.
These Microsoft runtime libraries are used by applications built with Visual C++.
The requirement can depend on the software version and components being used. If DSX reports that a Visual C++ runtime is missing, use the Microsoft package rather than downloading individual DLL files from an unknown website.
Windows 10 and Windows 11
The current Steam version of DSX supports 64-bit Windows.
Its current system requirements list:
- Windows 10 as the minimum operating system
- Windows 11 as the recommended operating system
- 64-bit processor and operating system
- x64 architecture
The current Steam version also notes that an internet connection is used for ownership verification, firmware update checks, and driver downloads. Its caching system allows the app to continue working offline for a limited period.
Windows itself is not a controller driver. It is listed here because DSX and its related components are designed to run within the supported Windows environment.
Which Driver Does What?
| Driver / Component | Main Purpose |
|---|---|
| ViGEmBus | Creates virtual controller devices for supported emulation setups |
| HidHide | Hides the physical controller from selected applications |
| .NET Framework | Provides the runtime required by applicable DSX versions |
| Visual C++ Redistributable | Provides Microsoft runtime libraries used by applicable software |
The first two are directly related to controller handling. .NET Desktop Runtime and Visual C++ Redistributable are supporting Windows software components rather than controller-emulation drivers.
Do You Need ViGEmBus?
It depends on the DSX version and the type of controller emulation you want to use.
For the older GitHub version of DSX, ViGEmBus was part of the required setup for its virtual controller features.
For example: DualSense → DSX → Virtual Xbox 360 Controller → Game
If a game already supports the DualSense directly, virtual controller emulation may not be necessary.
For the current Steam version, do not install ViGEmBus simply because you have a DualSense controller. Check the requirements for the version and features you are actually using.
Do You Need HidHide?
HidHide is mainly useful when the physical controller and virtual controller are both visible to a game.
For example, if the game detects:
- Physical DualSense
- Virtual Xbox 360 controller
you may experience double inputs or other controller conflicts. In that situation, HidHide can hide the physical controller from the game while allowing the required software to access it.
If you are not using a virtual controller and do not have an input conflict, you may not need HidHide.
About .NET and Visual C++
These components should not be confused with ViGEmBus or HidHide.
.NET Desktop Runtime and Visual C++ Redistributable provide software libraries used by applicable versions of DSX and related Windows software.
They do not create virtual controllers and they do not hide physical controllers. If DSX reports that one of these components is missing, install the required Microsoft component from an official Microsoft source.
Driver Requirements Can Depend on the DSX Version
DSX has had different releases and installation methods over time. The final GitHub release, DualSenseX v1.4.9, is no longer supported or updated. The project moved development to the Steam version of DSX.
The old v1.4.9 documentation specifically instructed users to install ViGEmBus and listed HidHide as an optional driver.
The current Steam version has a different installation model and its published system requirements do not list ViGEmBus as a universal requirement.
Because of this, an older DSX driver guide may describe a setup that does not exactly match a newer release.
For that reason, check the requirements for the particular DSX version you are installing instead of treating every old driver guide as a current requirement.
Driver Problems
Virtual controller is not appearing
If you are using an older DSX setup with Xbox 360 or DualShock 4 emulation, check whether the required virtual controller driver is installed correctly.
The game detects two controllers
Check whether both the physical DualSense and virtual controller are visible. If you are using virtual controller emulation, HidHide may help prevent the game from seeing the physical controller.
DSX reports a missing Windows component
Check the .NET or Visual C++ requirement for your DSX version and install the required Microsoft component from an official source.
Driver installation does not fix the problem
Avoid installing additional random driver packages. USB, Bluetooth, Windows updates, other controller-mapping software, and game-specific input settings can also affect controller detection.
If the problem is related to connection, controller detection, or game input, see our troubleshooting guide for the next steps.
Driver Installation
If your DSX version requires these components, install them from their original sources:
- ViGEmBus for virtual controller emulation.
- HidHide when the physical controller needs to be hidden from selected applications.
- Microsoft .NET Framework when required by the DSX version.
- Visual C++ Redistributable when required by the DSX version.
Restart Windows if an installer specifically asks you to restart, then launch DSX and test the controller.
Avoid third-party driver packs that bundle unrelated controller software.
Keeping Drivers Updated
Check the official project pages when you need a newer driver or when a Windows update causes a driver-related problem.
HidHide has its own release page where new versions are published. Always check the release information before updating.
For older ViGEmBus-based setups, remember that the ViGEmBus project is no longer actively developed and its repository is archived.
Stick to the original project or Microsoft sources when downloading drivers and runtime components.
Third-party sites sometimes repackage these installers. There is little reason to use a repackaged driver when the original source is available.