Which vJoy Build Should You Download? 2.2.2.0 vs 2.2.1.1 vs 2.1.9.1
Which vJoy build should you download is the first real decision in any vJoy setup, and the internet makes it harder than it needs to be by treating three different releases, from three different maintainers, as if they were interchangeable files with the same name. They are not. This page lays out the lineage honestly, gives you a decision table based on your operating system, force feedback needs and feeder compatibility, and lists the verified file sizes and SHA-256 hashes for all three builds so you can prove the file on your disk is the file this page is talking about. Decide here once, then install with confidence.
The lineage in one paragraph
vJoy began with Shaul Eizikovich. The original line ended at 2.1.9.1, attestation-signed for Windows 10, with the same file distributed through SourceForge and the jshafer817 GitHub asset. Benjamin, known as njz3, then forked the code to work on force feedback, producing the signed 2.2.1.1 release with multi-device FFB fixes. BrunnerInnovation followed with 2.2.2.0 in December 2023, the newest release of all, signed with an EV certificate and attestation signing, and the only build that explicitly claims both Windows 10 and Windows 11 support. Newer number does not automatically mean right for you, but now you know who made each build and why it exists.
The decision table
| Your situation | Recommended build | Why |
|---|---|---|
| Windows 11, new install | 2.2.2.0 | Only build explicitly claiming Win11 support, EV and attestation signed |
| Windows 10, new install | 2.2.2.0 | Newest maintained line, also the safe choice before a Win11 upgrade |
| Force feedback is central | 2.2.1.1 | njz3 fork built for FFB, including multi-device fixes |
| Feeder misbehaves on 2.2.x | 2.1.9.1 | Compatibility fallback; some feeders only partially support 2.2.x |
| Windows 10, existing stable setup | Stay, or 2.2.2.0 | 2.1.9.1 is attestation-signed for Win10; change only with a reason |
Two rows deserve emphasis. The Windows 11 row is not a preference: njz3’s own README directs Windows 11 users to BrunnerInnovation 2.2.2.0, which tells you how the maintainers themselves see the tracks. The fallback row is equally real: at least one feeder vendor, TJoy, documents 2.2.x as only partially supported, so a feeder that works perfectly on 2.1.9.1 and misbehaves on 2.2.x is giving you information, not an error to fight. Choose the build your feeder supports, and let operating system decide only among the builds your feeder tolerates.
Verified files and hashes
| Build | File | Size | SHA-256 |
|---|---|---|---|
| 2.2.2.0 | vJoySetup_v2.2.2.0_Win10_Win11.exe | 5,302,312 B | ef569a3105cd301b89580f18f60c66b339e95296acf2c0dfcaf4b4bbf8ab68fe |
| 2.2.1.1 | vJoySetup-2.2.1-signed.exe | 9,761,336 B | 0c599290da9ab17ed189deb1db20d8bb2688d15173fe464d485c203032eeef8d |
| 2.1.9.1 | vJoySetup.exe | 11,482,272 B | f103ced4e7ff7ccb49c8415a542c56768ed4da4fea252b8f4ffdac343074654a |
These hashes were verified from the actual upstream files. Download from the vJoy download page, compare the size first because it is instant, and compare the SHA-256 when the choice matters, which for a kernel driver is always. A mismatch means the file is not the release in this table, whatever its name claims. Replace it rather than installing it. Note also what no build in this table does: none of them emulates XInput, and all of them present DirectInput devices that a feeder must write to. Build choice changes signing, vintage and force feedback work, not that fundamental model.
Not this vJoy: the Headsoft disambiguation
One confusion poisons search results and must be separated out. Headsoft VJoy is a different product by a different author, Ben Baker. It is version 1.2, it ships alongside FaceTrackNoIR, and it offers a much smaller device, described as 2 devices with 32 buttons. It shares a name with the vJoy this site covers and almost nothing else: different author, different code, different capabilities, different purpose. If a guide mentions FaceTrackNoIR bundles or a 1.2 version number, it is talking about Headsoft’s tool, and its instructions, downloads and limits do not apply to the Shaul-lineage vJoy in the table above. Check which product a page means before following it, especially when a download is involved.
Licence, stated carefully
You will see confident one-word licence claims about vJoy around the internet. Resist repeating them. The sources conflict: SourceForge lists the project as Public Domain, while the GitHub repositories carry MIT tags. The honest statement is that qualified picture, and it is what this site publishes. Anyone who tells you a single tidy licence label for every vJoy distribution is simplifying past the evidence. For practical purposes the builds above are free to download and use from their upstream sources, and the hashes in this guide let you be certain you have those exact releases.
Frequently asked questions
I am on Windows 11 and my feeder is old. Which risk do I take? Install 2.2.2.0 first because it is the signed Windows 11 build, test the feeder thoroughly in JoyMonitor, and fall back to 2.1.9.1 only if the feeder demonstrably misbehaves. Can I install two builds side by side? No. One driver is installed at a time; switching means uninstall, reboot, install. Is 2.2.1.1 newer than 2.1.9.1 but older than 2.2.2.0? Yes, that is the order, and the middle build exists for its force feedback work rather than as a general stepping stone. What about even older versions? The 2.1.8 line served Windows 7 through Windows 10 version 1803 and belongs in an archive, not on a current machine.
Keep going
Start from the vJoy download page if you need the installer again, and use the vJoy Setup hub as the index for this whole cluster. Two guides that pair naturally with this one are How to Install vJoy on Windows 11 and How to Install vJoy on Windows 10. Read them in that order if you are building a setup from scratch: download choice first, installation second, configuration third, and only then time inside a game or simulator. That order prevents the most common wasted hour in this niche, which is debugging a feeder or a game for a driver problem that was visible in Windows all along.