Advanced users can verify using certutil -hashfile <filename> SHA256 in PowerShell. Official ZLG forums sometimes provide the hash.
Open Windows PowerShell and run the command: Get-FileHash path\to\driverfile.zip zlg usbcanii driver download high quality verified
| | Likely Cause | Solution | | :--- | :--- | :--- | | Windows 11 Error: "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)" | Driver conflict with Windows security features, specifically "Memory Integrity" (Core Isolation). | Open Windows Security → Device Security → Core Isolation details . Turn off Memory Integrity and restart your PC. | | Windows 7/10/11: Yellow exclamation mark in Device Manager | Operating system's driver signature enforcement blocking the unsigned or improperly signed driver. | - Update Windows : Install Windows updates, specifically the KB3033929 security update for Windows 7. - Disable Signature Enforcement (for testing): Restart your computer, press F8 before Windows loads, and select " Disable driver signature enforcement " from the Advanced Boot Options menu. | | "Open Device Failed" error in Python or other dev environments | The device index or channel is incorrect in the software code. For example, the software might be trying to open USBCAN-I instead of USBCAN-II. | Ensure the device type is explicitly set to ZCAN_USBCAN2 in your code's device selection logic (e.g., ZCanDeviceType::ZCAN_USBCANFD_200U in Rust or equivalent in C/C++/Python). | | Windows 11: Driver installation fails completely | The driver being used is a very old version not fully compatible with Windows 11's more stringent kernel security. | Download the very latest driver from the official ZLG website (https://manual.zlg.cn/web/#/146). If that fails, enable TestSigning mode by running bcdedit /set testsigning on as an administrator and rebooting. | | Linux: Device not found or permission denied | The user does not have the appropriate permissions to access the USB device node in /dev/bus/usb/ . | - Temporary fix : Use sudo chmod 666 /dev/bus/usb/xxx/yyy (replace xxx/yyy with the output from lsusb ). - Permanent fix : Follow the udev rule creation steps outlined in the Linux installation section above. | | Linux: ZLG USBCAN-II not working on ARM64/aarch64 (e.g., Nvidia Jetson) | The official ZLG drivers from the website are pre-compiled for amd64 (x86_64) architecture only, not for ARM64. | - Check the official ZLG website to see if they have released an ARM64 version. - Use the open-source zlgcan driver, which is cross-platform and can be compiled for ARM64. | | Device recognized, but CAN data transmission is erratic or lost on Windows | In Windows 11, the driver might be incorrectly bound to a generic driver stack. | Use the Zadig tool. Run Zadig, select your ZLG device from the list, and ensure it is bound to either the WinUSB or libusb driver stack. If not, change it using the tool. | | Device constantly fails to initialize on Windows 11 with a recent Intel or AMD CPU | Windows 11's Virtualization-Based Security (VBS) and Hyper-V can create conflicts. | Open Windows Security → Device Security → Core Isolation . Turn off Memory Integrity . You may also need to disable Virtual Machine Platform (VMP) and Hyper-V in " Windows Features ". | The driver may be corrupted or missing
: Extract the downloaded archive and copy the libusbcan.so shared library to the /lib directory. This typically requires sudo privileges: Turn off Memory Integrity and restart your PC
The installer will guide you through the process. A typical ZLG driver installation involves a straightforward wizard, as documented in their user manual:
For developers, the driver package includes the ControlCAN.dll library. Many third-party tools (like CANTest) require you to manually copy this DLL into their installation directory to ensure compatibility.
