How to Install vJoy: Complete Step-by-Step Guide

This is the complete, build-agnostic guide to install vJoy correctly the first time. It covers the decisions that generic download pages skip: which build to pick, why you uninstall an old build before installing a new one, what the installer actually puts on your system, how to use Configure vJoy to define a device, and how to verify the result in joy.cpl. It also explains the idea beginners miss most often, that vJoy by itself does nothing. A feeder application sends the input. Follow this guide in order and you will know, at each stage, whether you have a driver problem, a configuration problem or a feeder problem.

What you are actually installing

vJoy is a Windows virtual joystick driver. It creates virtual DirectInput joystick devices that other programs can write to and games can read from. It supports up to 16 virtual devices, and each device can expose up to 8 axes, up to 128 buttons and up to 4 POV hat switches. It does not emulate XInput, so it does not pretend to be an Xbox controller. The package also bundles useful tools: Configure vJoy, also called vJoyConf, which defines the devices; JoyMonitor, which shows live device state; and a demo feeder that shows how a feeder talks to the driver through vJoyInterface.dll. Understanding that bundle explains most beginner confusion.

Step 1: Pick a build

Three builds matter today. BrunnerInnovation 2.2.2.0, released in December 2023, is the newest and the only build that explicitly claims Windows 10 and Windows 11 support, signed with an EV certificate and attestation signing. The njz3 2.2.1.1 build is a signed fork focused on force feedback. The original 2.1.9.1 build is attestation-signed for Windows 10 and remains the fallback when a feeder only partially supports 2.2.x. On Windows 11, start with 2.2.2.0. On Windows 10, start with 2.2.2.0 unless your feeder or force feedback needs point elsewhere. Our dedicated decision guide compares all three in a table with verified file hashes.

Step 2: Uninstall any old build first

If vJoy is already installed, uninstall the old build in Windows Settings and reboot before installing a different one. This is not tidiness for its own sake. Different releases ship different versions of the driver and of vJoyInterface.dll, and a system left with pieces of two releases can produce the classic mismatch where the driver version and the DLL version disagree. A clean break between builds takes two minutes and saves an evening of misleading error messages. While you are preparing, close every game and feeder, and export any feeder profiles you care about.

Step 3: Run the installer

1. Download the installer, vJoySetup, for your chosen build from the download page and check its file size and hash.
2. Run vJoySetup as administrator and approve the Windows prompt.
3. Keep the default options unless you have a specific reason to change them.
4. Let the installer finish completely, then reboot the PC.
5. Do not open a game or feeder until after the reboot and the checks in the next steps.

Get the file from the vJoy download page, where each build is listed with its source, size and SHA-256. Treat any installer that arrives with a different name pattern, an unexpected extra program, or a hash that does not match as the wrong file, and replace it rather than arguing with it. Driver software runs at a privileged level, so provenance is not a detail.

Step 4: Configure vJoy

After the reboot, open Configure vJoy from the Start menu. This is vJoyConf. Select device 1 and define a modest first device: enable the axes your feeder will write, add the buttons you need, and decide whether you need a POV hat. Apply the configuration. Resist the urge to enable every axis and 128 buttons on every device. Each enabled control is something games will list and something a binding screen can confuse you with, and simulators famously show every vJoy device under the identical name vJoy Device. A lean first device is easier to verify and easier to bind. You can expand it later in minutes.

Step 5: Verify in joy.cpl

Press Windows key plus R, type joy.cpl, and press Enter. Select the vJoy Device and open Properties. This panel is your ground truth. If no vJoy Device appears, the driver or the device configuration is the problem, and you should fix that layer before touching any game. If the device appears, keep the Properties window open and start your feeder or the demo feeder: the axis bars and button indicators should respond as the feeder writes values. That response proves the whole chain from feeder through vJoyInterface.dll to the Windows DirectInput view that games also use.

Step 6: Your first feeder note

A feeder is any program that writes joystick data into a vJoy device. Joystick Gremlin merges and remaps physical controls, UCR maps many input types to vJoy as its DirectInput output, FreePIE runs scripted conversions, and small utilities feed serial devices, mouse movement or custom hardware into vJoy. Your first feeder test should be deliberately small: one axis or one button, watched in joy.cpl or JoyMonitor. Once that single mapping moves reliably, add the rest one at a time. Building a full profile before proving a single input is how beginners end up unsure which of twenty mappings is broken.

Common mistakes and questions

• Nothing moves in my game. Check joy.cpl first. If it does not move there, the game is not the problem.
• Driver version does not match DLL. Your feeder is using a vJoyInterface.dll from a different release than the installed driver. Use matching components.
• Do I need to run vJoy before playing? vJoy is a driver, not an app you launch each session. You run your feeder; the driver is already loaded.
• Can vJoy break my real joystick? No. Physical devices remain separate. vJoy only adds virtual devices alongside them.
• Which licence applies? Sources conflict: SourceForge lists Public Domain while the GitHub repositories are MIT-tagged, so treat the licence as that qualified picture rather than a single simple label.

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 Configure vJoy with vJoyConf. 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.