vJoy Device Not Showing in joy.cpl: 6 Checks

You installed vJoy, opened joy.cpl to test it, and there is no vJoy Device in the list. That empty list is frustrating because joy.cpl is where most setup guides tell you to verify everything. Work through the six checks below in order. Each one rules out a documented cause, and most readers find their device by check three or four, without reinstalling anything.

A quick orientation first: joy.cpl is the Windows game controllers panel. It lists game controller devices Windows currently has loaded and available. A vJoy Device appears there only if the vJoy driver is installed, loaded, enabled, and configured to present at least one device. Each check below maps to one link in that chain.

Check 1: is the driver actually loaded?

An installer can lay down files without the driver ending up loaded and running. Open Configure vJoy (vJoyConf). If it reports the driver as not enabled, or refuses to show a configuration, the driver is not loaded and joy.cpl is honestly reporting that. In that case, stop checking joy.cpl and fix the driver state first using our driver-not-enabled guide, then return here. If vJoyConf opens normally and shows a configuration, continue to check 2.

Check 2: Device Manager, Human Interface Devices

Open Device Manager and expand the Human Interface Devices section, then look for the vJoy Device. Three outcomes are possible. If the device is present and enabled, Windows knows it, and the problem is narrower than it looked — continue to checks 5 and 6. If the device is present but disabled, enable it, then close and reopen joy.cpl. A disabled device does not present itself as a usable controller, and re-enabling it is the entire fix for a surprising number of readers. If no vJoy Device appears anywhere in Device Manager, the install itself is incomplete or was undone; go to check 4.

Check 3: was the device disabled some other way?

Devices get disabled accidentally through right-click menus, device cleanup tools, and earlier troubleshooting sessions that were never reversed. While you are in Device Manager, use View, Show hidden devices, and check whether a greyed-out vJoy Device is listed. A hidden, disconnected, or disabled entry explains an empty joy.cpl with an otherwise healthy install. Enable or reconnect what you find, reboot, and test joy.cpl again before moving on.

Check 4: wrong-build remnants

If Device Manager shows nothing at all, suspect remnants. Installing the original 2.1.9.1 line, the njz3 2.2.1.1 fork and the BrunnerInnovation 2.2.2.0 build over each other, or leaving a half-finished install in place, can leave a state where no build is properly in charge — and only one vjoy.sys can run. The fix is not a fourth install attempt. Uninstall all vJoy entries, inspect the driver store with pnputil -e for Shaul or vJoy OEM INFs, remove only those entries with pnputil -f -d oemXX.inf, reboot, and install exactly one build. Our complete uninstall guide and our conflicting-installs guide cover this procedure step by step.

Check 5: is the configured device count zero?

vJoy lets you configure how many virtual devices exist, up to a documented limit of 16 devices, each with up to 8 axes, up to 128 buttons and up to 4 POV hats. Open Configure vJoy and look at your configuration. If the configuration presents no enabled device — in effect, a device count of zero for practical purposes — joy.cpl has nothing to show even though the driver is fine. Configure at least one device with at least the basic axes, apply the configuration, and let vJoy apply the change before rechecking joy.cpl. This check catches readers who disabled devices while experimenting and forgot, and fresh configurations that were never actually applied.

Check 6: reboot, then look again

Driver and device changes under Windows frequently need a reboot to settle, and joy.cpl reflects loaded devices, not pending ones. If you changed anything in checks 2 through 5 — enabling a device, applying a configuration, finishing an install — reboot once and open joy.cpl again before concluding anything. Skipping the reboot is the most common reason a correct fix gets abandoned as ‘didn’t work’.

How to confirm it is fixed

  1. joy.cpl lists at least one vJoy Device by name.
  2. Selecting the device and opening its properties shows a test page.
  3. With a feeder running, the axes and buttons on that test page respond to your input.
  4. The device is still listed after a reboot, proving the fix is in the installed configuration and not in a temporary state.

If all six checks pass without a device appearing — driver reported loaded, Device Manager clean, a device configured, reboot done — capture your vJoyInstall.log from C:\Program Files\vJoy\ and the exact build you installed. At that point you have ruled out everything documented, and the log is the evidence needed for the next level of help.

Related guides

vJoy is an unofficially documented tool on this site. vJoy itself was created by Shaul Eizikovich, with later signed forks by other maintainers. This site is not the official vJoy project site.

Similar Posts