Work through the steps in sequence and test the launch after each one. If InputMapper opens but then fails to detect or map a controller, switch to the relevant guide in our troubleshooting hub — this page is only about getting the program itself to start and stay open.

Check 1: .NET Framework 4.x

InputMapper is built on the .NET Framework, and it needs the .NET Framework 4.x line present and healthy on your system. If that runtime is missing, disabled, or damaged, InputMapper can fail silently at launch with no useful error message, which matches the “nothing happens” symptom many users report.

On Windows 10 and 11 the framework is a Windows component, so check it through “Turn Windows features on or off” and confirm the .NET Framework 4.x entry is enabled. If it is enabled but you still suspect damage, use Microsoft’s own repair options for Windows components rather than downloading runtime installers from third-party sites. Only ever describe or install it as “.NET Framework 4.x” — guides naming a precise minor version as a hard requirement are overstating what is known. After any change, reboot and test InputMapper before moving on.

Check 2: Run as Administrator

InputMapper talks to device drivers, and on some systems it cannot complete its startup without elevated privileges. Right-click the InputMapper shortcut or executable and choose Run as administrator. If the program opens and works under elevation but not normally, you have found your cause: set the shortcut’s compatibility option to always run as administrator so you do not have to remember each time.

Treat this step as a diagnostic even when it does not fix the problem. A launch that fails identically with and without administrator rights is telling you the block is probably not permissions, and your time is better spent on the security software and driver checks below.

Check 3: Firewall and Antivirus Allow-listing

InputMapper loads profiles from an online server, so firewall and antivirus prompts around this program are a known issue, discussed by users on the EA forums among other places. If your security software blocks InputMapper’s network access or quarantines part of the install, the program may hang while loading profiles, crash shortly after opening, or refuse to start at all.

Open your antivirus history or quarantine and check whether anything related to InputMapper was flagged or removed around the time the problem began. Add the InputMapper program folder to your firewall’s allowed apps and to your antivirus allow-list, then launch again. Do not disable your antivirus entirely as a test and leave it off; allow-listing the one program is the safe and sufficient step. If a component was quarantined, reinstall InputMapper after allow-listing so the missing piece is restored, using the order in the final section.

About the SmartScreen “Unknown Publisher” Warning

When you install or first run InputMapper, Windows SmartScreen may warn that the publisher is unknown. This happens because the old signer certificate behind the software was never renewed — the program is abandonware-era freeware from DSDCS, and its final build, 1.7.7452.13622, dates from May 2020. An unknown-publisher warning on a file you obtained from a trusted source, as described on our download page, is expected for software of this age.

The warning alone does not mean the file is malicious, but it does mean you should be certain where your copy came from. Only proceed past SmartScreen for a file you downloaded through a source you trust, never for an InputMapper installer that arrived via a bundle, an email attachment, or a random mirror. If you are unsure about your copy, delete it and re-download cleanly rather than clicking through.

Check 4: Remove Leftover Scp and HidGuardian Drivers

A launch crash can also be caused by what is underneath InputMapper rather than by InputMapper itself. PCs that have carried controller tools for years often hold leftover drivers from the SCP stack or from the legacy hiding stack, HidGuardian and HidCerberus. InputMapper 1.7-era installs even included a HidCerberus service of their own. Damaged or half-removed components from those projects can destabilise startup, because InputMapper enumerates devices and drivers as it opens.

Review what is installed before removing anything, and only remove controller-stack components you recognise as leftovers you no longer use. HidGuardian and HidCerberus are a legacy 2016 to 2018 stack that has been archived, and the modern hiding tool is HidHide, so most users need the old components for nothing. Do not delete driver files manually from system folders; use the normal uninstall routes, create a restore point first if you are about to change drivers, and reboot afterwards. Our background on SCPToolkit risks helps if you are unsure what an SCP component is doing on your system.

Final Step: Clean Reinstall in the Right Order

If the checks above do not revive InputMapper, reinstall cleanly and in the order the stack expects. First uninstall InputMapper. Then deal with the output driver: ViGEmBus, which InputMapper 1.7 uses for its virtual controller, should be installed and healthy before InputMapper goes back on. Install ViGEmBus 1.22.0 from GitHub releases only, following our ViGEmBus install guide, and reboot. Finally reinstall InputMapper, allow-list it in your security software, and launch it once as administrator for the first run.

Test with a bare setup: one supported controller, no game launcher running, no other mapper open. Confirm the program opens, stays open, and lists your controller, following the basics in how to use InputMapper. Only then restore your profiles — which is a good moment to start keeping a copy, as shown in how to back up InputMapper profiles. A program that opens cleanly on a bare setup but crashes when other tools return has given you the answer: one of those tools is part of the conflict.

Frequently Asked Questions

Why does InputMapper close immediately after opening?

The most common causes are a missing or damaged .NET Framework 4.x runtime, security software blocking or quarantining part of the program, and leftover Scp or HidGuardian drivers destabilising startup. Work through the runtime check, run as administrator, allow-list InputMapper, and reinstall cleanly in order.

Does InputMapper need .NET Framework?

Yes. InputMapper needs the .NET Framework 4.x line present and enabled. On Windows 10 and 11 it is a Windows component you can check under “Turn Windows features on or off”. If it is disabled or damaged, InputMapper can fail to launch with no clear error.

Is the SmartScreen unknown publisher warning dangerous?

The warning appears because the old signer certificate was never renewed for this discontinued software. It is expected for a genuine copy obtained from a trusted source, but you should only proceed if you are certain where your file came from and never for a copy from a bundle or random mirror.

Why does my firewall ask about InputMapper?

InputMapper loads profiles from an online server, so it legitimately needs network access and firewall prompts are a known issue. Allow InputMapper in your firewall and antivirus rather than disabling your security software, and reinstall if a component was quarantined.

This guide covers removing conflicting old installs first, installing ViGEmBus 1.22.0 correctly, and rebooting so the driver actually loads. For the fuller background on what ViGEmBus is and how it fits into the InputMapper stack, see our ViGEmBus install guide alongside this repair walkthrough.

What the Virtual Bus Does in InputMapper 1.7

InputMapper 1.7 does not create its virtual Xbox 360 controller by itself. It outputs through ViGEmBus, an independent project by developer nefarius that provides virtual gamepad devices on Windows. InputMapper reads your physical DualShock 4 or other supported controller, translates the input, and asks ViGEmBus to present it as an Xbox controller that games can use.

Earlier generations worked differently: InputMapper 1.5 and 1.6 used ScpVBus from the SCP stack instead. That history matters for this error, because leftover pieces of the old stack are one of the main reasons a fresh ViGEmBus install does not take over cleanly. If your PC has carried InputMapper, SCPToolkit, or similar tools over several years, assume there are leftovers until you have checked.

Step 1: Remove Conflicting Old ViGEm and Scp Installs First

Before installing anything, remove what is already there. Open Windows Settings, go to Apps, and uninstall any existing ViGEmBus entries, especially very old versions that predate the current driver. Do the same for SCP components such as ScpVBus if you no longer use the old SCP stack for anything else. Two virtual bus drivers competing for the same job can leave InputMapper unable to open either one reliably.

Be deliberate here. Only remove virtual bus and SCP components you recognise as part of old controller setups, and note what you removed in case another old tool depends on it. If you still rely on SCPToolkit for a DualShock 3 setup, read our notes on SCPToolkit risks before deciding what to keep. InputMapper supports the DualShock 3 only via a Magic-NS dongle, so most users do not need the SCP stack for InputMapper at all.

Restart the PC after uninstalling. Driver removals often only complete during a reboot, and installing the new bus on top of a half-removed old one is a reliable way to get the same error back.

Step 2: Download ViGEmBus 1.22.0 from GitHub Only

The final ViGEmBus release is version 1.22.0, published on November 2, 2023, after which the project was archived. It is distributed through GitHub releases only. Use the button below, which goes to the project’s GitHub release, and download the installer for 1.22.0.

Download ViGEmBus 1.22.0 on GitHub

Affiliate link — see our Affiliate Disclosure.

Warning: never use vigem.org

Do not download ViGEmBus from vigem.org, and do not follow an old updater that points to that domain. The domain was handed over, and old updaters pointing there are a documented risk. The same caution applies to random driver sites offering newer-sounding ViGEmBus versions: there is no release newer than 1.22.0, because the project is archived. Anything claiming to be a 2024 or 2025 ViGEmBus update from a third-party site is not the genuine driver.

Step 3: Install and Reboot

Run the 1.22.0 installer with administrator privileges and let it complete without interruption. When it finishes, reboot the PC even if the installer does not force you to. The virtual bus is a kernel driver, and InputMapper can only open it once Windows has loaded it in a fresh session. Testing without rebooting is the most common reason people conclude the install did not work when it actually did.

After the reboot, start InputMapper before your game launchers, connect your controller, and check whether the virtual bus error is gone and the virtual Xbox controller now appears. You can confirm in the Windows Game Controllers panel (joy.cpl): with a controller mapped, the Xbox 360 controller entry should be present alongside InputMapper’s own device view.

Upgrading in place? Run the installer twice

One quirk from the ViGEmBus release notes catches people out: when upgrading in place over an existing ViGEmBus installation, run the installer twice. The first run handles the existing installation, and the second completes the upgrade to 1.22.0. If you upgraded, rebooted, and still see the old version or the same bus error, run the 1.22.0 installer a second time and reboot again before trying anything more drastic.

Step 4: Verify InputMapper Sees the Bus

With a clean install in place, work through a short verification. First, open InputMapper with no game or launcher running, so nothing else can interfere with the test. Second, connect a supported controller — DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, or a generic DirectInput or XInput device. Third, confirm InputMapper lists the controller without a virtual bus error and that a profile can be started, following the basics in how to use InputMapper.

If the bus error returns only when a particular launcher is open, the problem is no longer the driver install itself. Close that launcher, retest, and treat it as a conflict rather than a broken bus. Our troubleshooting hub covers those conflicts, including exclusive mode and double input, which often appear alongside bus problems on messy older installs.

If the Error Persists

If a clean removal, a GitHub-sourced 1.22.0 install, the double-installer step for upgrades, and a reboot still leave you with a missing virtual bus, check the basics once more: that you are logged in with permission to install drivers, that your antivirus did not silently quarantine the installer, and that Windows is fully updated enough to accept the driver. Re-download the installer from GitHub in case the first download was incomplete, and run it as administrator.

Resist the temptation to fix a stubborn bus error by installing HidGuardian or other legacy hiding components, or by downloading bus drivers from unofficial mirrors. Those steps add new variables without addressing the bus itself. A verified ViGEmBus 1.22.0 install on a clean base solves this error in the overwhelming majority of cases; if yours is the exception, capture the exact error text and compare it with the entries in our InputMapper FAQ before changing anything else.

Frequently Asked Questions

What does virtual bus not found mean in InputMapper?

InputMapper 1.7 outputs its virtual Xbox controller through the ViGEmBus driver. The error means ViGEmBus is missing, failed to install, or is blocked by a conflicting older bus driver. Removing old ViGEm and Scp installs, then installing ViGEmBus 1.22.0 from GitHub and rebooting, fixes most cases.

Which version of ViGEmBus should I install?

Install ViGEmBus 1.22.0, the final release from November 2, 2023. The project is archived, so there is no newer official version. Download it only from GitHub releases, never from vigem.org or third-party driver sites.

Why do I need to run the ViGEmBus installer twice?

When upgrading in place over an existing ViGEmBus installation, the release notes call for running the installer twice: the first run handles the existing install and the second completes the upgrade. Reboot afterwards and retest InputMapper.

Is ViGEmBus the same as ScpVBus?

No. ScpVBus was the virtual bus used by InputMapper 1.5 and 1.6 as part of the SCP stack. InputMapper 1.7 uses ViGEmBus instead. Leftover ScpVBus installs can conflict with ViGEmBus, which is why removing old Scp components is part of this fix.

If the doubling happens in every program and not just Steam, your problem is more likely an unhidden physical controller — start with our double input fix. This guide is for the Steam-specific case and assumes InputMapper itself is set up as in how to use InputMapper.

Why Steam Input Fights InputMapper

Steam Input is Steam’s own built-in controller mapper. When it is active for a PlayStation controller, Steam reads the physical DualShock 4, applies its own configuration, and presents the result to the game. InputMapper is doing a parallel job at the same moment: reading the same pad and presenting a virtual Xbox 360 controller through ViGEmBus. A game caught between them can receive Steam’s output, InputMapper’s output, or on bad days both, which is why symptoms range from double inputs to dead buttons to a controller layout that changes between the Steam overlay and the game itself.

Only one mapper should own the controller for any given game. For InputMapper users, that means Steam Input must be switched off in the right places — plural, because Steam has a global PlayStation switch, Big Picture settings that mirror it, and a per-game override that beats both.

Fix 1: Turn Off PlayStation Configuration Support

The classic conflict switch is PlayStation Configuration Support in Steam’s controller settings. When it is on, Steam treats a connected DualShock 4 as its own to configure, which is precisely what an InputMapper user does not want. Open Steam settings, find the Controller section, and turn PlayStation Configuration Support off.

Restart Steam after changing it, reconnect your controller, start InputMapper before launching a game, and test a title that previously doubled. For many users this single switch ends the conflict, because Steam now leaves the physical pad alone and the game simply sees InputMapper’s virtual Xbox controller like any non-Steam game would. While you are in Steam’s controller settings, leave the equivalent support options for controller types you do not use with InputMapper as they are; change only what this conflict needs.

Fix 2: Set Steam Input to Forced Off Per Game

If a particular game still misbehaves, use the per-game override, which is the most surgical of Steam’s switches. In your Steam library, open the affected game’s properties, go to the Controller section, and set the Steam Input option to Forced Off. That game will then ignore Steam Input entirely and take its controller input directly — which, with InputMapper running, means from the virtual Xbox pad.

Per-game control is useful because it lets you keep Steam Input available for other titles where you actually prefer it. Apply Forced Off to one affected game, test it thoroughly, and only then repeat the setting for other games with the same symptom. If Forced Off fixes a game that the global switch did not, the game was probably using a stored per-game setting that predated your global change, which is common in libraries built up over years.

Fix 3: Check Big Picture Controller Settings

Steam’s Big Picture mode has its own controller settings screens, and configurations there can apply to your games even if you normally launch them from the desktop client. Open Big Picture, go to its settings and controller options, and confirm that PlayStation configuration support is off there as well and that no Big Picture controller configuration is being forced onto your games.

This check matters most if you ever use Big Picture — for example on a living-room PC — because it is easy to enable a setting in that interface once and forget it exists. After changing anything in Big Picture, fully exit and restart Steam before retesting, so no cached configuration from the previous session survives into your test.

The Reverse Case: When Steam Input Alone Is Better

Be honest about the alternative: for a library that lives entirely inside Steam, Steam Input alone may be the better tool, with no InputMapper involved at all. It is built into Steam, maintained, and applies its configurations per game automatically. If you rarely play non-Steam games and do not need InputMapper’s specific profiles, removing one mapper from the equation entirely is a legitimate solution, not a defeat.

Our full comparison of InputMapper vs Steam Input lays out where each one wins. The deciding factors are usually where your games live, whether you need one consistent Xbox pad outside Steam, and whether you are using a controller Steam handles well on its own. What you should not do is run both at once and hope the game sorts it out — that is the conflict this whole page exists to end. A comparison with the other dedicated mapper is also available in InputMapper vs DS4Windows if you are reconsidering your whole setup.

Important Caveat: Non-Steam Games Added to Steam

Adding a non-Steam game to your Steam library does not remove it from this conflict — it can import the conflict into a game that was previously fine. If Steam Input is active, launching that shortcut through Steam can let Steam map the controller on top of InputMapper for a title that never had a problem when launched directly.

Two practical rules follow. First, if a non-Steam game works perfectly outside Steam, keep launching it outside Steam, or set its per-game Steam Input option to Forced Off in the shortcut’s properties just as you would for a native Steam game. Second, when a previously fine game starts doubling right after you added it to Steam, suspect the shortcut before you suspect InputMapper, your drivers, or the game itself. Removing the game from Steam, or forcing Steam Input off for it, should restore the original behaviour immediately.

Putting It Together

The reliable InputMapper-plus-Steam routine is short: PlayStation Configuration Support off globally, Big Picture settings checked once, Forced Off applied per game wherever a title still resists, and InputMapper started before Steam games launch. Follow it and Steam becomes a neutral launcher that simply starts games, while InputMapper owns the controller for every one of them. More conflict and detection fixes are collected in our troubleshooting hub, and quick answers live in the InputMapper FAQ.

Frequently Asked Questions

Why does my controller double-press only in Steam games?

Steam Input is mapping your controller at the same time as InputMapper, so Steam games receive two translations. Turn off PlayStation Configuration Support in Steam settings, and if a game still doubles, set its per-game Steam Input option to Forced Off in the game’s library properties.

What does Forced Off mean in Steam controller settings?

Forced Off tells Steam to apply no Steam Input mapping to that specific game. The game then reads controllers directly, which for InputMapper users means it sees the virtual Xbox 360 controller InputMapper creates, with no second mapping layered on top.

Do Big Picture settings affect games launched from the desktop?

They can. Big Picture has its own controller settings, and a configuration enabled there can apply even when you launch from the desktop client. Check Big Picture once, make sure PlayStation support is not enabled there, and restart Steam afterwards.

Should I just use Steam Input instead of InputMapper?

If all your games are in Steam and you do not need InputMapper’s profiles or a consistent virtual Xbox pad elsewhere, Steam Input alone is a reasonable choice. Just do not run both mappers on the same controller at once, which is what causes the conflict.

Our dedicated Windows 11 hub collects the short version of these fixes. This post is the full walkthrough, in the order you should apply it after an upgrade.

Step 1: Rebuild the Driver Stack in the Right Order

A Windows upgrade can leave a driver stack that looks installed but is ordered or registered in a way InputMapper 1.7 no longer expects. The cleanest recovery is to rebuild the stack in order rather than patching it in place. The order that works is: InputMapper’s output driver first, any controller-hiding tool second, and InputMapper itself last.

Start with ViGEmBus, the driver InputMapper 1.7 uses to create its virtual Xbox 360 controller. If it is damaged or missing after the upgrade, follow our ViGEmBus install guide to install version 1.22.0 from GitHub releases and reboot. Next, if you use a hiding tool, make sure it is HidHide rather than the legacy stack (the next sections explain why). Finally, reinstall or repair InputMapper itself so its components register against the fresh drivers. Test after the rebuild with no launcher running before you change anything else.

Step 2: Recheck Detection and Profiles

After an upgrade, confirm the basics still hold. Windows should list your controller in the Game Controllers panel (joy.cpl), InputMapper should list the same controller in its device view, and your profile should load and start. InputMapper loads profiles from an online server, so allow it through your firewall if profile loading stalls after the upgrade; a fresh Windows 11 firewall profile can treat the program as new. It is also worth backing up your profiles once everything works again.

If the controller is not detected at all on Windows 11, do not assume the upgrade broke InputMapper specifically. Run through the cable, pairing, and Windows-visibility checks first; an upgrade is also when old cables and stale pairings choose to fail. Supported controllers remain the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices.

Step 3: Exclusive Mode on Windows 11

Exclusive mode is the feature that suffers most on Windows 11. InputMapper tries to claim the physical controller so games only see the virtual pad, but modern Windows gives other programs — Steam above all — more chances to open the device first. The symptoms are the exclusive mode failed error or its quiet consequence, double input in games.

The quick mitigations still apply: close Steam and other launchers completely, start InputMapper before them, and run InputMapper as administrator for a test. If exclusive mode then works, your drivers are fine and the issue was contention. If it still fails on a clean boot order, stop fighting the setting and move to the modern hiding method below, which does not depend on InputMapper winning that race.

Step 4: Use HidHide, Not HidGuardian, on Windows 11

Older InputMapper setups hid the physical controller with HidGuardian and HidCerberus, a research stack from 2016 to 2018 that has long been archived. On Windows 11 that legacy stack is the wrong tool: it was never built or maintained for this version of Windows, and leftover components from a Windows 10 install are a common source of strange behaviour after an upgrade.

The modern successor is HidHide v1.5.230 (May 2024), built for Windows 10 and 11 on x64. It hides the physical controller from everything except whitelisted applications, so you whitelist InputMapper and games only ever see the virtual Xbox controller. Our HidHide guide gives the full setup and explains the differences if you are migrating from the legacy stack. If your Windows 11 problems involve hidden devices, double input, or exclusive mode, this migration is the single change most likely to settle all three at once.

Step 5: Check Steam’s Role Separately

Windows 11 upgrades often coincide with a fresh Steam install or reset Steam settings, which can quietly re-enable PlayStation Configuration Support. With that option on, Steam grabs PlayStation controllers itself and InputMapper’s output doubles or conflicts. Turn PlayStation Configuration Support off in Steam settings, or set Steam Input to Forced Off per game, and retest. Keep this diagnosis separate from the driver work above: if double input happens only in Steam games, it was never a Windows 11 driver problem. Our troubleshooting hub links the dedicated Steam conflict guide.

When to Switch Tools Instead

There is a point where loyalty to InputMapper costs more time than it saves, and Windows 11 is often where users reach it. InputMapper is closed-source freeware by DSDCS whose final build, 1.7.7452.13622, was built in May 2020. It will not receive Windows 11 fixes, new controller support, or updates of any kind.

Switch tools in these cases. If your controller is a DualSense, InputMapper never supported it in the first place — follow our DualSense on PC guide for working options. If you want a maintained mapper for a DualShock 4, the DS4Windows continuation, ds4windowsapp v3.5 from February 2026, is the actively developed route; the original Ryochan7 line ended at 3.3.3 in December 2023 and its repository is now gone. Our DS4Windows install guide will help you make the switch. And if you play mainly Steam games, Steam Input alone may cover your needs without any external mapper at all.

None of that means you must abandon InputMapper today. For a supported DualShock 4 with a clean ViGEmBus install and HidHide hiding the physical pad, InputMapper on Windows 11 is a perfectly workable setup. The honest summary is: rebuild the stack, hide with HidHide, keep Steam in check — and if your hardware or patience has moved on, move tools with it.

Frequently Asked Questions

Is InputMapper officially supported on Windows 11?

No. InputMapper runs on Windows 11, but its final build dates from May 2020, before Windows 11 existed, so it was never officially supported there. Most problems after an upgrade come from the driver stack, exclusive mode contention, or legacy hiding tools rather than the program itself.

What order should I reinstall drivers on Windows 11?

Install ViGEmBus 1.22.0 first and reboot, then set up HidHide if you hide your controller, then reinstall or repair InputMapper last. Test with no game launcher running before changing other settings, and allow InputMapper through the firewall so its online profiles can load.

Should I use HidGuardian or HidHide on Windows 11?

Use HidHide. HidGuardian is a legacy, archived stack from 2016 to 2018, while HidHide v1.5.230 is maintained for Windows 10 and 11 and hides the physical controller per application through a whitelist, which fixes most exclusive mode and double input problems.

When should I switch from InputMapper to another tool?

Switch if you use a DualSense, which InputMapper never supported, or if you want a maintained mapper for the DualShock 4. The DS4Windows continuation, ds4windowsapp v3.5, is actively developed, while InputMapper’s final build from May 2020 will receive no further updates.

If your controller connects but then misbehaves in games, that is a different problem covered in our troubleshooting hub. This guide is only about getting a controller detected in the first place, following the same basic flow as how to use InputMapper for the first time.

First, Confirm the Controller Is Supported

InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 and PlayStation Move Navigation controller only via a Magic-NS dongle, and generic DirectInput and XInput devices. That list matters because two popular pads are not on it: the DualSense and the Switch Pro Controller are not supported by InputMapper at all.

If you are holding a DualSense, no cable or setting in this checklist will make InputMapper detect it. Use our guide to the DualSense on PC or the DS4Windows install guide instead. Switch Pro owners should likewise use a tool that supports that controller. For every supported pad, continue below.

Check 1: Data Cable vs Charge-Only Cable

The single most common cause of a wired DualShock 4 not being detected is a charge-only micro-USB cable. Many cables bundled with chargers and power banks carry power but no data lines. The controller lights up and charges, which makes the cable look fine, while Windows receives no data at all and InputMapper sees nothing.

Swap in a cable you know carries data — for example, one you have used to transfer files to a phone. Keep it short and plug it directly into a motherboard USB port rather than a front-panel port or unpowered hub for the test. Then watch Windows, not just InputMapper: a newly recognised controller should appear in Device Manager and in the Game Controllers panel. If a known data cable fixes detection, retire the old cable for controller use so you do not repeat the diagnosis next month.

Check 2: Bluetooth Pairing State

If you connect over Bluetooth, start by checking the pairing state in Windows Bluetooth settings. A controller that shows as paired but not connected, or that was paired to another device or user profile in between, often stays invisible to InputMapper. Remove the controller from the Bluetooth device list entirely, put it back into pairing mode, and pair it again as a fresh device.

Stay close to the PC during pairing and make sure the controller is charged; a nearly empty battery can drop the connection before InputMapper ever enumerates the device. Our Bluetooth pairing guide covers the exact pairing sequence and clean setup from scratch. If pairing repeatedly fails or the device vanishes, test with USB instead — the next check explains why that comparison is so useful.

Check 3: What Does Windows See?

Press the Windows key, type joy.cpl, and open the Game Controllers panel. This panel shows what Windows itself can see, independent of InputMapper. If your controller appears here, Windows has a working connection and the problem sits inside InputMapper or its drivers, so continue to the next checks. If the controller does not appear here either, InputMapper cannot invent it: fix the connection itself first, using the cable and pairing checks above.

While the panel is open, select the controller and open its properties to test a few buttons and sticks. Live responses confirm the device is not just listed but actually reporting input. A device that is listed but never responds is often connected over a failing cable, a weak Bluetooth link, or with a flat battery, even though it looks detected at first glance.

Check 4: Refresh InputMapper’s Device List

Sometimes Windows sees the controller but InputMapper’s list was built before the device was ready. Disconnect the controller, close InputMapper completely, reconnect the controller, wait a few seconds for Windows to settle, and only then reopen InputMapper. Starting InputMapper after the controller is already present gives it the cleanest chance to enumerate the device.

Also connect one controller at a time during diagnosis. Multiple pads, dongles, and virtual devices from other tools make it hard to tell which entry InputMapper is reacting to. Once detection works with a single controller, you can reconnect your other hardware and confirm everything still works together.

Check 5: Is ViGEmBus Installed?

InputMapper 1.7 outputs its virtual Xbox controller through ViGEmBus, the independent driver project by nefarius. If ViGEmBus is missing or its installation failed, InputMapper may have nothing to attach its output to and device handling can stall. The final ViGEmBus release is 1.22.0 from November 2023, distributed through GitHub releases only.

If you suspect the driver is missing, follow our ViGEmBus install guide rather than grabbing an installer from a random download site. Never use vigem.org: that domain was handed over, and old updaters pointing there are a documented risk. A reboot after installing the driver is not optional — complete it before retesting detection.

Check 6: Try the Other Connection Type

End the checklist by crossing over: if you have been testing over Bluetooth, test wired, and if you have been testing wired, test over Bluetooth (or on another USB port). This one comparison splits the problem in half. Detection over USB but not Bluetooth points at pairing, the adapter, or interference. Detection over Bluetooth but not USB points at the cable or the port. Detection on neither path, with Windows also seeing nothing, points at the controller itself — try it on another PC or console to confirm it still works.

Hardware Causes: Cable and Dongle

When the checklist points at hardware, replace the weak link rather than reinstalling software again. A short, proper data cable removes the most common wired failure, and a decent Bluetooth adapter placed close to your desk removes the most common wireless one.

Get a Data Micro-USB Cable on Amazon

Get a Bluetooth Dongle on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why does InputMapper say no compatible controllers detected?

InputMapper has not seen a supported controller in a usable state. The most common reasons are a charge-only USB cable that carries no data, a stale Bluetooth pairing, or the controller not appearing in Windows at all. Work through the cable, pairing, and joy.cpl checks in this guide in order.

Does InputMapper detect the DualSense or Switch Pro Controller?

No. InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices. The DualSense and Switch Pro Controller are not supported and will not be detected.

How can I tell if my USB cable carries data?

Test the cable by transferring a file to a phone or another device. If it only charges, it is a charge-only cable and a DualShock 4 connected with it will never appear in Windows or InputMapper, even though the light bar turns on.

What should I check if Windows sees the controller but InputMapper does not?

Restart InputMapper after the controller is already connected so its device list is rebuilt, connect only one controller while testing, and confirm ViGEmBus 1.22.0 is installed from GitHub releases with a reboot afterwards.

This guide works through the fixes in the order that solves the problem most often, starting with quick checks that take under a minute. If you are also seeing double inputs in games, see our double input fix as well.

What Exclusive Mode Actually Does

InputMapper takes a physical controller, most often a DualShock 4 or DualShock 4 V2, and presents it to Windows as a virtual Xbox 360 controller through the ViGEmBus driver. Games that expect an Xbox pad then work without any extra configuration. For that trick to work cleanly, the original physical controller has to be hidden from games. Otherwise the game sees both devices at once: the real DirectInput pad and the virtual XInput pad.

Exclusive mode is InputMapper’s attempt to claim the physical device for itself so other programs cannot read it directly. When it fails, InputMapper leaves the physical pad exposed, and any game that reads both input paths will double-register presses or pick the wrong device. Every step below is about removing whatever grabbed the controller first, or hiding it with a more modern tool.

Quick Check 1: Close Competing Apps First

The most frequent cause is another program opening the controller before InputMapper does. Steam is the best-known example, but game launchers, other controller tools, and even some web browsers with gamepad support can hold the device open. A controller can only be claimed exclusively by one program at a time, so whoever gets there first wins.

Close Steam completely, not just to the system tray. Do the same for other launchers you have running, and close browser tabs or windows if you have been testing your pad on a gamepad tester site. Disconnect any other controller software for the moment as well. Then restart InputMapper and reconnect the controller. In a large share of cases the error simply disappears, because nothing else is competing for the device anymore. Our dedicated guide to the InputMapper and Steam Input conflict explains the Steam side of this in more detail.

Quick Check 2: Start InputMapper Before Your Launchers

Order matters. If Steam or a launcher starts with Windows and grabs the controller at sign-in, InputMapper will lose the race every time, no matter how often you reconnect the pad. Get into the habit of starting InputMapper first, confirming the controller connects without the exclusive mode warning, and only then opening your launcher and game.

After a reboot, test this order once before changing deeper settings: fresh boot, InputMapper first, controller second, launcher third. Many users find the error never returns once the order is fixed.

Step 3: Toggle Exclusive Mode and Reconnect

If the error persists, open InputMapper’s settings and find the exclusive mode option. Turn it off, save, disconnect the controller, and close InputMapper. Then reopen InputMapper, turn exclusive mode back on, and reconnect the controller. Toggling the setting forces InputMapper to release any half-finished claim from the previous session and start the handshake again from a clean state.

While you are there, confirm you are connecting a supported controller. InputMapper officially supports the DualShock 4, DualShock 4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 and PlayStation Move Navigation controller via a Magic-NS dongle, and generic DirectInput and XInput devices. The DualSense and the Switch Pro Controller are not supported by InputMapper, and no setting will make exclusive mode work reliably with them. If you have a DualSense, you will need a different tool that supports it.

Step 4: Restart the Bluetooth HID Device

When the controller is connected over Bluetooth, the problem is sometimes a stale Bluetooth HID state rather than a competing app. Windows can hold on to an old pairing session in which the device was already opened by another service, and InputMapper then fails its exclusive claim against that leftover session.

Try this sequence. Turn the controller off and remove it from Windows Bluetooth settings. Restart the Bluetooth support service or toggle Bluetooth off and on. Then pair the controller again as a fresh device and start InputMapper before anything else. You can also test with a wired micro-USB connection: if exclusive mode works over USB but fails over Bluetooth, you have narrowed the problem to the Bluetooth path. Our Bluetooth pairing guide walks through clean pairing step by step.

Step 5: Run InputMapper as Administrator

Claiming a device exclusively requires more access than simply reading its inputs. If InputMapper is running with standard permissions while another service with higher privileges holds the controller, the claim can fail. Right-click the InputMapper shortcut and choose Run as administrator, then reconnect the controller and check whether the warning is gone.

If running as administrator fixes it, you can set the shortcut to always run with elevated privileges. Treat this as a diagnostic as much as a fix: it tells you the conflict was about access, not about a broken driver. If it makes no difference, move on rather than stacking more permission changes on top.

Step 6: Check for Legacy HidGuardian Leftovers

Older InputMapper setups relied on HidGuardian and HidCerberus to hide the physical controller. That stack dates from a 2016 to 2018 research project and has been archived for years. InputMapper 1.7-era installs even included a HidCerberus service. When parts of that legacy stack are left behind, half-installed, or configured for a device you no longer use, they can interfere with exclusive mode instead of helping it.

Do not install HidGuardian today to chase this error, and do not delete driver files at random. Check whether the legacy components are present, note their state, and read our comparison of HidGuardian vs HidHide before changing anything. The modern replacement does the same hiding job in a supported way, which leads to the most reliable long-term fix.

The Modern Route: Hide the Controller with HidHide

If exclusive mode keeps failing on Windows 10 or Windows 11, the durable solution is to stop relying on InputMapper’s own exclusive claim and hide the physical controller with HidHide instead. HidHide v1.5.230, released in May 2024 for Windows 10 and 11 on x64 systems, hides the physical controller from everything except the applications you whitelist. You whitelist InputMapper, cloak the DualShock 4, and games then only ever see the virtual Xbox controller that InputMapper creates.

This approach sidesteps the race entirely, because the hiding happens at the driver level before any launcher can grab the pad. Our full HidHide guide covers installation and the whitelist setup step by step. Once HidHide is configured, you can usually leave InputMapper’s exclusive mode setting as it is and simply enjoy a single, clean controller in every game.

What Not to Do

Search results for this error are full of random registry hacks and scripts that delete device keys. Avoid them. A registry value copied from a forum post can hide the wrong device or break Bluetooth for other hardware. There is no verified registry edit required to fix exclusive mode in InputMapper. Likewise, do not install driver packs from unofficial sites or download HidGuardian from third-party mirrors. Work through the steps above in order, change one thing at a time, and test after each change. If none help, browse our troubleshooting section before considering a full reinstall.

Frequently Asked Questions

Why does InputMapper say it failed to connect exclusively?

Another program usually opened the physical controller first, so InputMapper could not claim it exclusively. Steam, game launchers, other controller tools, and browser gamepad pages are the most common culprits. Close them, start InputMapper before your launchers, and reconnect the controller.

Can I ignore the exclusive mode error?

You can, but games may then see both the physical controller and the virtual Xbox controller at once, causing double inputs or the wrong device being selected. It is better to fix the cause or hide the physical controller with HidHide so only the virtual pad is visible.

Does exclusive mode work on Windows 11?

InputMapper runs on Windows 11, but it was never officially supported there because the final build dates from May 2020. Exclusive mode is less reliable on modern Windows, which is why hiding the controller with HidHide is the recommended long-term approach.

Should I install HidGuardian to fix exclusive mode?

No. HidGuardian is a legacy, archived project from 2016 to 2018 and should not be installed on modern Windows 10 or 11 systems. Use HidHide instead, which is the maintained successor for hiding the physical controller per application.

Double input is closely related to the exclusive mode failed error — when InputMapper cannot claim and hide the physical pad, double input is usually the result. Start there if you are seeing that warning, and use this guide to confirm the fix in your games.

How Double Input Happens

InputMapper reads your DualShock 4 or other supported controller and outputs a virtual Xbox 360 controller through ViGEmBus. That design only works if the original device is hidden. If the physical controller stays visible, a game can receive the same press from two different devices at the same moment. The game is not broken, and your controller is not faulty. Windows is simply presenting both devices, and the game is listening to both.

There are three distinct causes, and each has a different fix. First, the physical pad is not hidden at all. Second, Steam Input is mapping the controller on top of InputMapper’s mapping. Third, the game itself reads both XInput and DirectInput at the same time. Guessing wastes time, so spend two minutes on the triage below before changing settings.

Triage: Which Cause Do You Have?

Cause 1: The physical pad is not hidden

Disconnect from your game and open the Windows Game Controllers panel by running joy.cpl. With InputMapper running and your controller connected, look at the device list. If you can see both the physical DualShock 4 (often listed as a wireless controller) and the virtual Xbox 360 controller, the physical pad is not hidden. This is the most common cause, and the fix is the HidHide setup in the next section.

Cause 2: Steam Input is double-mapping

If double input only happens in Steam games, and especially if the doubling stops when you close Steam completely, Steam Input is the likely culprit. Steam’s built-in mapper can read the physical pad and translate it at the same time as InputMapper, producing two mapped outputs. The full walkthrough is in our guide to the InputMapper and Steam Input conflict, and the short version appears later in this guide.

Cause 3: The game reads both XInput and DirectInput

Some games, particularly older titles and some emulators, listen to XInput and DirectInput simultaneously by design. In those games the virtual Xbox pad and the physical pad both register even when everything else is configured correctly. The giveaway is that double input happens in one specific game while others are fine, and joy.cpl or other games show no problem. Hiding the physical pad with HidHide still solves this case, because there is then only one device left for the game to read.

The Main Fix: Hide the Physical Pad with HidHide

HidHide is the modern tool for this job. HidHide v1.5.230, released in May 2024 for Windows 10 and 11 on x64, hides a physical controller from every program except the ones you whitelist. It replaces the legacy HidGuardian and HidCerberus stack from 2016 to 2018, which is archived and should not be installed today. Our step-by-step HidHide guide has the full setup, and the summary below is enough to fix double input in most cases.

Step 1: Whitelist InputMapper

Install HidHide and open its configuration client. On the Applications tab, add InputMapper’s executable to the whitelist. This step is essential and the order matters: InputMapper must be allowed to see the physical controller, because it is the program that reads it and creates the virtual pad. If you cloak the device before whitelisting InputMapper, InputMapper will lose sight of your controller too. That outcome looks alarming but is easy to reverse by unticking the cloak, adding the whitelist entry, and cloaking again.

Step 2: Cloak the DualShock 4

On the Devices tab, find your physical controller and tick the option to hide it, then enable device hiding. From this moment, games and launchers can no longer see the physical pad at all. Only whitelisted applications, which in this setup means InputMapper, retain access. Restart InputMapper if it was already running so it picks up the new state cleanly, and reconnect the controller if prompted.

Step 3: Verify with joy.cpl

Open joy.cpl again. You should now see only the virtual Xbox 360 controller in the list for normal applications, while InputMapper still shows your physical controller in its own device list. Press a few buttons in the Game Controllers test screen and confirm each press registers once. Then launch the game that was doubling and test the menus, which is where double input is easiest to spot. One press should move one entry. If it does, the fix is complete and will survive reboots, because HidHide reapplies the cloak automatically.

If Steam Is the Cause

When the triage points at Steam, open Steam settings and turn off PlayStation Configuration Support, which is the classic switch that makes Steam grab PlayStation controllers. For individual games, open the game’s properties in your library, go to the Controller section, and set Steam Input to Forced Off so that game uses InputMapper’s virtual pad only. Also check Big Picture controller settings, because a configuration enabled there can apply even when you launch games from the desktop client.

Test with one game before changing your whole library. If Forced Off removes the doubling in that title, apply the same per-game setting to other affected titles. Remember that turning Steam Input off for a game means that game relies entirely on InputMapper, so keep InputMapper running before you launch it. The reverse situation, where Steam Input alone is the better tool, is covered in our comparison of InputMapper vs Steam Input.

If One Game Still Doubles

For a single stubborn game that reads both input paths, first confirm the HidHide cloak is active and joy.cpl shows only the virtual pad. If the game still doubles, check whether the game has its own controller settings that select a specific device, and point it at the Xbox 360 controller explicitly. Some games also store a device choice in their configuration from before your fix, so reselecting the controller inside the game can be necessary even after Windows is correct.

Also test the game with the controller connected by USB if you normally play over Bluetooth, and the other way around. A game that behaves differently per connection type is telling you the physical device is still visible on one path, which sends you back to the HidHide checks rather than to the game’s settings. Do not respond by installing additional mapping tools on top of InputMapper. Stacking mappers almost always makes double input worse, not better.

Keeping the Fix in Place

Once double input is gone, leave the setup alone. Keep InputMapper as your only mapper for this controller, keep HidHide’s whitelist limited to InputMapper and any other tool you deliberately use, and start InputMapper before your launchers. If you later add a new controller, remember that InputMapper supports the DualShock 4, DualShock 4 V2, Xbox 360, Xbox One, DualShock 3 via Magic-NS, and generic DirectInput and XInput devices, but not the DualSense or Switch Pro Controller. A new unsupported pad will need a different tool rather than more InputMapper settings. More fixes live in our troubleshooting hub, and general questions are answered in the InputMapper FAQ.

Frequently Asked Questions

Why is my controller pressing buttons twice in games?

Your game is seeing both the physical controller and the virtual Xbox controller created by InputMapper, so each press arrives twice. Hide the physical controller with HidHide, whitelisting InputMapper so it can still read the pad, and verify in joy.cpl that only the virtual controller is visible.

How do I check if my physical controller is hidden?

Run joy.cpl to open the Windows Game Controllers panel. With InputMapper running, you should see only the virtual Xbox 360 controller listed. If the physical DualShock 4 also appears, it is not hidden and games can read it directly.

Can Steam cause double input with InputMapper?

Yes. If Steam Input maps the controller at the same time as InputMapper, the game receives two mapped outputs. Turn off PlayStation Configuration Support in Steam settings, or set Steam Input to Forced Off for the affected game in its library properties.

Is HidGuardian still the right tool to hide my controller?

No. HidGuardian is a legacy project from 2016 to 2018 that has been archived. HidHide v1.5.230 is the modern successor: it hides the physical controller per application through a whitelist and is the recommended fix for double input on Windows 10 and 11.

Before changing anything here, make sure the controller pairs and stays connected in Windows itself using our Bluetooth pairing guide and the setup steps in connecting a PS4 controller to PC. If the pad will not pair at all, that is a detection problem, not a lag problem.

First, Confirm It Is Really the Bluetooth Link

Play the same game, in the same room, with the controller connected by a micro-USB data cable for ten minutes. If the lag and disconnects disappear completely on USB, your InputMapper profile, ViGEmBus, and the game are all fine, and the fault is isolated to the wireless path. If problems continue even wired, stop here and check the broader fixes in our troubleshooting hub instead, because no dongle placement will cure a problem that also happens on a cable.

Also note when the dropouts happen. Disconnects that arrive after a predictable idle period point at power management. Lag that spikes when other devices are active, or when you plug something in, points at interference. Random dropouts at any moment, getting worse the further you sit from the PC, point at range. Each pattern has its own fix below.

Cause 1: Interference from USB 3.0 Ports and Hubs

The most overlooked cause of Bluetooth controller lag is USB 3.0 interference. USB 3.0 ports, cables, and external drives emit radio noise in the same 2.4 GHz band that Bluetooth uses. A Bluetooth dongle plugged in right next to an active USB 3.0 port or hub — the classic setup on the back of a PC — can be drowned out by its neighbours, producing exactly the stutter and sudden disconnects users blame on InputMapper.

Move the Bluetooth dongle away from USB 3.0 devices. Unplug nearby USB 3.0 hubs and external drives for a test session and see if the connection stabilises. Keep the dongle out of a cluster of cables at the back panel if you can. Many users are surprised that simply relocating the dongle, without changing a single setting, ends months of intermittent lag.

Cause 2: Dongle Placement — Use a USB 2.0 Extension

Placement is the companion fix to interference. A dongle buried at the back of a metal PC case, under a desk, has both a weak signal and a blocked one. Bring the dongle up and out: plug it into a short USB 2.0 extension cable and position it on top of the desk or the case, with a clear view towards where you sit.

USB 2.0 is specified deliberately here. An extension also moves the dongle away from the noisy USB 3.0 ports at the back panel, solving both problems with one cheap cable. After repositioning, retest in the same game and seating position as before so the comparison is fair. If lag drops sharply, leave the extension in place permanently rather than treating it as a temporary diagnostic.

Cause 3: Power Management Turning the Adapter Off

Windows can power down the Bluetooth adapter to save energy, and when it does, connected controllers lag or vanish. Open Device Manager, find your Bluetooth adapter, open its Properties, and go to the Power Management tab. Untick “Allow the computer to turn off this device to save power” and apply the change.

While you are in Device Manager, check any related USB hub entries for the same setting if disconnects continue, since the adapter may sit behind a hub that is itself being powered down. This fix is especially relevant on laptops and on desktops using aggressive power plans. After changing it, play for a full session, including a pause where the controller sits idle, because idle-period disconnects are the signature of this cause.

Cause 4: Distance and Line of Sight

Bluetooth range figures assume open air. In a real room, walls, metal furniture, aquariums, and even your own body between the pad and the dongle all weaken the signal. If your PC is across the room, under a desk, or in a cabinet, you may simply be at the edge of a usable link, and the connection will degrade gradually rather than failing outright.

Test by playing close to the PC for one session. If everything is smooth nearby and rough from the sofa, the answer is geometry, not drivers: reposition the dongle on its extension towards your seating, move the PC out of its cabinet, or accept a wired connection for that setup. Also reduce competing 2.4 GHz traffic where you can during the test — the fewer devices shouting in the same band, the easier it is to judge the improvement.

Final Step: Re-pair Cleanly

If the link is still unstable after placement and power fixes, remove the pairing entirely and start again. In Windows Bluetooth settings, remove the controller, restart Bluetooth, charge the controller fully, and pair it again while sitting close to the dongle in its new position. A pairing created while the signal was weak or interrupted can behave badly for its whole lifetime, and a clean re-pair costs only a minute.

After re-pairing, open InputMapper, confirm the controller is listed, and test in a game before reopening other launchers. Keep the setup notes simple: what you moved, which checkbox you cleared, and whether the re-pair helped. That record stops you repeating the same experiments next time the setup changes.

Better Hardware for Stubborn Setups

If your adapter is very old, built into a crowded rear panel, or simply weak, a replacement dongle on an extension is often the end of the story. These are the options we point readers to for this exact problem.

See UGREEN Bluetooth Adapters

Get a Bluetooth Dongle on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why does my controller lag over Bluetooth but not on USB?

Because the problem is in the wireless path, not in InputMapper. Interference from nearby USB 3.0 ports and hubs, a dongle hidden behind the PC case, power management putting the adapter to sleep, and distance or obstructions are the usual causes. The wired test confirms the software side is fine.

Can USB 3.0 devices really interfere with Bluetooth?

Yes. USB 3.0 ports, cables, and drives emit noise in the same 2.4 GHz band Bluetooth uses. A dongle plugged in beside an active USB 3.0 hub can stutter or disconnect. Moving the dongle away, ideally onto a USB 2.0 extension on your desk, is a well-established fix.

Which power setting causes Bluetooth disconnects?

In Device Manager, open your Bluetooth adapter’s Properties and the Power Management tab. If “Allow the computer to turn off this device to save power” is ticked, Windows can sleep the adapter mid-session. Unticking it stops idle-period disconnects.

Should I re-pair the controller or replace the dongle first?

Re-pair first, after fixing placement and power management, because it is free and quick. Replace the dongle only if a clean pairing in a good position with power saving disabled still drops out, or if the adapter is old and weak.

If you only need the short comparison, see HidGuardian vs HidHide. This page is the longer safety and migration walkthrough, including the precautions to take before touching any driver.

Why Users Fear HidGuardian

HidGuardian is a kernel-level filter driver, and that category of software deserves respect. A filter driver sits in the device stack and decides which programs can see which human interface devices. When it works as configured, it hides selected controllers from selected programs. When it is misconfigured — in particular, when its AffectedDevices configuration lists devices badly or is left behind after the tools that managed it are gone — devices can be hidden from everything, including the programs you actually want to use.

That failure mode explains most of the fear. A controller that vanishes from every app looks like broken hardware. Add the general anxiety that any kernel driver can, in principle, be involved in a blue screen when it conflicts with other drivers or a Windows update, and the reputation follows. None of this means HidGuardian was malware — it was not — but it does mean an unmanaged leftover copy on a modern system is a legitimate thing to clean up, carefully and in the right order.

What HidGuardian Actually Was

HidGuardian, together with its companion service HidCerberus, was the controller-hiding stack used in the InputMapper 1.7 era. It came out of a research project that ran from 2016 to 2018 and has been archived ever since. InputMapper 1.7-era installs even included the HidCerberus service component, which is why so many long-time InputMapper users have these names on their systems without ever having installed them separately.

Its job was narrow: hide the physical controller so that only InputMapper could read it, while games saw only the virtual Xbox controller. That job is still necessary today. What has changed is the tool: the maintained successor is HidHide, currently at version 1.5.230 from May 2024, built for Windows 10 and 11 on x64, which hides a physical controller per application through a simple whitelist. The concept survived; the implementation moved on. Our HidHide guide covers the successor in full.

Why You Should Not Install It Today

Do not install HidGuardian on a current Windows 10 or 11 system, even if an old tutorial tells you to, and even if a download for it is easy to find. The project has had no maintenance since its research period ended, it was never built for today’s Windows versions, and the hiding task it performed is now done better and more safely by HidHide, with a configuration app that shows you exactly what is hidden and which programs are whitelisted.

This advice applies especially to users who arrive here from an exclusive mode or double input error. Installing an archived kernel driver to fix a configuration problem adds risk in exactly the wrong direction. The modern route for both problems is HidHide, covered in our double input fix and the migration path below.

How to Check If HidGuardian Is Installed

Start by looking, not by removing. Check your installed programs list for HidGuardian or HidCerberus entries. Look in Windows Services for a HidCerberus service, which InputMapper-era installs included. In Device Manager, with hidden devices shown, you may also see the filter associated with game controller devices on systems where it was active.

Write down what you find before changing anything: which components are present, whether the service is running, and whether your controller currently behaves normally. If your setup works today, there is no emergency. Plan the migration for a moment when you can test calmly afterwards, rather than ripping out a driver minutes before you want to play.

Safe Migration Path to HidHide

Step 1: Create a restore point first — mandatory

Before uninstalling or disabling any part of the legacy stack, create a Windows restore point manually and confirm it completed. Also back up anything you are about to change. This step is not optional boilerplate. A restore point is what turns a migration mistake from a recovery project into a five-minute rollback, and it is the single most valuable precaution in this entire guide.

The same caution applies to the registry. Back up before any change, work only from a restore point you have just created, and do not edit values you cannot identify. If a forum post tells you to delete device keys or rewrite HidGuardian’s configuration by hand and you cannot clearly identify every value involved, stop and use the uninstall route instead. There is no step in this migration that requires blind registry editing.

Step 2: Uninstall or disable the legacy stack in order

Remove the legacy stack through normal Windows uninstall routes, in order: stop and remove the HidCerberus service component first if it has its own entry, then uninstall HidGuardian itself, then reboot. Rebooting matters because filter drivers unload during a restart; testing before the reboot can show you a half-migrated state that looks like a new problem. After the reboot, confirm your controller appears normally in the Windows Game Controllers panel (joy.cpl) with no hiding active.

If an uninstall entry is missing and a component appears stuck, do not escalate to manually deleting driver files from system folders. Use the restore point you created if the system misbehaves, and consult our troubleshooting hub for related symptoms before trying more invasive steps.

Step 3: Install HidHide

With the legacy stack gone and the controller visible and working, install HidHide from its GitHub release using the button below.

Download HidHide on GitHub

Affiliate link — see our Affiliate Disclosure.

Then configure it in the order our HidHide guide sets out: whitelist InputMapper first, then cloak the physical controller, then enable hiding. Whitelisting first is what guarantees InputMapper keeps sight of the pad it needs to read.

Step 4: Verify the result

Open joy.cpl: normal applications should now see only the virtual Xbox 360 controller, while InputMapper still lists your physical controller. Start InputMapper, confirm your profile loads, and test one game that previously showed double input or exclusive mode trouble. If the controller instead disappears from InputMapper itself, you cloaked before whitelisting — untick the cloak, add InputMapper to the whitelist, and cloak again. When the test game plays cleanly, the migration is complete and your hiding setup is on maintained software.

Frequently Asked Questions

Can HidGuardian cause a blue screen?

HidGuardian is a kernel filter driver, and any kernel driver can be involved in a blue screen if it conflicts with other drivers or system changes. The more common problem is misconfiguration: a badly set AffectedDevices list can hide devices from everything. Either way, the safe response is a planned migration to HidHide, not panic removal.

Is HidGuardian malware?

No. HidGuardian and HidCerberus were the legitimate controller-hiding stack of the InputMapper 1.7 era, from a 2016 to 2018 research project that has since been archived. It is obsolete rather than malicious, and InputMapper-era installs included the HidCerberus service.

How do I know if HidGuardian is on my PC?

Check your installed programs for HidGuardian or HidCerberus entries, and look in Windows Services for a HidCerberus service. Note what is present and whether your controller works normally before changing anything, and create a restore point before any removal.

What replaces HidGuardian for InputMapper today?

HidHide v1.5.230 is the modern successor. It hides the physical controller per application through a whitelist: you whitelist InputMapper, cloak the controller, and games then see only the virtual Xbox controller, without the legacy stack.