vJoy Failed to Install on Windows 11: Use the Signed Build

If vJoy failed to install on Windows 11, the most likely explanation is also the simplest: the build you tried predates Windows 11. vJoy has had several maintainers, and their builds do not carry the same Windows support or the same signing. This guide explains which build is documented for Windows 11, why the older builds struggle, and the exact order to install in so you are not troubleshooting a build that was never the right choice.

The symptom

On Windows 11 the failure usually looks like an installer that rolls back, a driver that installs files but never loads, or an install that seems complete until you open joy.cpl and find no vJoy Device. Because Windows 11 is stricter about driver signing than the Windows versions the original vJoy line was built for, a build that worked for years on an older system can fail here without anything else being wrong with your PC.

Why it happens: the build timeline

The original vJoy line by Shaul Eizikovich ends at version 2.1.9.1. In the author’s own words, that build is attestation-signed for Windows 10. About Windows 11 the author said only, in 2022, words to the effect of hearing that it is working. That is anecdotal, not a support claim: 2.1.9.1 often works on Windows 11, but it is not guaranteed, and its attestation signing is Windows 10-only. The njz3 2.2.1.1 build is a signed fork focused on force feedback, and njz3’s own README now points Windows 11 users to the newer build below. The BrunnerInnovation 2.2.2.0 build, released on 19 December 2023, is signed with an EV certificate with attestation signing via the Microsoft Partner program, and it is the only build that explicitly claims support for both Windows 10 and Windows 11. It supports Windows 10 and 11 only.

The fix: install the signed 2.2.2.0 build cleanly

  1. Remove what is already there. Uninstall every existing vJoy entry in Settings, Apps. If you have tried more than one build, follow our complete uninstall guide, including checking the driver store with pnputil -e for leftover Shaul or vJoy entries, so the new install starts clean.
  2. Restart Windows. Driver changes that have not been through a reboot are a common reason a correct install still looks broken.
  3. Download the BrunnerInnovation 2.2.2.0 installer from our download vjoy page. The verified file is vJoySetup_v2.2.2.0_Win10_Win11.exe, 5,302,312 bytes, SHA-256 ef569a3105cd301b89580f18f60c66b339e95296acf2c0dfcaf4b4bbf8ab68fe. Checking the hash confirms the file you run is the file that was verified.
  4. Run that one installer, and no other vJoy installer in the same session. Let it finish, then reboot again if prompted.
  5. Open joy.cpl and confirm a vJoy Device is listed, then open Configure vJoy to confirm it opens without an error.

A conditional note on Memory Integrity

If Windows lists vjoy.sys on its incompatible-drivers screen under Core Isolation, that is a separate, conditional situation covered in our Core Isolation guide. There is no authoritative vJoy-specific source that establishes how Memory Integrity interacts with every vJoy build, so this guide does not present it as the default cause of a Windows 11 install failure, and it does not tell you to turn security features off as a first step. The documented first move on Windows 11 is the build swap above: remove the pre-Windows 11 build and install the build that is signed and documented for Windows 11. Only if a clean 2.2.2.0 install still fails should you read the logs described in our general install-failure guide and consider the conditional checks.

When to use an older build instead

There is one honest exception. At least one feeder vendor documents the 2.2.x line as only partially supported, so if your feeder misbehaves on 2.2.2.0, the original 2.1.9.1 build is the compatibility fallback. That is a feeder-compatibility decision, made after the driver itself installs and loads, not a reason to start with 2.1.9.1 on Windows 11. And if you do fall back, do it as a clean swap: uninstall 2.2.2.0 fully, reboot, then install 2.1.9.1 alone. Two builds installed together create the version conflicts covered elsewhere in this troubleshooting section.

How to confirm it is fixed

  1. joy.cpl lists at least one vJoy Device on Windows 11.
  2. Configure vJoy opens and lets you view and change the device configuration.
  3. Your feeder application connects without a driver-not-enabled or version-mismatch error.
  4. After a full reboot, the device is still present. A device that only appears until the next restart was never fully fixed.

If all four checks pass, your Windows 11 install problem was the build, which is the outcome most readers of this page should expect. If a clean 2.2.2.0 install still does not produce a device, keep the installer logs and continue with the general failed-to-install guide, which starts from those logs.

One last habit worth adopting once Windows 11 accepts the build: record what you installed. Note the build number, the installer file name, and where you downloaded it from, and keep that note with the rest of your simulator or controller setup. If a future Windows update, feeder change, or hardware swap ever makes the device disappear again, that record turns a fresh mystery into a five-minute comparison, because you will know exactly which signed build was working on this machine.

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