Getting started / Windows
A useful first run without adding an input driver.
Start with a small observable result. Add driver dependencies when your actual workflow needs them.
Several tools have a useful starting point before you install a kernel component: reading a device inventory, opening a browser tab through an SDK, or checking a fixture offline. Those first steps are deliberately different from intercepting physical input or creating a live USB device.
Automate a dedicated browser
Browser Control SDK controls its own Windows WebView2 browser through Python, JavaScript, C++ and other clients. It does not require an input driver or administrator rights.
- Download and extract the complete Windows x64 release.
- Open
BrowserControl.exe. Microsoft Edge WebView2 Evergreen is a runtime dependency; follow the application's official runtime link if it is missing. - With Python 3.10 or later, install the client:
python -m pip install browser-control-sdk
The package installs a client, not the browser application. Save this script and run it with the same Python environment:
from browser_control import Browser
browser = Browser.connect()
tab = browser.new_tab("https://example.com")
print(tab.snapshot()["text"])
Expected result: the dedicated browser opens Example Domain and the script prints the page's visible text. This demonstrates a browser connection and page observation; it does not establish that every website or authentication flow can be automated. The example needs Internet access.
If no browser is found, open the extracted application first. If Python cannot import the client, check that the package was installed into the interpreter running the script. Closing a client script does not close a connected browser. Use the browser normally or explicitly close only the instance you intend to close.
Collect read-only device evidence
Driver Readiness Inspector is a MIT Windows utility without a demo timer or paid unlock. It uses user-mode Windows APIs and does not install a driver.
- Extract its complete Windows x64 release.
- Open
DriverReadinessInspector.exe, then select a device node. - Inspect the reported PnP problem code, package and service evidence. Export an HTML or JSON report when you need to share a support case.
Expected result: a local report of observed device and driver state. Missing or access-denied fields remain unknown. A report does not repair the device, certify security or establish the physical device count: Windows often exposes several nodes for one device.
Review a report before sharing it. Device identifiers and system details can be relevant to support while still being unnecessary in a public issue.
Validate a fixture before a live run
Input CI Runner and HID Fixture Studio separate offline fixture validation from explicit live operations. Begin with the documented validation path.
A valid JSON model or HID descriptor is an integration starting point. It does not prove device enumeration, filter attachment, report consumption or application compatibility. Live Vdevice-backed tests require the matching product driver and must account for its documented evaluation and known stability limits.
When your next step needs a driver
Use the matching product's complete release and examples. Check the Windows build, CPU architecture, device family, evaluation terms and removal procedure. A C++ or language SDK package is a separate deliverable and normally does not install the product driver.
Some engineering previews intentionally do not publish a usable driver. For example, the serial/COM preview repositories document unvalidated live paths, and the file/registry previews document pending altitude, signing or live qualification. A preview is not made ready by copying files from a different edition.