Download InputMapper v1.7.7452 Stable

Mirror hosted for this site: Terabox mirror — the same file; verify the checksum either way.

Mirror hosted for this site: Terabox mirror — the same file; verify the checksum either way.

Step 1: Install ViGEmBus

Run the ViGEmBus driver setup file first. This system extension needs to settle inside your Windows hardware profiles to build the virtual controller channel before InputMapper boots up.

Step 2: Restart Your PC

Perform a full operating system reboot. This gives Windows a chance to register the virtual controller bus driver correctly and prevents unexpected hardware matching failures.

Step 3: Run InputMapper Setup

Launch the main InputMapper v1.7.7452 setup installer. Follow the on-screen configuration prompts to unpack the core profile files and map tools into your Program Files directory.

Step 4: Connect Gamepad

Plug in your controller via USB or connect over Bluetooth. Open InputMapper with Administrator privileges, assign your new profile, and start mapping your inputs.

The last build of the 1.7 line; its build number decodes to May 2020. No official changelog survives — the original project site is gone — so instead of invented release notes, here is what can actually be verified about this build:

• File name: InputMapper1.7.7452.13622.exe — 72.2 MB.
• MD5 1b166e39787476748358cca460fe4225 — the FileHorse and FileCroco listings agree.
• SHA-256 ef06918e…e02608 — verified by direct download on 2026-10-23 (see the download card above).

An earlier 1.7 build, decoded to January 2020 and recorded in software uninstall databases. Superseded by 1.7.7452.13622 — there is no reason to run it today.

• Part of the 1.7 line, which outputs through ViGEmBus (the earlier 1.5 and 1.6 lines used ScpVBus instead).

The 1.6 line (up to 1.6.10.19991) used the ScpToolkit ScpVBus driver instead of ViGEmBus, on the Windows 7/8-era stack.

• Known issue: a buffer-overflow vulnerability in build 1.6.10 is recorded as CVE-2019-25464.
• Legacy builds are listed for reference only — we offer no downloads for them.

📡 Wireless Bluetooth Sync

1. Open your Windows system settings dashboard and navigate to Bluetooth & Devices. Ensure your PC’s transceiver is activated.
2. Pick up your DualShock 4 controller. Hold the Share Button and the PlayStation (PS) Button down simultaneously for 3 to 5 seconds.
3. Release the inputs when the rear lightbar transitions into a rapid, rhythmic double-strobe white blinking pattern.
4. On your desktop panel, select Add Device → Bluetooth, select the detected “Wireless Controller” profile, and let the software sync finish.

🔌 Secure Tethered Wired Sync

1. Acquire a premium data-compliant Micro-USB cable. Avoid low-grade charging cables which fail to pass peripheral input data packets.
2. Plug the connection cable directly into an available onboard USB 2.0 or USB 3.0 controller node port on your computer’s motherboard chassis.
3. Connect the adapter link directly into the controller slot. Windows will chime and configure a generic DirectInput audio/peripheral device automatically.
4. Launch your freshly downloaded InputMapper setup file to take command of the link pipeline and shift input routing rules to XInput status.

Why does Windows SmartScreen block the InputMapper .exe file?

Because the core InputMapper v1.7.7452 executable hasn’t received a renewed commercial digital certificate signature from the original developer team since development concluded, Windows flags it as an “unknown publisher.” If you verified the file’s SHA-256 hash checksum on our module, click “More Info” and select “Run Anyway” to bypass the security wall safely.

What happens if I skip downloading the ViGEmBus Driver package?

Skipping the driver installation causes the application to launch successfully, but it will display an error message stating “Virtual Bus Not Found” or fail to recognize your controller profiles. InputMapper lacks an internal virtualization driver engine; it relies completely on the external ViGEmBus package to bridge its signals with your Windows architecture.

Does this standalone package download require internet access to install?

No. The installers are standalone setup packages. Your system does need a .NET Framework 4.x runtime present; if it is missing, Windows may offer to fetch it from Microsoft, which requires an active internet connection.