How to Fix 'Failed to Install vJoy Driver' & Code 52 Signature Error

One of the most common issues encountered when setting up virtual controllers on modern Windows systems is the infamous "Failed to install vJoy driver" error or Windows Code 52 ("Windows cannot verify the digital signature for the drivers required for this device"). This technical guide provides tested solutions to resolve driver signature enforcement conflicts, clean up legacy driver residue, and ensure a flawless installation.

Common Error Variations

• "vJoy failed to install: INF file could not be installed."
• "Device Manager: Code 52 - Windows cannot verify the digital signature."
• "Error 0x80070002 / 0x80070005 during driver package registration."
• "Installation halts at 99% when creating virtual HID device."

Solution 1: Clean Removal of Previous Driver Residue

Failed previous installations frequently leave locked files in the Windows DriverStore. Before reinstalling:

1. Press Win + X and select Device Manager.
2. Click View > Show hidden devices.
3. Expand Human Interface Devices and look for vJoy Device.
4. Right-click on it, choose Uninstall device, and make sure to check the box for "Delete the driver software for this device".
5. Open Command Prompt as Administrator and run:

   pnputil /enum-drivers | findstr -i vjoy

6. If an oemXX.inf matching vJoy is listed, delete it using:

   pnputil /delete-driver oemXX.inf /uninstall /force

Solution 2: Temporarily Disable Memory Integrity (Core Isolation)

Windows 11 features Hypervisor-protected Code Integrity (HVCI). Older builds of vJoy may not meet HVCI criteria:

1. Open Windows Security from the taskbar.
2. Navigate to Device Security > Core isolation details.
3. Toggle Memory integrity to Off.
4. Restart your computer.
5. Run the official installer from the vJoy Download Page.
6. After successful installation and testing via joy.cpl, you can test re-enabling Memory Integrity.

Solution 3: Using the Fully Signed vJoy 2.1.9.1 Build

If you are experiencing signature rejection with custom community builds, switch to the SHA-256 signed official build vJoy 2.1.9.1, which features broad cross-signing compatibility for Windows 10, 8.1, and 7.

You can download the verified binary package directly from our download center with verified SHA-256 hashes.

Solution 4: Enable Test Signing Mode (Developer Workaround)

If your specific Windows build requires experimental or community-patched vJoy drivers:

1. Open Command Prompt (Admin).
2. Execute:

   bcdedit /set testsigning on

3. Restart your PC. You will notice a "Test Mode" watermark in the lower-right corner.
4. Install the vJoy driver. Windows will permit test-signed kernel binaries to execute.

Verification After Fixing

Once you complete these steps, open Command Prompt and check that the vJoy service is running properly:

sc query vjoy

The state should display RUNNING. You can now follow our Windows 11 Setup Guide to configure buttons, axes, and feeder applications.