Unsolved
1 Rookie
•
1 Message
0
28
December 19th, 2025 14:28
OptiPlex 3000 Thin Clients ThinOS 10 HP Printer USB Redirection WinUSB Driver Error
I’m trying to determine whether others are seeing the same behavior with Dell ThinOS 10 HP Printer USB redirection and Omnissa Horizon.
Environment
ThinOS: 2511
WMS: 5.3 On Prem Pro
Omnissa Horizon Client
Protocol: Blast & PCoIP
VDI OS: Windows 11
USB redirection: Enabled in WMS
Affected Devices
HP LaserJet printers with composite USB interfaces, including:
HP LaserJet 400 M401
HP LaserJet M402
HP LaserJet Pro 4001
HP LaserJet M404
Affected interfaces are non-print functions (e.g. MI_00, MI_01, MI_03, MI_04) that are expected to bind to WinUSB.
Issue Description
When these printers are redirected from ThinOS → Horizon → VM:
The printer device appears in the VM
The HP print driver loads correctly
WinUSB does NOT auto-bind to the Universal Serial Bus devices interface
The device is missing the compatible ID:
USB\MS_COMP_WINUSBAs a result, Windows reports “driver not available” for the USB interface
However:
The same printers, when connected to the same virtual machine sessions on:
Dell Zero Clients, or
Physical Windows PCs
DO enumerateUSB\MS_COMP_WINUSBand auto-bind WinUSB correctly.
Notes:
Manually forcing WinUSB in Device Manager works immediately
I believe a possibility is that Microsoft OS Descriptors are not being forwarded by ThinOS USB redirection.
This behavior is consistent and reproducible.
- Zero Clients with the same virtual machine sessions work correctly, so this appears ThinOS-specific.
In environments with many persistent or non-persistent desktops:
Manual WinUSB binding is not scalable
The issue reappears after image refreshes
Questions for the Community
Is anyone else seeing missing
USB\MS_COMP_WINUSBwhen redirecting composite USB devices from ThinOS, resulting in a driver error?Has anyone found a ThinOS or WMS setting that can solve this?
Any success cases with HP Printers+ ThinOS + USB Redirection?


