VMWare Horizon usb redirect not working for printers

[scottjones74]

printing to USB printers has stopped working since upgrading to horizon 2206 (have upgraded to 2209 to see if that helped and it did not).

we are non-persistent instant clones, print drivers are installed in the image, USB redirect is installed with the agent, USB is allowed in horizon admin.   Even checked GPO's and registry ([HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Installer\Features_HorizonAgent] "PrintRedir"="Local" for VMware printing )

It was working on previous versions of horizon 8.  We are using windows 10 enterprise version 21H2.

The issue occurs on zero clients, thin clients, and horizon client from a windows laptop, so I know its something with the image or a setting.  I have built two new master images from scratch to try and find the issue but cannot.  The printer is “seen” in the control panel, but it does not load the driver.  If I run the master image, the driver is loaded immediately.  

any help or direction is appreciated, this should be a simple fix but i cannot find it. 

[ofox]

@Jackson_Goverme  kindly check this out.

https://support.microsoft.com/en-us/topic/march-28-2023-kb5023778-os-build-22621-1485-preview-d490bb...

• This update addresses an issue that affects USB printers. The system classifies them as multimedia devices even though they are not.

[peetey100]

This update seems to be for Win11 not win10 where the above problem is?

[jhol5]

windows 10 21H2 / 22H2

March 21, 2023—KB5023773 (OS Builds 19042.2788, 19044.2788, and 19045.2788) Preview - Microsoft Supp...

windows 11 21H2

March 28, 2023—KB5023774 (OS Build 22000.1761) Preview - Microsoft Support

windows 11 22H2

March 28, 2023—KB5023778 (OS Build 22621.1485) Preview - Microsoft Support

Each one states:

• This update addresses an issue that affects USB printers. The system classifies them as multimedia devices even though they are not.

[alepev]

Hello, I am writing here because we were struggling with this problem for quite some time now and this thread gave me the necessary hint to solve it. When connecting the printer to the Notebook via USB and redirecting it to the virtual machine, everything worked fine.

Info about our case:

The ThinClient is configured for external use and not in our network, the printer also isn't in the network for the same reason which is why we connect it via USB.

Printer: HP Laserjet Pro 400  M401dn

Thinclient Model: Wyse 5070 Pentium

OS-Version: Dell ThinOS PCoIP (8.6_810)

USB Redirection is configured in the Wyse Management Suite.

The Thinclient connects to a Virtual Computer Windows 10 22H2 via VMWare Horizon Version 2206.

When connecting the Printer via USB, the ThinClient gives two different ID's as output: "(PID: 0x15XX, VID: 0x03XX)" & "0x03f0,0x152a,0x07,0XXX,0XXX".

We had a USB Redirection for this: (PID: 0x15XX, VID: 0x03XX)

The Printer on the virtual computer got displayed the same way as in the original attachment of this thread (i attached it here again).

When deleting the USB Redirection, the printer got recognised by the ThinClient and I was able to print out a test page from the Thinclient directly, but it didn't get recognised at all on the VC. When adding the USB Redirection again, the Thinclient doesn't recognise it as a printer anymore, and it got displayed the same way again on the VC as in the attached Image.

After adding the additional USB redirection for this "0x03f0,0x152a,0x07,0XXX,0XXX", the VC didn't show an error anymore for the device, but it still only got recognized as a device and not as a printer. After deleting the original USB redirection (PID: 0x15XX, VID: 0x03XX), the printer finally got recognized correctly by the Computer and everything worked.

I hope I was able to help out with this comment.