Vdevice - Windows Kernel Driver for Virtual USB Keyboard, Mouse and Gamepad

Create and control virtual USB devices on Windows 10/11 x64 with a Microsoft-signed kernel driver and a two-file C++17 SDK. Define raw USB/HID descriptors, VID/PID, strings, endpoints and reports. Every device uses the same seven library operations; model-specific protocols live in the examples.

Download | Installation | Raw C++ API | Graphical examples | Compatibility

Keyboard control panel	DS4 control panel

Screenshots show offline previews of the applications, not hardware tests.

Install and try

1. Download VdeviceSetup.exe from the latest release and accept elevation.
2. Choose Install or Reinstall / repair. Wait for Installed and ready; if Windows requests a restart, save your work and use Restart Windows.
3. Extract the release's Vdevice-Examples ZIP and open a control panel.
4. Accept the administrator prompt on opening the example, then click Create device and wait for READY.
5. Change fields and press Send state. Release / neutral releases held inputs; Disconnect removes the virtual device.

For a keyboard test, set key1 = 4 (A), choose Tap state in 3 s, then focus your editor. The example releases the key after 50 ms. Key usages follow the target application's keyboard layout.

The console installer provides the same installation backend:

.\VdeviceSetupConsole.exe /install
.\VdeviceSetupConsole.exe /status
.\VdeviceSetupConsole.exe /diagnose
.\VdeviceSetupConsole.exe /uninstall

The GUI reads installation, service and API state on opening and after each operation. A Restart Windows button appears when a restart is required and asks for confirmation. Exit code 3010 requests a restart; 1618 means another Vdevice setup is already running. The GUI also supports removal. The driver package is Microsoft-signed; installer and example EXEs have their own signature status. Installation and diagnostics.

Included devices and controls

UI executable	Example
VdeviceKeyboardUI.exe	USB boot keyboard, modifiers, six keys and host LED feedback
VdeviceMouseUI.exe	Five buttons, signed 16-bit relative X/Y and vertical/horizontal wheels
VdeviceXbox360UI.exe	ViGEm-style XInput gamepad, sticks, triggers, buttons and rumble
VdeviceDualShock4UI.exe	DS4 USB interface, sticks, triggers, D-pad, motion, touch and rumble/RGB feedback
VdeviceXboxOneGipUI.exe	Native PC GIP gamepad, metadata, Guide, analog controls and motor commands

Descriptor Workshop imports editable JSON descriptions and exchanges raw reports. All device examples have a graphical interface; the console installer remains available for command-line installation and diagnostics. Control panel instructions.

How it works

The driver uses KMDF / USB Device Emulation (UdeCx) to enumerate virtual USB devices from your descriptions. Windows selects a matching device driver from those descriptors and identifiers. Your application sends device-to-host input and handles host output or delegated control requests according to the protocol. The SDK device object owns its device; deletion or process termination disconnects it.

Supported descriptions include low/full/high speed, one configuration, multiple interfaces at alternate setting zero, and interrupt/bulk endpoints. SuperSpeed, isochronous audio, external hubs and additional configurations/alternate settings are outside the implemented scope. Changing a VID/PID alone does not reproduce a device's firmware or authentication. Protocol limits.

The GIP sample requires Windows 10 21H2 or later and uses Microsoft's documented PC USB security opt-out interface. It does not emulate console authentication. The Xbox 360 sample supplies the gamepad function; DS4 uses synthetic identity and example calibration data. These are PC protocol examples, not complete console firmware replicas.

Raw C++ SDK

Add Vdevice.h and Vdevice.cpp to your Windows x64 C++17 application. The library contains no built-in device profiles.

Operation	Purpose
Validate_Device(config)	Check descriptors and topology offline
Create_Device(config)	Create an owned virtual device
Get_Output(timeout)	Receive host output, control and device-state events
Respond_Output(output, bytes, stall)	Complete a delegated control request
Send_Input(device, endpoint, bytes)	Queue raw device-to-host input
Get_Info()	Read capabilities, demo state and owned devices
Delete_Device(device)	Disconnect and release a device

Check each operation's error and message. Creation is asynchronous: service outputs/controls during enumeration and wait for configuration before normal input. Keep the move-only device object alive while using it. The mounting guide explains every descriptor field and lifecycle step; the examples contain complete descriptor construction and report encoders.

Downloads and build

The latest release provides both standalone installers, examples, SDK sources, the Microsoft-signed driver package and SHA256SUMS.txt.

Vdevice/           Vdevice.h and Vdevice.cpp
ExamplesUI/        Control panels, raw protocols and Descriptor Workshop
InstallerConsole/  Console installer and setup backend
InstallerUI/       GUI installer and signed driver package
docs/ Tests/       API, installation and verification

Build with Visual Studio 2022 Desktop C++, a Windows SDK, CMake and .NET Framework reference assemblies: powershell -ExecutionPolicy Bypass -File .\Build.ps1. This builds user-mode components and runs offline tests. Kernel source is not included. User-mode source is MIT; prebuilt driver binaries have separate terms.

Demo edition and related projects

One hour per Windows kernel boot, starting at the first successful virtual device creation and shared across applications. Sleep counts; closing or reinstalling does not reset it. Expiry disconnects virtual devices and refuses new creation/transfers until Windows Restart. For the unrestricted version, DM titancsa on Discord.

The Xbox 360 and DS4 examples use descriptor/protocol material from nefarius/ViGEmBus under BSD-3-Clause; ViGEmBus does not need to be installed. Third-party notices.

To intercept and modify physical devices, use Interceptor. Vdevice creates virtual devices and uses its own driver.

Responsible use and disclaimer

This project, including its drivers, SDKs, libraries, applications, installers and examples, was created for lawful, constructive purposes such as accessibility, device customization, research, testing and software development. Illegal, malicious or unauthorized use is neither intended nor endorsed by TitanCSA or the contributors.

You are solely responsible for how you use, modify or distribute the software, for obtaining any necessary authorization, and for complying with applicable laws, third-party rights and service rules. TitanCSA and the contributors do not accept responsibility for users' actions, including illegal activity or misuse of the drivers or SDKs.

To the maximum extent permitted by applicable law, the software is provided "AS IS", without warranties of any kind, and TitanCSA and the contributors are not liable for claims, damages, data loss, system damage or other consequences arising from its use or misuse. Nothing in this notice excludes liability that cannot legally be excluded. Existing project and third-party license terms remain applicable.