If you want, provide a device’s lsusb output (Linux) or the Windows Device Manager device instance ID and I’ll map the vendor/product IDs to the exact Canon model and suggest the correct driver package.
The string "usbprint canondevicef144" is a USB Hardware ID (Device ID) used by the Windows operating system to identify a specific printing device connected via a USB port.
Here is a breakdown of the feature:
No. The usbprint canondevicef144 entry is not malware. However, malware authors sometimes disguise malicious devices with similar names. To be safe:
If you see the entry even when no Canon printer is connected, run a full antivirus scan. usbprint canondevicef144
You previously had the printer working. After a Windows update or system cleanup, the driver files were corrupted or removed. The registry still retains the USBPRINT class reference, but the link to the .inf driver file is broken.
You plugged in the printer, Windows automatically detected the hardware, but it failed to download the full feature driver from Windows Update or the Canon website. The system falls back to the generic USBPRINT class, but cannot identify the specific model beyond the DEVICEF144 code. macOS: System Information → USB, Printers & Scanners
If you’re implementing a Linux kernel feature, udev rule, or driver module, here’s how you could create it.
If you want, provide a device’s lsusb output (Linux) or the Windows Device Manager device instance ID and I’ll map the vendor/product IDs to the exact Canon model and suggest the correct driver package.
The string "usbprint canondevicef144" is a USB Hardware ID (Device ID) used by the Windows operating system to identify a specific printing device connected via a USB port.
Here is a breakdown of the feature:
No. The usbprint canondevicef144 entry is not malware. However, malware authors sometimes disguise malicious devices with similar names. To be safe:
If you see the entry even when no Canon printer is connected, run a full antivirus scan.
You previously had the printer working. After a Windows update or system cleanup, the driver files were corrupted or removed. The registry still retains the USBPRINT class reference, but the link to the .inf driver file is broken.
You plugged in the printer, Windows automatically detected the hardware, but it failed to download the full feature driver from Windows Update or the Canon website. The system falls back to the generic USBPRINT class, but cannot identify the specific model beyond the DEVICEF144 code.
If you’re implementing a Linux kernel feature, udev rule, or driver module, here’s how you could create it.
© LivelyPortal 2026. All Rights Reserved.

Оставьте Ваши контактные данные,
и мы свяжемся с Вами в ближайшее время.
Или напишите отзыв.