If one button press moves through two menu items, a game detects two controllers when only one is connected, or controller prompts keep switching between Xbox and PlayStation icons, you may be experiencing double input.
This can happen when a game receives input from both your physical DualSense and a virtual controller created by DSX. HidHide can help by hiding the physical controller from selected applications while allowing the controller-mapping software to access it.
However, HidHide is not necessary for every DualSense setup. If your game already supports the controller directly and you’re not using virtual controller emulation, start by testing the game without DSX.
This guide explains when HidHide is useful, how to configure it, and how to check whether it has actually solved the problem.
Why Double Input Happens
A DualSense controller can be visible to Windows as a physical device. Controller-mapping software may also create a virtual gamepad that presents the same button presses to a game.
If the game receives input from both devices, one physical button press can produce two actions.
Common symptoms include:
- Menus skipping an item with each button press.
- A character responding twice to one input.
- A game detecting two controllers instead of one.
- Xbox and PlayStation button prompts appearing inconsistently.
- One controller appearing as both a physical device and a virtual gamepad.
The exact behavior depends on the game, controller mode, and software involved. Seeing two controller entries does not always mean double input is occurring, but it is a useful clue.
What HidHide Does
HidHide is a Windows utility that lets you hide selected physical devices from applications.
In a typical virtual-controller setup, the intended arrangement is:
DualSense → DSX → Virtual controller → Game
HidHide can prevent the game from seeing the physical DualSense directly while leaving DSX able to access it. The game can then use the virtual controller without also receiving input from the physical device.
The important distinction is that HidHide controls device visibility. It does not create a virtual controller, change button mappings, or repair a broken USB or Bluetooth connection.
Official project: HidHide on GitHub.
Before You Install HidHide
First confirm that double input is actually the problem.
- Connect your DualSense.
- Check whether DSX detects the physical controller.
- See whether your current setup uses a virtual controller.
- Test the game with DSX closed if the game supports the DualSense directly.
- If the game works correctly without emulation, you may not need HidHide at all.
If the game requires a virtual Xbox or DualShock 4 controller and receives duplicate input, HidHide may be appropriate.
Version note: The older GitHub release of DualSenseX is discontinued. Its driver requirements can differ from the current Steam version of DSX. Do not install additional drivers simply because an older tutorial lists them.
Step 1: Install HidHide from the Official Source
If HidHide is not already installed and your setup needs it, use the official project release page.
- Visit the HidHide releases page on GitHub.
- Choose the appropriate release and installer.
- Follow the installation instructions.
- Restart Windows if the installer requests it.
- Open the HidHide Configuration Client.
Download the software from the official project rather than an unrelated driver-download website.
If HidHide is already installed, check its configuration before reinstalling it. A missing configuration entry or disabled hiding option may be the actual problem.
Step 2: Select the Physical DualSense in the Devices Tab
Open the HidHide Configuration Client and select the Devices tab.
You should see the gaming devices available for configuration. Depending on the connection and Windows device instance, your controller may appear under a name such as Wireless Controller or another Sony/DualSense-related label.
- Identify the physical DualSense.
- Select the device you intend to hide.
- Double-check that you have not selected an unrelated controller or device.
The exact device name can vary, so do not rely on one label alone.
If you have multiple controllers connected, identify the correct device before enabling hiding. Hiding the wrong device can make another controller unavailable to applications that need it.
Step 3: Enable Device Hiding
In the HidHide Configuration Client, locate the Enable Device Hiding option.
Enable it after selecting the correct physical controller.
This setting activates the hiding behavior for the configured devices. Selecting a controller without enabling hiding may not produce the result you’re expecting.
Be aware that hiding the physical controller can affect applications that are not allowed to access it. That’s why the next step matters.
Step 4: Allow DSX to Access the Physical Controller
Switch to the Applications tab in the HidHide Configuration Client.
This list determines which applications are allowed to access devices that HidHide hides from other applications.
To configure your setup:
- Add the executable for the DSX version you actually use.
- Confirm that the correct application path has been selected.
- Keep DSX on the allowed-application list so it can access the physical DualSense.
- Do not add the game to the list unless you specifically want that game to access the hidden physical controller.
The executable path depends on how DSX was installed. If you use the Steam version, locate its actual executable rather than copying a path from an older guide.
If you reinstall DSX or change versions, revisit this list to make sure it still refers to the correct application.
Important: The HidHide Configuration Client and DSX are separate applications. Allowing the configuration client does not automatically mean the DSX application itself has been allowed to access the physical controller.
Step 5: Restart DSX and Check the Controller
After configuring HidHide:
- Close DSX completely.
- Check the system tray to make sure it is not still running.
- Reopen DSX.
- Connect or reconnect the DualSense if needed.
- Confirm that DSX detects the physical controller.
- Check whether the virtual controller is available when your selected emulation mode is enabled.
If DSX can no longer detect the physical controller, recheck the HidHide application list and the device selection.
Do not keep enabling or disabling unrelated drivers without first confirming these settings.
Step 6: Check Windows Controller Visibility
Windows includes a controller utility that can help with basic testing.
- Press Win + R.
- Type
joy.cpl. - Press Enter.
- Review the game controllers Windows lists.
If your setup creates a virtual Xbox controller, you may see an entry such as Controller (XBOX 360 For Windows).
The physical DualSense may not appear in this list if HidHide is hiding it from the application that displays the controller list.
However, the number and names of the entries depend on the devices and drivers installed. Two entries do not automatically prove that a game is receiving double input, and one entry does not guarantee that every game will behave correctly.
Use this check as one diagnostic step, not the final test.
Step 7: Test the Fix in the Game
The most useful test is the game that previously had the problem.
- Launch the game with the intended DSX configuration.
- Open a menu.
- Press a direction button once.
- Confirm that the selection moves one step.
- Test a few other buttons.
- Check whether the game continues to receive duplicate input.
If the double input has stopped, the configuration may be working as intended.
If the problem continues, check whether another controller-mapping application or Steam Input is creating an additional input path. Also confirm that the game is using the controller output you intended.
Button prompts can still vary by game and controller mode. Xbox prompts alone do not prove that HidHide is configured incorrectly.
Common HidHide Problems and How to Fix Them
DSX No Longer Detects the Controller
If DSX cannot access the DualSense after enabling hiding, check the Applications tab.
Make sure the correct DSX executable is allowed to access hidden devices. Also confirm that the physical DualSense is the device you intended to hide.
If necessary, temporarily disable device hiding to test whether HidHide is responsible. Restore the intended configuration after testing.
Double Input Continues After HidHide Is Enabled
Check these points:
- Is device hiding enabled?
- Is the physical DualSense selected in the Devices tab?
- Is DSX allowed to access the physical controller?
- Is the game receiving input from the virtual controller?
- Is another controller-mapping program running?
- Is Steam Input creating another controller path?
HidHide only controls the visibility of the selected physical device. It cannot prevent duplicate input caused by two separate virtual controllers or other software configurations.
The Physical Controller Disappears from Windows Applications
This may be expected if the device is hidden from those applications.
Check which application is trying to access the controller and whether it is allowed through HidHide. Avoid adding every application to the whitelist without understanding why it needs access.
If you want to test the physical DualSense directly, temporarily disabling device hiding can help isolate the cause.
The Problem Returns After Reconnecting Bluetooth
Windows can expose a controller through a device instance that differs from the one you previously configured. If double input returns after re-pairing the DualSense, open HidHide and check whether the physical controller appears as another device entry.
Identify the correct instance before changing the hiding configuration.
The Problem Returns After Reinstalling DSX
If you change or reinstall DSX, check whether the application path in HidHide still points to the correct executable.
An outdated entry may not allow the current DSX application to access the hidden physical controller.
Update the entry only after confirming the path for your installed version.
HidHide Is Installed but Does Not Seem to Help
Installing HidHide alone is not enough. The physical device must be selected, hiding must be enabled, and the intended application must be configured correctly.
If these settings are correct and the game still receives duplicate input, investigate other input-mapping software and virtual controllers rather than repeatedly reinstalling HidHide.
Should You Use HidHide with Every DualSense Game?
No.
If a game supports the DualSense directly and works correctly without DSX, adding a virtual controller and HidHide can introduce unnecessary complexity.
Use the simplest controller path that works:
Native support: DualSense → Game
Virtual controller setup: DualSense → DSX → Virtual controller → Game
HidHide is mainly useful in the second arrangement when the game also sees the physical DualSense and duplicate input occurs.
The correct setup depends on the game, controller mode, and software version.
Does HidHide Replace ViGEmBus?
No. They have different roles.
ViGEmBus was used by legacy controller-mapping software to create virtual gamepads. HidHide controls whether selected applications can see particular physical devices.
If your virtual controller is not being created, HidHide cannot create it. If a game sees both the physical and virtual controllers, HidHide may help with device visibility.
Not every current DSX setup requires ViGEmBus, so check your version before installing or removing it.
Frequently Asked Questions
Why does one button press move a game menu twice?
The game may be receiving the same physical input through both the physical DualSense and a virtual controller. Other input-mapping conflicts can cause similar symptoms.
Should I add my game to HidHide’s Applications tab?
For the usual double-input setup, the goal is to allow DSX to access the hidden physical controller while preventing the game from accessing that same physical device. Adding the game to the allowed list may defeat that purpose. Follow the configuration that matches your intended setup.
Will HidHide remove PlayStation button prompts?
HidHide controls device visibility, not the button icons shown by a game. The prompts depend on the controller type the game receives and the game’s own support.
Do I need ViGEmBus to use HidHide?
No. HidHide and ViGEmBus serve different purposes. Whether you need a virtual-controller driver depends on your software and emulation setup.
Is HidHide necessary for Bluetooth controllers?
Not by itself. HidHide can be useful with a Bluetooth-connected DualSense if the physical controller and a virtual controller both reach the game. The connection method alone does not mean HidHide is required.
Still Getting Double Input?
If the problem persists, start with our DS5Windows/DualSenseX Troubleshooting Guide and check the relevant information in our Drivers Guide.
Before making more changes, record which DSX version you use, whether emulation is enabled, which controllers appear in joy.cpl, and whether the duplicate input happens in every game or only one.
That information will help you identify whether HidHide, a virtual controller, Steam Input, or the game’s own controller support is responsible.