Download vJoy Virtual Joystick Driver Official Binaries
Access fully compiled, clean .exe installation executables for the vJoy engine framework. Below you will find the distinct version tracks categorized by operating system compatibility. The main buttons below link directly to the upstream release files on GitHub and SourceForge — nothing repackaged. vJoy is free and source-available (SourceForge lists it as public domain; the GitHub forks carry the MIT licence).
Crucial Security Advisory: Kernel-Mode Execution
Because the virtual joystick framework must create deep system device nodes directly inside the Windows kernel layer, you must strictly evaluate software execution provenance. Never download vJoy setups from unverified third-party cracked file mirrors or rapid-share lockers. Always confirm that the binary files match the cryptographic release hashes highlighted in the deployment matrix below.
Windows 11 Highly Recommended Track
The current community build for Windows 11: BrunnerInnovation forked njz3’s force-feedback branch and sponsored proper driver signing, so it loads without lowering Windows security policies. This version also works on Windows 10.
v2.2.2.0 (Fully Signed Fork)
BrunnerInnovation Automated Signature Base
- Signature Matrix: EV-certificate signed + Microsoft Partner attestation signing (per the BrunnerInnovation release notes)
- System Parameters: Signed for Windows 10 and 11. If Windows lists the driver under Memory Integrity as incompatible on your PC, see our troubleshooting guides.
- Deployment: Installs with the standard vJoy setup wizard
Legacy Windows 10 & Fallback Archive Track
Are you running standard Windows 10 ecosystems or encountering input-grabbing registry glitches on specific emulator wrappers? Utilize these classic milestone rollouts.
v2.2.1.1 (njz3 Force-Feedback Fork)
Signed installer — the FFB branch
- Best for: force-feedback setups on Windows 10
- Win 11 Status: signed, but the njz3 README itself points Windows 11 users to v2.2.2.0
v2.1.9.1 (Original, SourceForge)
The original final release (2019)
- Best for: maximum feeder compatibility — some feeders only partially support 2.2.x
- Win 11 Status: attestation-signed for Windows 10; often works on Windows 11 but is not guaranteed
The Clean Installation Protocol
Follow this sequence exactly to prevent corrupted driver states and registry loops on your system.
Purge Legacy Configurations
Open the standard Windows Windows Settings or Control Panel and uninstall any previously aborted vJoy instances. Reboot your PC instantly. Linger driver hooks inside kernel buffers will block newly signed deployment configurations from running initialization paths.
Execute with Elevated Privileges
Locate your downloaded installer track package (e.g., vJoySetup.exe). Do not simply double-click the asset. Right-click the application executable file directly and pick “Run as administrator” from the contextual option tree menu.
Acknowledge the Security Challenge
During system execution, Windows might throw a security intercept asking whether to authorize a companion peripheral driver layout. The signed builds should not trigger a signature warning. If Windows does warn, stop and re-download from the links on this page rather than clicking through.
Finalize Configuration & Validate Nodes
Once the setup utility wizard reports a completion matrix, search your local start menu for “Configure vJoy”. Ensure Device 1 is activated with your intended axis arrays. Test physical binding loops seamlessly within target application settings panels.
Download & Installation Troubleshooting
Resolve runtime configuration crashes and deployment freezes instantly with these verified technical solutions.
Why does the vJoy installer hang or freeze at 0% or mid-installation?
An installer hang typically means the routine is blocked while trying to register driver certificates with the Windows Cryptographic database, or it is hitting a registry deadlock with an orphaned vJoy instance. Open services.msc via Windows Run, verify that Cryptographic Services is actively running, right-click the installer, and select “Run as administrator” to grant registry write access.
What causes the blue screen (BSOD) crash during installation, and how do I fix it?
A blue screen during a driver install usually means a leftover or mismatched driver state. Do not delete driver files from System32 by hand. Instead: uninstall vJoy in Settings > Apps, reboot, remove leftover vJoy driver packages with pnputil (see our complete-uninstall guide), check %TEMP% Setup Log and C:\Program Files\vJoy\vJoyInstall.log for the failing step, then install the signed v2.2.2.0 build.
The setup completed, but the companion apps say “vJoy Driver is not installed” or enabled?
This state indicates that while the software wrapping UI installed successfully, the actual kernel driver was rejected by the Windows device subsystem. This means the apps installed but the kernel driver did not load — a blocked signature, a disabled device, or leftovers from another build. Uninstall completely, reboot, and install one signed build (v2.2.2.0 for Windows 11). Our ‘vJoy Driver Not Enabled’ guide lists every check.
Can I install and use multiple separate versions of vJoy on a single PC?
No. The Windows operating system can only register and run a single vjoy.sys virtual bus master inside the kernel device tree at one time. Attempting to mix files from different branches will result in file structure corruption, driver initialization blocks, and device registration failures. Always completely purge old branches before changing to a different release track.
Which vJoy Build Should You Download?
Don’t guess your setup path. Compare structural differences across active branches to ensure your system security model lines up with the virtual controller architecture.
Track A: Signed v2.2.2.0
- 🎯 Primary Target: Modern Windows 11 (23H2 / 24H2+) environments.
- 🛡️ Secure Boot: the build is EV-signed and attestation-signed for Windows 10/11.
- ⚡ HVCI/Core Isolation: no published guarantee — if Windows blocks vjoy.sys, follow our troubleshooting guide.
- 🔌 Feeder Sync: Fully compatible with modern open-source tool forks.
Track B: Legacy v2.1.9.1
- 🎯 Primary Target: Windows 10, Windows 8, and niche game configurations.
- 🛡️ Signing: attestation-signed for Windows 10.
- ⚡ HVCI/Core Isolation: often works, not guaranteed — never disable security features as a first step.
- 🔌 Feeder Sync: Stabilizes older peripheral controllers and custom scripts.
💡 The Golden Rule: Always test **Track A (v2.2.2.0)** first. Only fall back to **Track B (v2.1.9.1)** if your physical configuration requires legacy controller mapping registry setups.
How to Verify Your vJoy Installer Integrity
Before running any executable file that interacts with the Windows kernel layer, we highly recommend verifying its SHA-256 cryptographic signature locally.
# Execute this command to check the installer package hash string locally:
Get-FileHash "$HOME\Downloads\vJoySetup.exe" -Algorithm SHA256
# Expected Output Signature Matrix:
Open Shell Console: Right-click your Windows Start menu icon and choose Windows Terminal or PowerShell.
Run Hash Check: Copy the code block above, modify the path if you saved the file outside your default path, and hit Enter.
Match & Verify: Ensure your computer’s string calculation output matches the clean source release logs from the developer branches.
How to Completely Remove Broken vJoy Drivers
Before deploying a new version track, you must thoroughly scrub residual registry entries and kernel files left behind by older versions to prevent driver allocation collisions.
Step 1: Standard Application Purge
First, exit any game wrappers, track feeds, or config maps running in the taskbar background. Navigate to your system apps manager to break the initial file associations:
Step 2: Device Manager Driver Scrub
An application uninstall often leaves ghost hardware profiles active in the Windows infrastructure. Force the operating system to drop the core controller configuration mapping:
- Right-click the Start menu button and select Device Manager.
- Expand the Human Interface Devices category listing.
- Right-click vJoy Device and select Uninstall device.
- ⚠️ Crucial: Check the box that says “Attempt to remove the driver for this device” before clicking the final confirmation button, then restart your PC.
Ready to Initialize Your Virtual Inputs?
Don’t let driver signature blocks hold back your simulator layout. Jump straight back to our secure version matrix tracks to execute a clean deployment sequence.