Forum Discussion

JDBaggs's avatar
JDBaggs
Copper Contributor
Feb 10, 2026

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. 

10 Replies

  • Bruce2020's avatar
    Bruce2020
    Copper Contributor

    Could it be related to this nugget of news

    "As of early 2026, Windows 11 has phased out support for legacy V3 and V4 printer drivers via Windows Update, causing older printers to stop working or fail installation. To fix this, manually download the latest driver directly from your printer manufacturer's website"

    Your printers show as type 3 and 4 if that relates to drivers 

    • JDBaggs's avatar
      JDBaggs
      Copper Contributor

      Hi:

       

      I was thinking a backend change as well when the problem started. Microsoft says there were no changes.  However, the timing was definitely right.  Although, machines with the patch could print to the exact same printers that failed for machines that received the update. 

       

      We are looking into printers that are Mopria certified, IPP enabled, and can direct register. This will eliminate the non-Microsoft drivers (except for vendor specific PSAs).

       

        

          

        

            

                                                    

  • Deborahind's avatar
    Deborahind
    Copper Contributor

    Collect screenshots of the error messages. Log the affected updates and machines. Keep track of the machines that have or haven't received KB5077744 and their status. Document any workarounds you have found (e.g., rolling back the update, workaround steps).

    • JDBaggs's avatar
      JDBaggs
      Copper Contributor

      Refer to the screen shots that I added to a reply I posted.    For whatever reason, I couldn't get them to attach to the original post.  Most of the items you mentioned are in there.    

      We did pause and uninstall the quality update via Intune Autopatch.  I believe the pause was the only thing that prevented all of machines from encountering the problem.  This is the weird part.  Once a machine had the update uninstalling that patch did not rollback to driver version 7623. 

      As per a workaround, there was a manual fix.

      Remove all printers that used the Universal Print Class Driver (otherwise the driver would be in use), then remove and re-add the driver.  This added the 7623 version back.


       

                          

  • HardCopy's avatar
    HardCopy
    Copper Contributor

    Hey JD,

      kind of off-topic...but I'm curious about the statement "The only thing mentioned about this update regarding printing was no new third-party drivers would be added to Windows Update."

     I looked and couldn't find any mention, in the KB, that relates to your above statement.

     I'm curious if you are referring to the well-knownhttps://learn.microsoft.com/en-us/windows-hardware/drivers/print/end-of-servicing-plan-for-third-party-printer-drivers-on-windows#overview that is underway?

    • JDBaggs's avatar
      JDBaggs
      Copper Contributor

      Hi:
      Yes, that was what I was referring to.  You're right not directly related to the quality update, just the timing of when the problem started to happen.  We were just looking at all changes to the environment that may have had any impact.            

  • JDBaggs's avatar
    JDBaggs
    Copper Contributor

    Here are the screenshots I couldnt attach earlier

    Driver versions on working

    and broken computers

     

    • Sean_Dyer's avatar
      Sean_Dyer
      Copper Contributor

      Maybe run PROCMON on the workstation to see what is actually failing. That's typically my next step. 

      • JDBaggs's avatar
        JDBaggs
        Copper Contributor

        Hi:

         

        Microsoft sent a script to collect a trace as I duplicated the error.    

        >.\TSS.ps1 -Scenario UEX_PrintFull

         

        Most of the results were around invalid driver, printer properties and missing components.      

        **************************************

        Driver manifest file not found:

        C:\Windows\System32\DriverStore\FileRepository

        \prnms014.inf_amd64_737db2ea136955d5

        \MSMPS-manifest.ini

        ****************************************

        DrvPrinterEventFailed

        hr=0x80070002 (The system cannot find the file specified)

        PRINTER_EVENT_INITIALIZE

         

        What this means (very important)

        • prnms014.inf = Microsoft Mopria / Microsoft IPP Class v4 driver
        • MSMPS-manifest.ini is mandatory for v4 driver initialization
        • If this file is missing:
          • v4 driver cannot initialize
          • PrintConfig fails
          • The printer never becomes usable