How to Install vJoy on Windows 10
Windows 10 is the easiest platform for vJoy because all three current builds can work there. That freedom is useful, but it also creates the main Windows 10 mistake: installing whichever file you find first, then discovering later that your feeder or your force feedback hardware needed a different build. This guide explains how to choose deliberately, how to install cleanly, and how to prove the result in Windows before you spend time inside a game or simulator. If you read only one sentence, make it this one: pick the build for your feeder and your hardware first, then install it once, properly.
Choosing a build on Windows 10
The newest build, BrunnerInnovation 2.2.2.0 from December 2023, is signed with an EV certificate with attestation signing via the Microsoft Partner program and explicitly supports Windows 10 and Windows 11. It is the sensible default for a new Windows 10 install, and the obvious choice if this PC may be upgraded to Windows 11 later. The njz3 2.2.1.1 build is a signed fork focused on force feedback fixes across multiple devices, so it earns its place when force feedback through a feeder is central to your setup. The original 2.1.9.1 build is attestation-signed for Windows 10 in its author’s own words, and it remains the compatibility fallback when a feeder behaves badly on 2.2.x.
| Build | Source | What defines it | Choose it when |
|---|---|---|---|
| 2.2.2.0 | BrunnerInnovation | Newest release, explicit Win10 and Win11 support | Most new installs |
| 2.2.1.1 | njz3 | Signed force feedback fork | FFB-focused setups |
| 2.1.9.1 | Original line | Attestation-signed for Windows 10 | Feeder compatibility fallback |
Whichever build you choose, get it from the vJoy download page so the file name, size and hash on that page can be checked against what you actually downloaded. Guesswork about which installer is which is how mismatched DLL problems begin.
Before you install
Check whether vJoy is already present. Open Windows Settings, look through installed apps, and check joy.cpl for an existing vJoy Device. If an older build is installed and you intend to change builds, uninstall it and reboot first rather than installing over the top. Also close every feeder and game. A feeder that is still running can hold the interface DLL open and leave you with a half-updated system that looks installed but behaves strangely. Finally, sign in as an administrator, because driver installation requires elevation.
- Note your current build if one is installed, so a later change is reversible.
- Export or copy your feeder profiles before changing builds.
- Uninstall the old build and reboot if you are switching tracks.
- Verify the new installer file size and hash after downloading.
Step-by-step installation
- Run the installer for your chosen build as administrator and approve the Windows prompt.
- Accept the default install location unless you have a documented reason to change it.
- Let the installer finish without launching any other program that uses joysticks.
- Reboot the computer so the driver loads in a clean state.
- Open Configure vJoy and make sure at least one virtual device is defined with the axes and buttons you need.
- Open joy.cpl, select the vJoy Device, and open Properties to confirm Windows sees it.
That sequence is deliberately boring. A correct vJoy install should be boring. The excitement in most support threads comes from skipping one of the dull steps, usually the uninstall of the previous build or the reboot, and then trying to diagnose the result as if it were a game problem. Keep the install and the verification as separate phases: first Windows must see the device, then a feeder must move it, and only then should a game be asked to respond to it.
Your first configuration
In Configure vJoy, also called vJoyConf, start with a single device. vJoy allows up to 16 virtual devices, each with up to 8 axes, up to 128 buttons and up to 4 POV hat switches, but a first install should use only what your first feeder writes. Enable the axes your feeder sends, add a modest number of buttons, apply, and return to joy.cpl. If you later add a second feeder, give it its own device ID rather than forcing two programs to write to the same device, which guarantees they will fight over axis values. Device planning is covered in depth in the vJoyConf guide linked below.
Common mistakes
- Installing all three builds to test them. Only one driver can be the installed driver. Test builds sequentially, with an uninstall and reboot between them.
- Assuming Windows 10 means any old file works. The legacy 2.1.8 line only covered Windows 7 through Windows 10 version 1803. Use a current build.
- Skipping joy.cpl. If Windows does not list the device, no binding screen in any game will rescue the setup.
- Forgetting the feeder. vJoy alone produces no movement. A feeder application writes data through vJoyInterface.dll.
- Mixing DLLs. A feeder shipping an older vJoyInterface.dll against a newer driver is a known mismatch pattern. Use components from the same release.
Frequently asked questions
Which build should a Windows 10 beginner install? Start with 2.2.2.0 unless your feeder documentation says otherwise. Is 2.1.9.1 unsafe on Windows 10 because it is older? It is the build its author describes as attestation-signed for Windows 10, and it remains a legitimate fallback, particularly when a feeder only partially supports 2.2.x. Does vJoy work as an Xbox controller? No. vJoy is a DirectInput virtual joystick driver and does not emulate XInput. Tools that need an Xbox-style device use a different layer. What if install fails? Note the exact error, check the installer log locations described in our troubleshooting cluster, and do a clean uninstall before trying again rather than repeating the same install over itself.
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: Complete Guide and Which vJoy Build Should You Download?. 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.