Void Drivers

Windows virtual drivers for headless cloud-gaming hosts - genuine-looking display, mouse, keyboard, and gamepad with no physical hardware attached.

---

About

Void is a pair of Windows drivers built to make a headless machine look like a fully-equipped gaming PC to games and anti-cheat (Vanguard, EAC, BattlEye):

Component	Tech	Runs in	What it does
VoidDisplay	IddCx UMDF	user mode	Adds virtual monitors for video capture / remote streaming
VoidInput	UMDF + VHF (HID)	user mode	Hosts virtual HID mouse, keyboard, Xbox One / DS4 / DS5 gamepads, and touch
libvoidrv	C++ SDK (C ABI)	-	One library that drives both, via voidrv.h
voidctl	CLI	-	Command-line control + test harness

Void is built from the ground up as clean, directly-controllable virtual hardware: devices that persist on your terms, driven by a single SDK with no session coupling.

Why it exists

• Headless hosts have no GPU display output, no input devices. Void supplies both as real device nodes, so capture APIs see a monitor and games see real controllers.
• Real input, not SendInput. VoidInput presents genuine HID devices (real VID/PID, real report descriptors) built on the in-box Virtual HID Framework, so input survives anti-cheat that blocks injected events. Gamepads are HID, reaching games through DirectInput, Windows.Gaming.Input, and Steam Input.
• No keepalive. Void displays persist until you explicitly remove them - no per-display heartbeat or periodic ping to keep them alive.

Design highlights

• VoidDisplay - up to 8 virtual monitors, default 1920x1080@60, custom VVD EDID, SDR first (HDR planned). Persists across sessions, no heartbeat.
• VoidInput - a UMDF driver on the in-box Virtual HID Framework that creates virtual HID devices on demand. Each clones a genuine HID identity (VID/PID + report descriptor) so it's indistinguishable from real hardware to applications; only the control interface is Void-branded.
• One control surface - both drivers are driven through DeviceIoControl, wrapped by libvoidrv so host apps never touch raw IOCTLs.

Status & roadmap

Pre-alpha - project scaffolding stage. Implementation order:

1. VoidDisplay (in progress) - virtual monitor + control IOCTLs.
2. VoidInput - VHF enumerator -> HID mouse -> keyboard -> Xbox One -> DS4/DS5 -> touch.
3. libvoidrv / voidctl - SDK + CLI alongside each milestone.

Building

Requires Visual Studio 2022 + WDK 10.0.26100 (with VS integration), x64.

# from a Developer PowerShell / Command Prompt
msbuild Void.sln /p:Configuration=Debug /p:Platform=x64

Both drivers are UMDF (user mode), so they install with a local test certificate (placed in Root + TrustedPublisher) - no testsigning mode and no Microsoft attestation required:

# create a self-signed test cert, then sign the .dll + .cat and trust the cert

Production signing is a directly-applied OV/EV Authenticode signature - a deferred release task.

Repository layout

void-display/   VoidDisplay (IddCx UMDF, C++)
void-input/     VoidInput  (UMDF + VHF HID, C++)
libvoidrv/      SDK (voidrv.h)
voidctl/        CLI
docs/           Design docs

License

MIT.