HidGuardian has a reputation that makes users nervous: forum posts blame it for hidden controllers, missing devices, and blue screens, and anyone who finds it on their system while troubleshooting InputMapper understandably wants to know whether it is dangerous and whether it should be removed. This guide explains calmly what HidGuardian actually was, why you should not install it today, how to check whether it is on your PC, and how to migrate safely to its modern successor, HidHide.
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.
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.