How to Fix XOutput Double Input with HidHide (Step-by-Step Guide)

Understanding Double Input — Why PC Games Register Ghost Controllers

When you configure XOutput, it does not overwrite or replace your physical gamepad driver. Instead, it relies on ViGEmBus to create an entirely new, secondary virtual Xbox 360 controller in Windows.

Older games only queried one input API. However, modern game engines (including EA’s Frostbite, Unreal Engine 5, and Unity) query both legacy DirectInput and modern XInput APIs simultaneously to maximize plug-and-play controller compatibility.

When you press a physical button (such as ‘A’), two separate input events fire at the exact same millisecond:

1. The game engine reads the raw DirectInput signal from your physical hardware.
2. XOutput intercepts that signal, translates it, and ViGEmBus broadcasts the XInput signal from the virtual Xbox 360 controller.

The game engine obediently executes both actions, resulting in classic double-input symptoms: menu selections skip two rows at a time, character selection screens assign you to “Player 2” (see our Controller Detected as Player 2 Fix), or tackling/passing triggers twice in sports titles.

What Is HidHide and How Does Kernel Device Cloaking Work

HidHide is an open-source Windows kernel-mode filter driver developed by Benjamin Höglinger-Stelzer (Nefarius). It attaches directly to the top of the Windows Human Interface Device (HID) driver stack as an Upper Filter Driver.

Instead of altering hardware firmware or hacking game files, HidHide intercepts all operating system requests to enumerate USB HID devices. If the requesting process is XOutput.exe, HidHide permits the raw controller data to pass through. If the requesting process is a game, launcher, or web browser, HidHide intercepts the query and reports that no physical controller exists.

Step 1 — Download and Install Nefarius HidHide

HidHide requires an active installation of ViGEmBus. If you have not yet set up ViGEmBus, complete our ViGEmBus Installation Walkthrough first.

1. Download the certified installer: HidHideMSI.msi (version 1.5.230.0) from our verified downloads portal or directly from the official Nefarius GitHub Releases.
2. Right-click the MSI file and choose Install (or execute with Administrator rights). Accept the license terms and keep the default destination folder intact.
3. Crucial Requirement: Restart Your PC. Like all kernel filter drivers, Windows cannot inject HidHide into the HIDClass driver stack until a full system reboot occurs. Skipping this restart is the primary reason users report that device hiding “fails to work.”

Step 2 — Whitelist XOutput in the Applications Tab

The whitelist tells HidHide which applications are authorized to pierce through the cloaking barrier and read your raw physical gamepad:

1. Open your Windows Start Menu, search for HidHide Configuration Client, right-click it, and select Run as administrator.
2. Navigate to the Applications tab (indicated by the checklist icon).
3. Click the + (Plus) button at the bottom right.
4. In the file browser, navigate to your permanent XOutput directory (e.g., C:\Tools\XOutput\) and select XOutput.exe.
5. Confirm that XOutput.exe appears in the whitelist table with an active checkmark.

Step 3 — Cloak Your Physical Controller in the Devices Tab

Now that XOutput has clearance to see all hardware, you must instruct HidHide to conceal your physical gamepad from every other application:

1. Switch to the Devices tab (represented by the gamepad icon) in the HidHide Configuration Client.
2. Locate your physical controller in the listed device tree. It will typically be labeled with its hardware name (e.g., “Generic USB Joystick”, “PLAYSTATION(R)3 Controller”, or the manufacturer VID/PID).
3. Check the box beside your physical controller. A red padlock icon will appear next to the device entry, indicating it is marked for cloaking.
4. Crucial Warning: DO NOT check the box next to “Xbox 360 Controller for Windows” (the virtual device created by ViGEmBus). Checking the virtual controller will cloak it from games, rendering your controller completely invisible!
5. At the bottom of the window, ensure the “Enable device hiding” checkbox is checked (the padlock icon at the bottom right will show as locked).

Step 4 — Verify Single-Controller Input in Windows and Games

Before opening your game, perform this quick 30-second verification test to confirm device hiding is functioning correctly:

1. Launch XOutput.exe as Administrator. Click Start on your controller profile. Notice that XOutput reads your button presses and stick movements normally because it is whitelisted.
2. Press Windows Key + R, type joy.cpl, and press Enter to open the native Windows Game Controllers window.
3. Inspect the list: You should now see EXACTLY ONE device listed: “Controller (XBOX 360 For Windows)”. Your original physical gamepad should be completely absent from this list.
4. Launch your game (e.g., EA Sports FC 24/25, Rocket League, or Forza). Navigate the main menus. Single directional presses will now move strictly one slot at a time, and the phantom “Player 2” split will be permanently resolved.

Troubleshooting Common HidHide Issues and Boundary Cases

If you encounter unexpected behavior after configuring HidHide, work through these verified diagnostic solutions:

When HidHide Is Not the Solution — Other Double Input Causes

While HidHide resolves the classic physical-plus-virtual hardware duplicate, certain symptoms resemble double input but stem from different technical faults:

• Character Creeping or Spinning Camera: If your character continues walking or menus scroll continuously without any button press, this is analog stick drift, not double input. Resolve it by configuring a 5% to 8% deadzone using our Stick Drift & Deadzone Guide.
• Two Physical Controllers for Local Co-Op: If you are configuring two physical controllers for local multiplayer, do not hide both into Controller 1. In XOutput, click “Add controller” twice to create Controller 1 and Controller 2 independently.
• DirectInput Protocol Incompatibility: If a 2026 title refuses to register inputs at all, the game engine does not listen for DirectInput signals. Review our DirectInput vs XInput Explainer to understand how modern APIs function.

Frequently Asked Questions About HidHide and XOutput