WinUSBridge Toolkit — $149

A triage and template pack for testing whether your legacy USB driver can move onto the user-mode WinUSB-rebind path. Drop the ZIP into Claude Code, Codex, Cursor, or another LLM workspace alongside your device's INF, vendor protocol docs, and the free diagnostic output — and use the included parameterised templates and design notes as scaffolding to draft the user-mode shim. When the device is a fit, it can compress the rebind to hours so USB hardware keeps running while a vendor-signed driver works through Microsoft's 3–6 week Partner Center pipeline.

Who this is for

Commercial stopgap / production triage. Your assembly line, laboratory, broadcast rig, or backup pipeline is blocked because Windows just blocklisted a vendor driver. The toolkit gets the device working again in hours so operations resume while compliance waits on the official signed driver. Positioned as a stopgap triage accelerator, not a certified remediation platform.
Hobbyist, homelab, legacy, and developer hardware. Internal tooling, developer testbeds, legacy lab instruments, and homelab gear where paying thousands for an EV code-signing certificate makes no financial sense. You want a structured way to collect evidence and ask an LLM for grounded next steps.

What's in the pack

Pack version 1.0.0— 5 files, ~32 KB total. Updates publish here as the Microsoft App Control / WDAC policy evolves.

README.md — quick-start, file index, per-product checklist.
device.config.example.json — every placeholder listed once with example values; the canonical per-product input.
GenericLoader.template.inf — parameterised WinUSB-binding INF; uses Microsoft's documented winusb.inf include pattern.
Install-WinUsbBridge.template.ps1 — installer engine with Install, Uninstall, and Status actions; verbose logging, scheduled-task persistence, clean rollback.
DESIGN-NOTES.md — structural derivation (public-source citation table), per-device-class integration notes, security posture documentation.

How you use it with an LLM

The pack is structured scaffolding. The intended workflow is to drop it into an LLM workspace alongside your actual case material, and use the LLM to fill the parameterised templates against your specific device — instead of asking the LLM to invent the user-mode rebind pattern from scratch.

Unzip the pack into a working folder for this device.
Add your case material to the same folder: existing INF / SYS / CAT files, vendor protocol documentation (datasheet or programming guide), an Event Viewer export filtered to CodeIntegrity 3076 / 3077, and any Device Manager screenshots or troubleshooting notes.
Open the folder in Claude Code, Codex, Cursor, or your local LLM workspace. The pack is plain text and JSON, so any LLM workspace that can read a directory works.
Use DESIGN-NOTES.md as the anchor. It contains the per-device-class residual-risk table and the user-mode-loader contract; the LLM uses it to decide whether your device is a rebind candidate, fill in device.config.example.json for your VID/PID, expand the two template files, and draft the user-mode loader your device needs.
Build, install on a throwaway VM, validate, then deploy. Standard Inf2Cat + pnputil flow. The installer's scheduled-task layer keeps the binding alive across Windows Update.

What this is not

Not a guaranteed fix. Hardware, chipsets, and endpoint security stacks vary; some devices are not rebind candidates at all (see the fit criteria).
Not a way to bypass Windows security, the Vulnerable Driver Blocklist, Secure Boot, or HVCI. The rebind uses Microsoft's in-box, supported winusb.sys path; nothing here disables a security policy.
Not a kernel-driver signing solution. There is no .sys in the bridge — that is the point. If your situation requires a re-signed kernel driver, the supported path is vendor / OEM re-signing through Microsoft Partner Center.
Not a replacement for vendor engineering or for a Change Advisory Board change in regulated environments. See the scope-of-use notice.
Not a SaaS, agent, dashboard, account, or licensing system. One tier, one ZIP, signed download link.

Order

$149 one-time download. One tier. No per-seat licensing, no subscription. Signed download URL emailed immediately after checkout (link valid for 7 days).

Before purchasing, run the fit criteria to confirm your device is a candidate for the rebind pattern.

Checkout is handled by Stripe. Sales are final on download. See the license and refund policy.

Engineering notice

WinUSBridge is a developer utility for engineering teams remediating blocklisted USB drivers via the WinUSB-rebind pattern. It is intentionally a temporary workaround — a tourniquet, not a long-term replacement for a vendor-signed driver.

Provided as-is. Hardware, chipsets, and endpoint security stacks vary widely; the pack ships without warranty of any kind. Standard indie-software terms.
Test before you deploy. Validate on a non-production device first. The toolkit is an engineering aid; your team owns the deployment decision and the testing that supports it.
Liability cap. Per the license, Wheel Up Labs' aggregate liability is capped at the purchase price you paid. This is normal for a $149 self-serve SKU; if your environment requires a higher-coverage commercial vendor, the scope-of-use notice above lists the supported alternatives.

Built from public sources

Pack contents are built from Microsoft Learn (WinUSB INF, Task Scheduler, Authenticode), the EZ-USB FX2LP Technical Reference Manual (Infineon, formerly Cypress), and the libusb and fx2lib open-source projects. The pack contains no vendor-proprietary code or device-specific implementation details.