This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 45%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi
Two issues with Universal Print in the last couple of days
1 - when printing for some users the client machine says the job has been sent to the printer but the job never appears in the print queue for Universal Print (ie https://portal.azure.com/#view/Universal_Print/MainMenuBlade/~/Printers)"portal.azure.com") or on the printer itself.
2 - when trying to add a printer using "Show printers and scanners associated with my Work or school" the printers show as installed and cannot be selected for installation but do not appear in the list of installed devices.
Has been working fine for approximately 6 months now. Printers are registered directly with Universal Print we don't use a connector.
Seems to be happening since windows updates Thursday 10th
Any pointers?
Thanks
Martin
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 20%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
We are having the same issues and mainly on windows 11.
Have you found any fixes?
For now I have rolled back to 23H2 and it all works again... so no not really I'm afraid!
I think I'll probably move to another print solution like Printix as we have a lot of label printers and an A0 plotter that Universal Print doesn't support anyway.
Hi, Is this only with Windows 11 client systems?
Thanks
I suspect the connector provider will need to make a code change due to the Mopria compliance changes in the IPP port on the latest Windows 11 update.
If you experience issues with Windows 10, then the Win 11 changes are not the root cause.