FakerInput: keyboard and mouse mapping

FakerInput is an optional virtual keyboard/mouse driver used by supported DS4Windows builds.

Start with ordinary mappings

Create a simple test profile and map one button to a key. Test in a normal text editor before changing driver configuration. If the key arrives there but not in a game, investigate that game’s input support, privilege level and rules.

When the driver may help

Some applications handle ordinary injected keyboard events differently from hardware-style input. A compatible FakerInput path can address particular input-method limitations. It cannot guarantee acceptance by every application or override game restrictions.

Install deliberately

Check that your DS4Windows edition supports the FakerInput release you intend to install.
Use the app setup option or the project release page.
Close remapping applications and complete the driver installation.
Restart if requested, reopen the app and check its input-method status or log.
Retest the same single-button mapping before adding macros or mouse controls.

Avoid permission guessing

Running every program as administrator is not a general fix. Use normal privileges for routine play. If a target application is elevated, understand the privilege mismatch before deciding how to run your remapper. Check competitive-game policies before using automated actions.

Remove it when no longer needed

Uninstall the driver through Windows Installed apps after closing dependent tools. Removing it can stop keyboard/mouse mappings in another remapper that uses the same driver. Keep virtual controller troubleshooting separate.

Sources: FakerInput project · Project and screenshot credits. Updated 11 November 2026.