You double-click InputMapper and nothing happens, or the window flashes and closes, or the program crashes a few seconds after starting. A mapper that will not open gives you very little to go on, so this guide works from the outside in: the runtime it needs, the permissions it starts with, the security software that can block it, and finally a clean reinstall in the correct order.
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.