- #SAVIN C9025 PRINTER AUTHENTICATION ERROR INSTALL#
- #SAVIN C9025 PRINTER AUTHENTICATION ERROR DRIVER#
- #SAVIN C9025 PRINTER AUTHENTICATION ERROR PRO#
- #SAVIN C9025 PRINTER AUTHENTICATION ERROR PC#
File is likely corrupt or a victim of tampering. !!! sto: Catalog did not contain file hash.
#SAVIN C9025 PRINTER AUTHENTICATION ERROR INSTALL#
More tellingly, in the client-PC's installation-log (c:\windows\inf\), every attempt to install one of these "broken" HP drivers generates the following output:įailed to verify file ' UNIRES.DLL' against catalog.
#SAVIN C9025 PRINTER AUTHENTICATION ERROR PRO#
The printer which generated this message was a Color LaserJet Pro M177, but we've experienced this message with other HP printer-models as well, including the LaserJet P3015.
#SAVIN C9025 PRINTER AUTHENTICATION ERROR DRIVER#
This can occur if there is a problem with the driver or the digital signature of the driver. The print spooler failed to import the printer driver that was downloaded from \\ps1\print$\圆4\PCC\ntprint.inf_amd64_a7ac65d1b7714fb1.cab into the driver store for driver HP Color LaserJet Pro MFP M177 PCLmS. In the event-logs on the client machine (Microsoft/Windows/PrintService/Admin), I get the following message after one of these failed driver-install attempts: I get it when I log-in using my District Enterprise Admin credentials. I get this error regardless of the level of permissions my account has. That's when I get the error described above. I then go to a client machine, browse to \\PS1 (the server), and select the name of the printer I wanna install from the list of all the printers on PS1. Once the driver-installation finishes, I right-click Printers and choose "Add Printer," and then I select the driver I just installed when prompted. Then I open Print-Management on the server, create my port if one doesn't already exist, and then right-click Drivers and choose "install." When prompted to select a driver to install, I choose "Have Disk," and browse to the directory where the driver exists. I then copy them onto a "drivers" directory on the print-server. If it doesn't self-extract, I extract it using 7zip. Obviously I don't want the full-installer, so I try to download a barebones driver, if one is available. In the event that a printer isn't compatible with the Universal Print Driver, I download the Win7 圆4 driver. Obviously, I have doublechecked to ensure that I'm downloading the correct drivers from HP. We need these drivers to work under a 64-bit paradigm. And anyway, it wouldn't matter if it DOES work on 32-bit clients, because the entire world of computing is now firmly 64-bit. However, as computing has shifted firmly into the 64-bit paradigm, we have few 32-bit workstations left on our network with which we can test. It might only be 64-bit clients who are affected. We have not experienced this problem with other printers shared through our print-server - such as our 30 Sharp-brand printer/copiers, or our 15 or so Brother printers. For those printers, we lack a workaround. However, not all HP printers are compatible with that driver. We have discovered that, for whatever reason, the UPD for PCL6 printing, v5.7.0, works fine. This problem seems to affect ALL HP printers which are not using the Universal Print Driver. (We have made some changes AS A RESULT of seeing this error, in an attempt to fix it, but to no avail.) But the thing is, we hadn't made any changes in Group Policy prior to experiencing this issue. This would seem to indicate a problem within Group Policy. Please contact your system administrator." "A policy is in effect on your computer which prevents you from connecting to this print queue.
#SAVIN C9025 PRINTER AUTHENTICATION ERROR PC#
We can still install HP printers on PS1 as before - but on a client PC (Win7 Pro 圆4), when we navigate to PS1 and doubleclick the printer-driver to install it, we get a message which states: However, at some point over the past 3-4 months, things stopped working. I mean, basically, we would use Print Management on PS1 to create a TCP/IP port, then install the HP drivers for the desired printer, and then create the shared printer. Until recently, we had no problem installing, sharing, and using these printers in this method. These printers are connected to our network, and are shared via our print-server, PS1, which runs Windows Server 2012 R2. We have a number of HP laser-printers installed in various labs and classrooms around the district. I work for a large public school district. I'm not sure whether or not this forum is the right place to post an enterprise-level question.