Integrated Printing using Universal EMF Driver erroring

[Malkware]

OS: Windows 10 1909

Agent: Horizon 7.12 - Integrated Printing

Issue:

After applying February's updates any printer that uses the VMware Universal EMF Driver no longer functions. We receive various errors depending on the application, but nothing definitive.

If we have a printer on the client that, in the VM, uses the expected driver (eg Sharp printer driver), then that printer will function correctly.

Does anyone have any ideas?

[ofox]

It looks like that you could still see the printers in the VM session but printing to them failed to work, yes?

Perhaps you could take an initial debug per https://kb.vmware.com/s/article/85280

BTW using vendor's driver goes through NPD while VMware Universal EMF Driver goes through UPD, so that's the difference. Both are part of VMware Integrated Printing offering.

[rpeb1723]

Any luck resolving this?  I have a similar problem and have had a ticket open for over a month now with basically zero progress being made on it. 

[ofox]

Hi rpeb1723,

We have not received any further response from Malkware. Regarding your case have you checked out https://kb.vmware.com/s/article/85280? Let me know your ticket number so that I can have a check.

[rpeb1723]

Yes, I have looked at that article and we can see that the vmware-print-redir-server is crashing and have provided tons of logs but havent really gotten any information from support.  I will send you my case number

[antonpaloka]

Have you seen this thread? There was a windows update which may have broken printing in VMware Horizon when using AppVolumes

https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Print-to-PDF-broken-following-...

[rpeb1723]

We are not using app volumes

[Glenn77]

Any update, I'm hitting the same issue and don't want to add native print drivers for a bunch of user printers

[rpeb1723]

My issue was related to a specific font that was added to Windows for our specialized application that was crashing the printing.  They are including it in the next release and gave me a hotfix for now.  I dont think that it is the same issue the original poster was having though.

[Glenn77]

Any update on this, seeing same issue. Not using appvolumes.