Windows 11 January 2026 update breaks universal print

Hi:

I had logged this ticket with Microsoft support on January 18th when the problem started.  However, today they closed the case without notifying me.  When I followed up to see why it had been closed.  They did not consider this a break fix, and nobody else has reported the issue.  I want to find out if this is true.  I'm sure Azure Universal Print is used by a large number of customers.         

We have been using Azure Universal Print for well on three years without any issues, until Microsoft released the KB5077744 (OS Builds 26200.7627 and 26100.7627).  We use a staggered update schedule, so not all computers receive the update.  As soon as machines started to receive it, printing errors started to show the errors when trying to print:

When trying to view printer properties

Machines who never received the update could still print.  Here are the errors we see when selecting or printing to a universal printer.  The only thing mentioned about this update regarding printing was no new third-party drivers would be added to Windows Update.  

 Operation could not be completed (error 0x00000003)

The system cannot find the path specified

when trying to print.

AND

The ‘Universal Print Class Driver’ printer driver is not installed on this computer.  Some printer properties will not be available…..

 Sorry, I tried to attach pictures, but it would not let me post.  Ill see if I can add them after the initial post. 

Microsoft support had a look in Print Management on a Windows 11 machine to see the version of the Universal Print Class Driver on machines that could and could not print.

 On a computer that could not print (10.0.26100.7627).

On a computer that can print and never received the updates (10.0.26100.7623):

Since then, we have built some new computers that just received the OOB patch released on January 28th (KB5074752) and they have no issues printing.  The only other difference was the computer received 25H2.  However, I tried 25H2 on a broken computer, and it had no impact.  Just to make sure.