C:\Program Files\AutoKent\MVCI Driver\
├── x64\
│ ├── mvci_x64.sys (kernel driver)
│ ├── mvci_x64.dll (J2534 vendor DLL)
│ └── mvci_x64.inf
├── MVCI_Config.exe
└── firmware\
├── v2.0.1.bin
└── flash_tool.exe
The J2534 DLL registers itself under:
HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04
Interactive:
msiexec /i "$env:TEMP\AutoKENT_MVCI_x64.msi"
Silent (enterprise):
msiexec /i "$env:TEMP\AutoKENT_MVCI_x64.msi" /qn /norestart ADDLOCAL=ALL
The installer performs the following steps automatically: autokent mvci multi driver x64
After install, reboot once (or run pnputil /restart) to let the PnP manager bind the new driver.
| Aspect | 32‑bit driver | 64‑bit driver | |--------|---------------|----------------| | OS support | Win XP–Win 7 32-bit | Win 7/8/10/11 x64 | | DSE requirement | None (XP era) | Mandatory signature or test mode | | USB stack | Often libusb0 (filter driver) | WinUSB / libusbK (cleaner) | | J2534 DLL | 32‑bit only | 32+64 hybrid (WoW64 aware) | | Stability | BSOD risk with sleep/resume | More stable on modern hardware |
| Symptom | Likely Cause | Quick Fix |
|---------|--------------|-----------|
| Device shows “Code 43” in Device Manager | Driver not signed for Secure Boot or corrupted INF | Re‑install with msiexec /i … /qn after disabling Secure Boot, then re‑enable it. |
| Dropped frames when streaming 1080p60 | DMA buffer too small or interrupt throttling | Increase buffer to 4096 KB via the registry key `HKLM\Software\AutoKENT\MVCI\DmaBufferKB Interactive:
msiexec /i "$env:TEMP\AutoKENT_MVCI_x64
Driver fails due to Secure Boot:
COM port not visible in software:
Device works intermittently:
Software reports “no device” or “unsupported adapter”:
| Feature | Support Level | |---------|----------------| | ISO 9141‑2 (KWP2000) | Yes | | J1850 VPW / PWM | Partial (some clones have weak physical layer) | | CAN 2.0A/B (11/29‑bit) | Full | | ISO 15765‑4 (CAN) | Yes | | Fast CAN (500 kbps) | Yes | | ISO 14230 (KWP over CAN) | Yes | | Auto‑baud detection | Yes (via DLL) | | Multiple concurrent channels | Usually 1 (hardware limitation) | | Voltage detection | Via utility (not live through API) |
Real‑world throughput (with Techstream): Device works intermittently:
The x64 driver does not improve performance over 32‑bit — it only enables compatibility with x64 diagnostic software.
| Feature | Benefit | How it works |
|---------|---------|--------------|
| Universal x64 binary (mvci_x64.sys) | One driver for every supported card; eliminates driver sprawl. | Built with the Windows Driver Kit (WDK) 10.0.22621, signed with a Microsoft EV certificate. |
| Secure‑Boot ready | Deploy on locked‑down workstations and kiosks. | The driver’s catalog (AutoKENT_MVCI.cat) is signed for WHQL‑compatible boot. |
| Multi‑device hot‑plug | Add or remove capture cards without a reboot. | Implements PnP‑IRP handling and dynamic mini‑port loading. |
| HDMI‑2.0 & SDI 4K@60 Hz support | Capture high‑resolution streams out‑of‑the‑box. | Updated register tables for the latest Cypress/Realtek video chips. |
| Built‑in latency‑measurement API | Precise jitter analysis for broadcast pipelines. | Exposes a IOCTL_MVCI_GET_LATENCY that can be queried from user‑mode tools. |
| Cross‑framework compatibility | Works with DirectShow, Media Foundation, OBS, vMix, and custom GStreamer plugins. | The driver registers as a Video Capture device class (6BDD1FC6-810F-11D0-BEC7-08002BE2092F). |
| Automatic mini‑port selection | No manual INF edits needed when mixing brands. | The driver reads the PCI/USB device ID and loads the matching mini‑port DLL from %ProgramFiles%\AutoKENT\MVCI\MiniPorts. |
| Diagnostic UI (AutoKENT MVCI‑Ctrl) | Real‑time status, DMA counters, and error logs. | A lightweight Win32/WinUI3 app bundled with the driver package. |