vJoy Failed to Install: Causes and Fixes

If vJoy failed to install, do not keep re-running the same installer and hoping for a different result. A failed install almost always leaves a trace you can read, and the original author told users exactly where to look. This guide works through the symptom, the verified causes, a step-by-step fix in a safe order, and how to confirm the driver is really installed before you move on to configuring devices or launching a game.

vJoy is a Windows virtual joystick driver. A feeder application writes data to it through vJoyInterface.dll, and games then see a DirectInput joystick. If the driver itself never finishes installing, nothing downstream can work: there will be no device in joy.cpl, no response in vJoy Monitor, and every feeder will report that the driver is not enabled. Fixing the install first saves you from chasing feeder and game settings that were never the problem.

What the symptom looks like

Install failures show up in a few recognisable ways. The installer may roll back or close without a clear message. It may appear to finish, yet no vJoy Device appears afterwards. Or a previous attempt may have half-installed, so the next attempt complains, behaves inconsistently, or installs files that do not match each other. Treat all three patterns as the same underlying job: find out what the last attempt actually did, remove leftovers cleanly, and install one build, once, on a clean base.

Why it happens: verified mechanisms

Only a small set of mechanisms is documented for vJoy install trouble, and this guide sticks to those. First, leftover installs: an earlier build, or an earlier failed attempt, can leave driver files and driver-store entries behind, and mixed files from different releases are a known source of failures. Only one vjoy.sys driver can run, so remnants matter. Second, running more than one build: installing the original 2.1.9.1 line, the njz3 2.2.1.1 fork and the BrunnerInnovation 2.2.2.0 build over each other does not give you three options, it gives you a conflict. Third, a partial install: if an attempt was interrupted, the files on disk and the driver state can disagree, which is why later checks fail. Finally, the build itself may simply not fit your Windows version, which is covered in detail in our Windows 11 install guide.

Step 1: read the install logs first

Before changing anything, read the logs. This is not generic advice: the original author, Shaul Eizikovich, directed users troubleshooting an install failure to check the Setup Log in %TEMP% together with C:\Program Files\vJoy\vJoyInstall.log. Those two files are the closest thing vJoy has to an official account of what the installer did.

  1. Press Windows + R, type %TEMP%, and open the most recent Setup Log file from around the time of your failed attempt. Note any error or rollback lines near the end of the file.
  2. Open C:\Program Files\vJoy\vJoyInstall.log if the folder exists, and read the tail of the file. If the folder does not exist at all, that itself tells you the install never got far enough to lay down its files.
  3. Write down exactly what the log says. If you later ask for help in a project repository or forum, paste the relevant log lines instead of only saying it failed to install. Helpers can do far more with a log excerpt than with a summary.
  4. Do not delete the logs before a clean reinstall. If the clean attempt also fails, comparing the two logs shows whether you are hitting the same point or a new one.

Step 2: remove leftover installs

With the log read, clear the ground. Uninstall every vJoy entry you find in Windows Settings, Apps, then restart. If installs were mixed or a normal uninstall does not clear the problem, follow the full documented cleanup in our uninstall guide: uninstall, inspect the driver store with pnputil -e for Shaul or vJoy OEM INF entries, remove only those entries with pnputil -f -d oemXX.inf using the exact INF name you found, then reboot. Never guess an oem number, and never remove driver-store entries that belong to other hardware. The driver store step exists because a normal uninstall can leave the driver package behind, ready to be reloaded on the next attempt.

Step 3: install one build only

Now install exactly one build that matches your system. For most readers on Windows 10 or Windows 11, that is the BrunnerInnovation 2.2.2.0 build, which is signed with an EV certificate with attestation signing via the Microsoft Partner program and explicitly states that it works on Windows 10 and Windows 11. If a feeder you depend on misbehaves on the 2.2.x line, the documented compatibility fallback is the original 2.1.9.1 build, which is attestation-signed for Windows 10. The njz3 2.2.1.1 build is the signed force-feedback fork. Pick one, install it, reboot if prompted, and resist installing a second build to compare: comparison is what created many of the conflicts this page fixes. Get the file from our download page, where each build lists its size and verified SHA-256 hash.

How to confirm it is fixed

  1. Open joy.cpl from Windows search or the Run box and confirm at least one vJoy Device is listed.
  2. Open Configure vJoy (vJoyConf) and confirm it opens without a driver-not-enabled error and shows your device configuration.
  3. Check that C:\Program Files\vJoy\ exists and that vJoyInstall.log now records a completed install rather than a rollback.
  4. Only then start your feeder application and confirm, in vJoy Monitor or in the feeder itself, that moving your input moves the virtual axes.

If joy.cpl shows the device and a feeder moves the axes, the install is fixed. If the device is missing, work through our joy.cpl checklist next rather than reinstalling a third time. If the installer still fails on a clean base with the correct build, keep both logs: at that point the log content, not another blind retry, is what will identify the blocker.

Related guides

vJoy is an unofficially documented tool on this site. vJoy itself was created by Shaul Eizikovich, with later signed forks by other maintainers. This site is not the official vJoy project site.

Similar Posts