Joya Systems

Call Us: 1-877-DEV-KERNEL

AR hardware

Windows HID input control for an AR computing device

A hardware company needed tight control over keyboard, mouse, and touch input before Windows processed it. Joya Systems built the kernel filters, virtual input drivers, user-mode service, SDK, installer scripts, and signing path needed for production testing.

Platforms

  • Windows 11 x64

Services

  • Windows driver development
  • HID filter drivers
  • User-mode service design
  • Microsoft driver signing

The challenge

The product needed to mediate physical input and synthetic input in a way that ordinary user-mode hooks could not guarantee. Input had to be observed before the OS consumed it, policy decisions had to happen in a service, and reinjected events had to look deterministic to the rest of the system.

What we built

We built HID filter drivers for keyboard, mouse, and touch devices so raw input could be forwarded to a user-mode service for policy decisions. The service could drop, modify, or reinject events depending on product state.

We also built virtual keyboard and mouse drivers so the system had a controlled path for synthetic input. That gave the application a stable interface instead of relying on best-effort desktop automation APIs.

The deliverable included a user-mode library, a Windows service, a test application, PowerShell install scripts, and support for Microsoft driver signing. The result was a complete driver stack, not a kernel component left for the product team to integrate on its own.

Project outcome

  • Delivered a complete Windows 11 input stack covering interception, policy handoff in a service, and deterministic reinjection with no user-perceptible added latency.
  • Provided virtual keyboard and mouse drivers for repeatable synthetic input instead of best-effort desktop automation APIs.
  • Shipped install, test, SDK, and Microsoft driver-signing support so the hardware team could validate the stack inside its own product builds.

Technical takeaway

This is the kind of work where the driver is only one part of the risk. The useful outcome was a complete input subsystem with a testable user-mode contract and a signing path.

Working on something similar?

If your team is building in this area — a driver, kernel module, packet path, file system filter, security sensor, or certification plan — start with a technical conversation, not a sales call. Contact Joya Systems and describe the product, platform, and current state of the code.

Related consulting work

Related case studies

Frequently asked questions

How can software intercept keyboard, mouse, and touch input before Windows processes it?

With HID filter drivers that sit below the OS input path and forward raw input to a user-mode service, which can drop, modify, or reinject events based on product state. User-mode hooks cannot guarantee this ordering; a kernel filter can. We built exactly that stack for keyboard, mouse, and touch on Windows 11.

How do you generate reliable synthetic keyboard and mouse input on Windows 11?

Through virtual keyboard and mouse drivers that present a controlled, stable device to the system, rather than relying on best-effort desktop automation APIs. We paired these with the filter drivers and a signing path so synthetic and physical input could be mediated together.

View all case studies