Issues WIth Printing After Installing HP Universal Driver for Windows 61.255.1.24923

[Kimboaticus]

I have around 12 office locations, each with a Windows Server 2019 Print server and various models of HP printer at said locations.  All total, we have more than 20 HP printers that are setup with the HP Universal Driver.  On Monday, I updated the Universal Driver to 61.255.1.24923 from 61.240.1.24630.  Once I did so, no one at any location was able to print to any of the HP printers using the Universal Driver.  When a job was submitted to the queue, they would get an error: "Job Aborted: Failure in UIO CreateAddressFromIPAddress".  The only way to get printing restored was to roll back to the older version of the UPD.  As this issue happened everywhere, the problem isn't a specific printer or printer model, nor a certain print server, nor a certain client PC.  So it has to be something about that newer driver but I have no idea what it could be.  Has anyone else experienced this issue or have any ideas what the problem could be?

To add more confusion, I installed the 61.255.1.24923 version of the UPD on my computer and then added one of the printers on the print server as a networked printer directly on my machine.  While I didn't get the above error about UIO, I did get a message about the printer certificate not being trusted.  I was given a dialog box to chose to either ignore the issue or cancel the connection.  I chose to ignore and things printed.  Any time I printed after that, even to other printers I added, they printed fine.  So I am wondering if the issue is that when going through the print server its not trusting the certificate but has no way to present that to the end user so it gets interpreted as "Job Aborted: Failure in UIO CreateAddressFromIPAddress" at the client end?  I guess another way to look at this is does the latest version of UPD require SSL Certificate secured communication to work?

[X-Savior]

I too am having the exact same issue with all our various HP printers.

We were running 6.8.0 PCL6 and PS driver packages without issue and then we updated and we see both of these issues.

Anyone have any solutions? I have rolled back our drivers to 6.8.0 for the time being.

[Kimboaticus]

I have opened a ticket with HP and am waiting on what they have to say but I also continued doing some testing.  I found that if I make new printers with the newer driver, they all work fine.  Its the "old" ones that don't work.  So, I tried deleting the existing printers and then recreating them and voila, they work.  I have also had some partial success with updating to the newer driver, exporting the printers to a file, deleting the printers that are using the Universal Driver, and then reimporting the printers from the file I created.  I say partially because it worked on one of my servers and not on a different server.  So far then, it seems that deleting a recreating from scratch is the only reliable way to get through this.  Not a great solution but it did work for me and might work for someone else if you are really stuck.

I'm still hoping HP will come up with something better though as rebuilding all your printer queues doesn't make a whole lot of sense.  I'm pretty much forced to go with the rebuild method because many of my workstations didn't roll back to the older driver when the server was rolled back and manually trying to downgrade the driver on a hundred machines is....sub-optimal.  So moving forward it is.  

[X-Savior]

Thank you for the info.

I will pick off a couple test printers and try recreating them and see if it helps.

Let me know what HP says. I will let you know how my tests work out.

[Kimboaticus]

Well, bad news on the ticket front.  HP closed my ticket tonight without explanation and after their business hours, all rather shady.  Ill be contacting them in the morning for an explanation.  Hopefully I dont get brushed off with this.  This is clearly an issue that needs investigation.  

[Kimboaticus]

Ok, so I finally got to talk to someone at support and here is what they said:

"I got an answer on what is going on here with the error 

Click on the link to see it: https://docs.microsoft.com/en-us/answers/questions/573124/microsoft39s-printnightmare-update-is-caus...

Pretty much they are calling this Microsoft's PrintNightmare. As you can see, that´s from the Microsoft website 

I found out it´s not only you having this error, so there are other people having the same exact error and similar ones, but does not belong to the driver per se 

Instead, it´s Windows that has the issue with those servers to work with new updates right now 

As you can see on the link, there is a specific path to do a work around on this or check out the comments, where there is apparently another work around:

This is how we found to fix it using the latest drivers. 

Deleted the print share and recreated it on the server using the new driver (instead of just updating to the new driver).

The point is that we made sure the issue is not coming out of the driver, but the whole servers for Windows"

I cant say that I agree with this assessment as our printers are deployed by GPO to the machine, not user so the drivers are being installed by the system.  Besides, I get the error right from the print server and I am an admin.  They do talk about recreating the printers and as I mentioned before, that has worked for me, with the exception of one print server.  No matter what I do, it wont work with the newer driver.  

[X-Savior]

Very interesting.

I am running a single Print Server (Server 2016) with only about 60 printers... so I decided to try blowing away a few printers and re-creating them. It did work and those printers are now running on the 7.0.1 Driver and printing just fine.

We have been avoiding updating our Print Server since August because of the changes made in the Sept Patches. Next week once I am done re-doing our drivers I might take a snapshot and try updating the server and see if anything breaks. I have read a lot of other forums/articles about issues after updating the Print Server as well.

With the changes M$ made we should all be running on the latest drivers... to hopefully avoid any other underlying issues.

[J_Tiedeman]

Removing the printer and adding it back worked for me. (In my case, I removed three instances of the printer.) Thank you!

[farmersLSD]

Thanks for this thread.  We're having a similar issue.  We get a certificate issue and a prompt to Continue or Abort, but I did set the printer to print directly and not spool or another setting, and get the same error as you.

I planned on migrating to 2019 anyway.  I wonder if that counts as creating a new share?  I rolled back temporarily, but have to manually remove all HP UPD drivers using their installer, then re-install from the server to get the error to go away.  I started a new thread, but no help from anyone regarding that.

[Kimboaticus]

Yeah, there hasnt been a whole lot of help from HP on this.  There is a patch to fix some printing issues that Microsoft has released to "Insiders" that Im hoping may actually fix things.  At this point, it looks likely that the patch wont be generally released until Patch Tuesday.  My guess on things is that the base issue lies with the spooler and it throws errors that the HP driver interprets in different ways and thats why we see a variety of issues.  But thats just a theory.  I guess Ill find out next week when and if the spooler patch is released.