We are having problems very similar to the issues described in
Every day we are having 8-15 users calling saying they are unable to print. The local Spoolsv.exe service is changing the registry key entry for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PS (v5.2) or for what ever their default printer is. We have tried with a different version of the driver and it will happen with our Xerox as well if that is their default. The problem itself is easy enough to fix by deleting the corrupt key, reinstalling the default printer and restarting the print spooler so they can print again. The problem is that it may happen again to them the next day, or it may be a month later. The specific entries being modified are string values forDependant Files, Help File and Monitor.
The errors in event log show:
The document Untitled - Notepad, owned by USERNAME, failed to print on printer {GUID}. Try to print the document again, or restart the print spooler.
Data type: NT EMF 1.008. Size of the spool file in bytes: 5332. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\COMPUTERNAME. Win32 error code returned by the print processor: 5. Access is
denied.
We are printing to a Win2008 R2 Server, We have Printer Driver Isolation Set on All machines for all drivers as well on the Print Server. KB2467753 has been applied to all the machines as well as our print server.
Suggests that we turn off CSR (Client-Side Rendering) for all of our printers. This simply by passes the problem that the local drivers are being corrupted, it will tax our print server much more and will take longer to print. We need to find out WHY this
registry key is being modified in the first place by the spoolsv.exe process and not try to bypass local rendering.
As a weird side note even with this driver corruption you are still able to print from adobe reader, they must be using their own driver files.