none
Print Driver being modifyied

    Question

  • We are having problems very similar to the issues described in

    http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/e2acb625-027d-47a9-b4a7-1616e270bcbc

    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 for Dependant 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.

    http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/19bb64cc-249e-4f36-a02d-2b43703d5a0d

    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.


    • Edited by 5cript3d Tuesday, February 05, 2013 11:28 PM
    Friday, January 25, 2013 8:47 PM

Answers

  • The driver patch information I'm sure is very useful, but it looks like the real issue is when you redirect a print server and Microsoft's spooler.exe service. We recently redirected our print server again and went through the exact same issue again with multiple print drivers being corrupted a day. Myself and a colleague put together a .vbs script and rolled it into an .exe to fix printers for our help desk. They simply put in the computer name that is experiencing an issue and it will scan their registry for blank values in the "Dependent Files" key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3.  If it finds it it will delete it and restart the print spooler service on that computer prompting it to re-download the driver.

    This will work regardless of the domain, printer brand or driver you are using. We have seen corrupted drivers on and this has been tested with Xerox, Samsung and HP printers with multiple driver versions.  When run it will pop up a box letting you know the driver it deleted and when it is done restarting the print spooler. If no corrupt drivers are found it will also let you know. I would recommend telling your users to restart the application they are attempting to print from for best results.

    Rem Created 6/3/2013
    Rem Created by Nathan Warren and Trevor McClanahan
    Rem We were tired of fixing printer drivers after redirecting to a new print server
    Rem Fix for the DEFAULT printer driver becoming corrupted
    Rem This script will search for empty data values in the Dependant Files Reg key signifying a corrupt driver
    Rem If it finds a blank value it will delete the key associated and restart the print spooler prompting the computer to redownload the driver from the print server
    
    
    
    
    
    
    
    
    
    
    Const HKLM = &h80000002
    
    Const StartKey    = "SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3"
    Const SearchValue = "Dependent Files"
    Const MatcharrValues   = ""
    dim result
    
    strComputer = InputBox("Enter Name of the Remote Computer:","Corrupt Printer Driver")
    result = False
    
    Set reg = GetObject("winmgmts:" _
        & "{impersonationLevel=impersonate}!\\" _
        & strComputer & "\root\default:StdRegProv")
    Set objWMIService = GetObject("winmgmts:" _
        & "{impersonationLevel=impersonate}!\\" _
        & strComputer & "\root\cimv2")
    
    
    FindAndDeleteKey StartKey 
    RestartSpooler
    Message
    
    Sub FindAndDeleteKey(key)
      WScript.Echo "[HKLM\" & key & "]"
      rc = reg.GetMultiStringValue(HKLM, key, SearchValue, arrValues)
      If Not IsNull(arrValues) Then
      For Each strValue In ArrValues
        WScript.Echo """" & SearchValue & """=""" & strvalue & """"
    	next
    	For Each strValue In ArrValues
        If StrValue = MatcharrValues Then
          DelKey HKLM, key
    	  result = True
    	  Exit Sub
        End If 
    	Next
      End If
      
    
      reg.EnumKey HKLM, key, subkeys
      If Not IsNull(subkeys) Then
        For Each sk In subkeys
          FindAndDeleteKey key & "\" & sk
        Next
      End If
    End Sub
    
    Sub DelKey(root, key)
      reg.EnumKey root, key, subkeys
      If Not IsNull(subkeys) Then
        For Each sk In subkeys
          DelKey root, key & "\" & sk
        Next
      End If
      rc = reg.DeleteKey(root, key)
      msgbox "Deleting [HKLM\" & key & "]"
     End Sub
    
    Sub Message()
    	If result = True Then
    	msgbox "Corrupt Driver Deleted and Spooler Restarted"
    		else
    	msgbox "No Problems Found"
    	End If
    End sub
    
    Sub RestartSpooler()
    	
    Set colListOfServices = objWMIService.ExecQuery _
    ("Select * from Win32_Service Where DisplayName ='Print Spooler'")
    For Each objService in colListOfServices
          objService.StopService()
        Wscript.Echo "Stopped Spooler service"
          Wscript.Sleep(5000)
        objService.StartService()
        Wscript.Echo "Started Spooler service"
    	
    Next
    
    End Sub
    

    • Marked as answer by 5cript3d Wednesday, June 12, 2013 3:01 PM
    Wednesday, June 12, 2013 3:01 PM

All replies

  • Can you please set up some data collection on a cross set of users in hopes that we can catch what is changing the registry settings in the act?

    We can run Procmon in a way that uses very little memory, saves the events to a backing file rather than the paging file, and can be run remotely by an admin.

    Below are the steps for configuring Procmon to only grab events that access a reg key called Dependent Files:

    1.       Set Procmon to drop filtered events under Filter.
    2.       Set the Filter to “Path Contains ‘Dependent Files’”
    3.       File - Export Configuration to save the configuration to a file (ProcmonConfiguration.pmc is the default.  Use “DepFiles.pmc”)
    4.       Save Procmon.exe and DepFiles.pmc to c:\procmon folder on the client.1.      

    Command line for Procmon on the client:

    Procmon /accepteula /backingfile c:\procmon\DepFiles.pml /LoadConfig DepFiles.pmc /Quiet

     

    To use PSExec to run remotely:
    1.       Copy procmon and config file to \\computername\admin$ share.
    2.       Run the following command from the remote computer:

     

    Psexec \\<computername  /accepteula -s  -u admin username  Procmon /accepteula /backingfile <path\filename.pml> /LoadConfig <config file>

    This should get us the Procmon data for the stack information for anything touching the Dependent Files key of any printer.  Please reply to this post with the Procmon log attached or a link to it.

    Thanks in advance!

    Tuesday, January 29, 2013 3:49 PM
  • You can't use "Psexec \\<computername  /accepteula -s  -u admin username  Procmon /accepteula /backingfile <path\filename.pml> /LoadConfig <config file>" As any switches after launching procmon through psexec aren't translated to the remote computer. We were able to launch "Psexec \\<computername> cmd" and then from there navigate to a .bat file we put on each computer with "Procmon /accepteula /backingfile c:\procmon\DepFiles.pml /LoadConfig DepFiles.pmc /Quiet". The big downside is that the filter only filters what you see in the results, it still captures events all day (about 40GB per computer) so we had them store the .pml files locally and have been clearing them out daily if no print issues occurred on that computer.

    We have this running on 15 different machines, so currently we are just waiting for one of them to have the issue to be able to dissect the log file. I will definitely post back when we have more information. Thanks for the post back, I was thinking something along the same lines, i was just afraid of the resources it would take.

    As a side note we turned off Client-Side rendering for a couple departments and they haven't experienced the issue. We don't want this workaround for the reasons mentioned in my first post.

    Tuesday, February 05, 2013 10:48 PM
  • Good catch on the cmd file for the switches, sorry about that. You can lower the number of events being captured in the settings of procmon so the overhead is less. Im on my phone, but I believe its

    under the settings menu.

    Wednesday, February 06, 2013 8:30 PM
  • We are experiencing the same problem here. For now, we just delete the cached driver and reinstall the printer. But like you know, this is not a permanent solution.

    We also have users reporting that Word crashes because of this same issue. Some users experience the problem multiple times a week, I'll set up procmon on their clients to see if we can get some information out of it.

    Also on a sidenote, I think it all started when we switched the print server to a Windows 2008 R2 server (was 2003 before). It affects both Vista 32bit and W7 64bit.

    Monday, February 11, 2013 1:30 PM
  • Did you find a solution?
    We are having the exact same problem.

    Windows server 2008R2 print cluster
    Windows 7x64 client computers
    HP Universal print driver 5.3

    Thursday, April 11, 2013 8:08 AM
  • Honestly we never found a permanent solution. The problem has only stopped happening as often as it used to (only 1-2 a day maybe) after we made sure every computer was updated with KB2647753 (print update) and we changed a couple of our printers to Server Side Rendering. All the procmon logs showed was that the print spooler was changing the driver key in the registry.

    We did find a really simple fix that can be done completely remotely though. Delete the key for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\{name of driver here} Then as long as their default printer uses that driver you can restart their print spooler and it will reinstall the printer driver and work correctly.

    I will also note that this issue started when we upgraded our print server from 2003 to 2008 R2 as well. Windows 7 x64 and HP universal 5.2. Wonder if the will ever actually fix the issue.

    • Proposed as answer by Shebnes Friday, April 12, 2013 7:06 AM
    Thursday, April 11, 2013 2:29 PM
  • Did you find a solution?
    We are having the exact same problem.

    Windows server 2008R2 print cluster
    Windows 7x64 client computers
    HP Universal print driver 5.3


    Hi,

    Hp UPD 5.3 is starting to be old (july 2011), I would update it. I didn't find 5.4 release notes, but a example in my shop 5.3 update to 5.4 stopped some bug with printer option. The tab was showing in the server but not on the computer (tab like to select black/white or color). So a lot of bug got corrected in the UPD over time.

    Found that's one, http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03635717/c03635717.pdf, but it's for HP UPD 5.6, it now support win8/win2012/newer hp's model and you got the list of fixes from 5.5 -> 5.6.

    Thanks


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/


    Saturday, April 13, 2013 4:57 AM
  • Hi

    We've been having this problem since October last year, and I've been following this thread for a few months now.  We have been unable to do any monitoring as our organisation is not really set up to do this. The fix we use is to patch the registry of an affected PC remotely and then get the user to reboot.  I may try simply restarting the print spooler next time.  I have been using EMCO's free "Remote Registry Exporter" to extract the Drivers key into multiple REG files and then do a text search for the string <"Dependent Files"=hex(7):00,00,00,00> to identify any new machines.

    However our environment has turned up some interesting trends.  We are a UK University and the affected machines are all Windows 7 open-area Student Use.  We have about 6000 W7 workstations in total (we are still in the process of migrating from XP), and 4000 of those are Student machines.  All our Student machines are Windows 7 now.

    These 4000 Student PCs are spread over 3 campuses, in Open Areas and Libraries, and we use a standard install image for all our student workstations, with hardly any changes for location - other than custom mapping to local printers.  But as these printers are all physically identical, the same driver (HP Universal PS v3.5) is always loaded.  

    We should theoretically see random occurrances of this issue across all student areas, but we don't.  We have only noticed this error in 1 area - a Library with 240 machines in it. Out of these 240, about 26 have ever had the error, and we have noticed a certain amount of "grouping" both in time and physical location.  7 machines on one row had the error, whereas a month later 4 machines in another bank had it.

    Looking at our environment, and assuming that all machines are identical, we asked what was different about this Library?  One possible conclusion is the Students.  Students on particular courses will be printing particular types of work, and it is almost always Word documents.  Students on Textile, Art, Business courses are all based around this particular Library and will use it's resources for printing (since it's the nearest to their teaching areas).  Our campus is spread out over the town of Nottingham, so students will tend to stay in their particular area.  This means the same students are printing the same type of documents in the same physical area.

    We also find that students don't tend to alert support staff if they can't print on a PC. They just move to another one that allows them to print successfully.  This is why a lot of the errored machines weren't noticed for months, because so long as a student can print out on another PC they don't report the faulty one.  The next student comes along, encounters the same error, moves to another PC and so on.  It is only at times of very high usage (generally round about Course Deadline time) when students can't find another free PC that they tend to report the one they're currently on.

    We suspect that the physical "grouping" may be down to a particular student with a particular type of document that causes this effect.  The first time it occurs they move to the next machine.  It breaks that PC so they move to the next, and so on until they've broken a whole bank.  At this stage maybe they amend their document or simply go elsewhere or maybe print it at home.

    Now that we have the ability to locate machines the day they break we will try to track down any students who had printing errors and find out what document they had errors with.

    -Dave

    Friday, April 19, 2013 9:35 AM
  •  I didn't find 5.4 release notes, but a example in my shop 5.3 update to 5.4 stopped some bug with printer option. The tab was showing in the server but not on the computer (tab like to select black/white or color). So a lot of bug got corrected in the UPD over time.

    HP loves to quickly remove all older release content soon as a new UPD comes out. Thus, now I harvest everything for every release.  When upgrading UPD releases, you know you're suppose to be using the AutoUpgradeUPD tool, right?  It basically recreates each print queue. Otherwise (in the past) there has been DEVMODE registry corruption which ends up with a whole bunch of weird bugs with print clients.


    UPD_5.4.0.11744_ReleaseNotes.doc

    New Features

    For complete details of new and existing UPD features and management, please reference the UPD System Administrator's Guide.  The following features were added to the UPD release:

     

    5.4.0.11744

      • Status "Automatic Configuration Disabled" displayed on Driver Properties Status-About tab when driver installation default “Print Auto-Configuration” is set to Disabled using Driver Configuration Utility or Driver Deployment Utility.
      • Request PIN print for every new print job when driver installation default “Request PIN (while printing)” is set using Driver Configuration Utility or Driver Deployment Utility.


      Issues Resolved

      The following list identifies key issues resolved in the release.

       

      5.4.0.11744

       

      6678     IPP driver vending failures from Windows Server 2003 x86

      8417     Form to Tray assignments incorrect when installing with /sm switch

      8486     Comments and Location information missing from MPA list with dynamic mode

      8870     UPD displays incorrect print speed when using MPA and virtual devices

      8874     Booklet layout incorrect when upscaling documents containing portrait and landscape

      9024     Copy count is set to zero when switching printing shortcuts in some applications 

      9257     Novell iprint: upd gets installed in dynamic mode when ShortInstallName=<servername> in iprint.ini on Novell

      9639     Warning message and event id 58 in event viewer after installing printer via point and print

      10356   PCL 5 driver shows incorrect driver model on Win 7 / Server 2008

      10445   Citrix StressPrinters v.1.3.2 fails with errors, may hang or crash the spooler

      10547   Citrix / Terminal Server users intermittently unable to launch application after printer mapping

      10549   Citrix / Terminal Server resources not released after mapping a printer

      10550   64 bit PCL5 driver copies hpcpn112.dll file to 32 bit directory during installation

      10555   Slow printing with n-up printing in large active directory environments

      10640   Hard disk not displayed as installed option after preconfig in non-bidi environment

      10795   PCL5 driver prints some documents incorrectly with office 2007 in vector graphics

      10847   Duplex not auto-detected during installation on some printer models

      10849   Color mode not properly detected during installation

      10955   Session 0 / Interactive Services Detection when creating printer connections ???

      11148   PS driver does not recognize output device from some MFP device models.

      11216   Incorrect output bin options form some MFP device models

      11240   UpdateNow connecting to P2035 fails with a communication error

      11567   PS Driver – Stapling occurs on wrong side of paper with M9040/M9050

      11659   Spooler crash on 32 bit Windows Server 2008

      11675   PS Driver not displaying custom paper sizes with Width > Length (i.e. 12x15) 

      Known Issues

      The following issues exist in UPD v5.3.1 and UPD v5.4.1

      10895   install.exe /s switch fails with error used with the /sm switch. 

      11760   Color Option selection defined on the Color tab, or through Driver Configuration Utility, saved as a Shortcut in the driver does not retain setting.  Example- setting “Print in Grayscale” saved as shortcut name “Print black and white” outputs job in color, preview icon may show as grayscale or color.

      UPD_5.5.0.12834_ReleaseNotes.doc

      New Features

      For complete details of new and existing UPD features and management, please reference the UPD System Administrator's Guide.  The following features were added to the UPD release:

       

      5.5.0.12834

      During installation, selecting the version specific driver designates the major.minor.subminor UPD version release as part of the installed driver name.  For example, HP Universal Printing PCL 6 (v5.5.0).  Prior versions (UPD 4.7 to v5.4.0) only used major.minor.  For example, HP Universal Printing PCL 6 (v5.4). 


      Issues Resolved

      The following list identifies key issues resolved in the release.

      5.5.0.12834

       

      5345     UPD 5.4 PCL5 was printing duplex jobs as single sided output (simplex) if papertype was selected

      5693     Error message "This command could not be completed" pops up when selecting "Update now"

      6075     Some driver settings defined via Printer Properties-Preferences did not retain after printer upgrade.  Settings defined via Printer Properties- Advance-Printing Defaults would retain

      6771     Shortcuts created with N-UP option and Duplex were changing after saving shortcut.

      6795     Encrypt job option not available in Windows cluster environments 

      6815     Dutch translation error in installer

      6818     Additional shortcuts created with CFM files can be deleted from preferences when the printer port is set to LPT1

      6828     PS and PCL6 using PowerPoint 2010, after changing the duplex settings from the printer properties, were not correctly reflecting on the PowerPoint Print settings.

      6835     Alternative letterhead mode not working with UPD PCL5 v5.4

      6836     UPD v5.3 and 5.4 PS and PCL6 using PowerPoint 2007, duplex flip pages up was printing duplex flip pages over

      6841     Manual duplex help screen appearing on server console instead of terminal server client

      6849     Missing Output bin options in Permanent instance of UPD 5.4 PCL6 using Host name / FQDN with CM6040mfp "3 Bin Stapler stacker - Mail Box mode"

      7247     UPD 5.2.6 space between characters randomly wrong with custom soft font on LaserJet 2055

      7251     Version of cioum.dll and registry key for CIO version was updated

      7256     Registry growing with UPD v5.2.6 in a cluster environment

      7270     @PJL JOB command missing when printing from Internet Explorer

      7272     Envelope DL paper size missing on non-English Windows 2008R2

      7276     Printing Shortcuts Paper Source using setting from Different Shortcut

      7320     Session 0 UI not getting closed

      7323     The 5 bin mailbox bins for the M603 were labeled incorrectly

      7328     Stapling option not showing up correctly for Stapler/Stacker model B522E in UPD version 5.3.1 and 5.4 PCL5 and PCL6.

      7632     UPD fails to install via USB Plug and Play with Smart Install disabled

      9601     UPD 5.4 and 5.5 USB Plug and Play fail to detect 3rd tray in LaserJet Pro 400 MFP M425

      11421   UPD 5.2.5 - Windows 2008 32-bit Spoolsv Crash

      11559   Landscape Duplex jobs print the back side flipped over with UPD 5.3.1.

      11587   Manual duplex help screen appearing on server console instead of client screen

      11744   UPD 5.2.6 PCL5 registry growth issues

      11760   New shortcut with "Print in Grayscale" enabled does not retain setting

      11762   Spooler crashing when running Citrix Stresstest utility as admin

      11850   Custom Paper Size smaller than 4 x 6 not displaying in driver

      11851   UPD 5.3.1, changing the default paper size to a new size does not display in the print dialog preview

      11890   UPD 5.4 does not provide stapling options for the LJ 9055/9065 Multifunction Finisher (Q3634)

      11900   GDRV tag leak with UPD PCL5 when printing some CorelDRAW documents on Win XP

      11933   UPD 5.4 PCL5 and PCL6 did not handle spaces in watermarks containing special characters


      Known Issues

      HP targets resolution in future releases of the UPD and/or driver tools within the Print Admin Resource Kit (PARK).

       

      5.5.0.12834

      UPD’s “install.exe /? help screen displays /aml as an unsupported installation switch; the switch is supported.

       

      5639:  After altering installation defaults using the Driver Configuration Utility or Driver Deployment Utility with Printer Status Notification= Disable, the UPD’s About tab displays Configuration Status as "No Administrator preferences" and "Auto configured."

       

      Driver issues specific to environments using Manage Print Administrator, UPD AD Template, or client side XML policy file:

       

      #RQ2891: Unlocked settings changed by the user during application context File-Print, Printer Properties, or Printer Properties-Advance should revert back to policy defined settings upon application exit

       

      #7596 Managed printer list containing subgroups displays slowly upon loading in client application for users not in the Administrator group, impacts UPD 5.1 and higher.

       

      #7243:  Policy settings are not maintained after navigating between driver shortcuts.   For example, print in grayscale defined within a policy may not be honored by the driver after a user navigates between printing shortcuts in the UPD.

       

      #8604: Print settings defined within a policy and later changed to a new setting and not locked may cause the UPD to ignore settings defined by the user during FILE-PRINT.  For example, policy defines duplex enabled and not locked, the policy is changed to duplex disabled, users selecting “Duplex” during FILE-PRINT may receive simplex printed output. 

       

      #9452: New template creation, when saved, replaces the existing template under Manage Print Policies, limiting product to only one template.  Same issue observed in UserMode settings.  MPA v2.6.5 and v2.6.7.

       

      #1661/6760:  UPD v5.5.0, after configuring a policy setting, the setting may become locked in the driver even if that setting was defined as unlocked within the policy.

       

      #9006:  UPD 5.5.0 causes crash in Windows Explorer using Managed Print Administrator (MPA) Graphics Mode printer list.  Customers using or planning MPA deployments are advised not to upgrade to UPD v5.5.0.

       

      #8257 UPD 5.4 and 5.5.0:  Change an existing printer list or modify the view of an MPA list in the MPA after print queue has been configured with /gpolicy and the MPA printer list does not appear in Devices and Printers selecting the printer queue, Printer properties or Printer preferences.  Workaround is reboot host. 

      UPD_5.6.0.14430_ReleaseNotes.doc

      Enhancements/Features

      • Support for Windows 8 and Windows Server 2012.

      Note:  UPD Dynamic Mode printing from Windows Store apps is not supported.  To print from Windows Store apps, create a permanent instance printer.  

      • New driver initialization routine to prevent interactive services detection (Session 0) messages
    • MPA, UPD AD template, or client side XML policy settings are enforced for printing defaults, and can only be overridden on a per-job basis.   Note that locked policy settings may not be changed at any time by end user.

    Fixes/Fixes History

    Key issues resolved in this release of the HP Universal Print Driver v5.6.0.14325

    Issue ID

    Description

    1661

    Policy settings in AD/MPA are locked in application even if unlocked in the policy

    6771

    Orientation and binding incorrect with some custom shortcuts

    6815

    Error in Dutch translation of UPD installation screens

    6836

    Incorrect duplex binding from Microsoft PowerPoint with N-up printing

    7323

    5-bin mailbox bins mislabeled with HP LaserJet M600 and CE997A mailbox

    7410

    Install.exe with custom scripts hangs after approximately 100 print queues

    7596

    Slow printer list population with MPA managed printer lists

    7993

    5-bin mailbox bins mislabeled with HP LaserJet P4515 and CB520A mailbox

    8257

    MPA managed printer list is not displayed in printer properties or preferences

    8284

    Documents with mixed orientation do not print correctly

    8422

    Unable to communicate with printer using custom SNMP Get Community Name in Dynamic Mode.

    8604

    Changes to unlocked policy settings are ignored at the application level

    8965

    Incorrect output from Microsoft PowerPoint with HP EasyColor enabled (PCL 6 only)

    9006

    Windows Explorer crashes when viewing graphic printer lists from printing preferences when using UPD with a Managed Printer List

    9213

    HP LaserJet 9040 missing option to print to the Left Bin (Face Up) when no output accessory is attached

    9326

    UPD factory default shortcut shows Letter paper size and non-metric values for UK English and other West European countries

    9333

    Device type and status notification incorrect for DCU pre-configured settings (PCL 6 only)

    9651

    DL Envelope size is not avaialble (PCL 5 and PCL 6 only)

    8919

    FastRes 1200 and ProRes 1200 resolutions missing from print quality tab (HP LaserJet P3005)

    10912

    Plug & Play failures with HP LaserJet P2055 and M401<sup>1</sup>

    12070

    Intermittent installation errors/failures in Citrix XenDesktop

    12574

    Oficio paper size does not auto-duplex on HP LaserJet M600 series

    <sup>1</sup>If present, the inf files from previous UPD versions must be removed from the system.   The RemovePnPDrivers utility in the Printer Administrator Resource Kit (PARK) can facilitate inf file removal.    

    Deprecated features

    UPD v5.6.0 does not contain a UPD PCL 5 release.  Beginning with UPD v5.5.0, PCL 5 began a yearly update release cycle, therefore the most current version of UPD PCL 5 may not match the version number release for UPD PCL 6 and PS.  The most current UPD PCL 5 version is available on www.hp.com/go/upd.

    UPD PCL 5 is not supported on Windows 8 or Server 2012.

    Issues and Workarounds

    The following list contains the known issues in this release and available workarounds.  HP targets resolution for these issues in future releases of the UPD and/or print driver tools within the Print Administrator Resource Kit (PARK). 

     

    Issue ID

    Description

    Workaround

    6816

    UPD preview of printed output shows the staples in the wrong position when selecting “Print on both sides” and “Flip pages up” for landscape orientation. 

    Disregard preview.   The staple location is dependent upon page orientation and device capabilities

    8041

     

    Windows Server 2003 Terminal Server redirected print queues are missing tabs, paper sizes/types and trays in remote session. 

    No workaround for Windows Server 2003.   Note: This behavior is not seen in Windows Server 2008 Terminal Server and newer with Easy Print.

    8218

     

    Intermittent error message “Object is not connected to server” when creating a permanent instance printer in Dynamic Mode with a restricted user account.

    Set Driver Isolation Mode to “none” and retry.

    9212

     

    A delay is seen the first time the driver UI is opened after installing a printer via point and print on client computers with McAfee antivirus software installed.

    The delay is only seen the first time the UI is opened.   The delay is not seen when the UI is reopened. 

    9664

    Trays, Media information and Watermarks are displayed in English on systems with the Windows Multilingual User Interface Pack (MUI) installed and set to a non-English language

    No workaround available.

    10841

    Registry growth in HKU\.DEFAULT\ Software\Hewlett-Packard is seen on Windows Terminal Server systems.

    No workaround available.

    11791

    A delay is seen when opening a print queue on a remote server through Windows Print Management Console

    Log into the remote server through Remote Desktop Connection or run the Print Management Console from a computer that does not have local print queues using HP UPD

    12323

    The “pin to print” dialog may be displayed in the background (hidden) instead of in the foreground

    Click the “pin to print” icon in the taskbar to bring the dialog to the foreground

    12650

    HP UPD PS driver does not show all supported print resolutions for HP LaserJet M401

    No workaround available

    Friday, April 19, 2013 6:10 PM
  • excellent information.

    Thanks


    Alan Morris Windows Printing Team

    Monday, April 22, 2013 10:04 PM
    Answerer
  • The driver patch information I'm sure is very useful, but it looks like the real issue is when you redirect a print server and Microsoft's spooler.exe service. We recently redirected our print server again and went through the exact same issue again with multiple print drivers being corrupted a day. Myself and a colleague put together a .vbs script and rolled it into an .exe to fix printers for our help desk. They simply put in the computer name that is experiencing an issue and it will scan their registry for blank values in the "Dependent Files" key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3.  If it finds it it will delete it and restart the print spooler service on that computer prompting it to re-download the driver.

    This will work regardless of the domain, printer brand or driver you are using. We have seen corrupted drivers on and this has been tested with Xerox, Samsung and HP printers with multiple driver versions.  When run it will pop up a box letting you know the driver it deleted and when it is done restarting the print spooler. If no corrupt drivers are found it will also let you know. I would recommend telling your users to restart the application they are attempting to print from for best results.

    Rem Created 6/3/2013
    Rem Created by Nathan Warren and Trevor McClanahan
    Rem We were tired of fixing printer drivers after redirecting to a new print server
    Rem Fix for the DEFAULT printer driver becoming corrupted
    Rem This script will search for empty data values in the Dependant Files Reg key signifying a corrupt driver
    Rem If it finds a blank value it will delete the key associated and restart the print spooler prompting the computer to redownload the driver from the print server
    
    
    
    
    
    
    
    
    
    
    Const HKLM = &h80000002
    
    Const StartKey    = "SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3"
    Const SearchValue = "Dependent Files"
    Const MatcharrValues   = ""
    dim result
    
    strComputer = InputBox("Enter Name of the Remote Computer:","Corrupt Printer Driver")
    result = False
    
    Set reg = GetObject("winmgmts:" _
        & "{impersonationLevel=impersonate}!\\" _
        & strComputer & "\root\default:StdRegProv")
    Set objWMIService = GetObject("winmgmts:" _
        & "{impersonationLevel=impersonate}!\\" _
        & strComputer & "\root\cimv2")
    
    
    FindAndDeleteKey StartKey 
    RestartSpooler
    Message
    
    Sub FindAndDeleteKey(key)
      WScript.Echo "[HKLM\" & key & "]"
      rc = reg.GetMultiStringValue(HKLM, key, SearchValue, arrValues)
      If Not IsNull(arrValues) Then
      For Each strValue In ArrValues
        WScript.Echo """" & SearchValue & """=""" & strvalue & """"
    	next
    	For Each strValue In ArrValues
        If StrValue = MatcharrValues Then
          DelKey HKLM, key
    	  result = True
    	  Exit Sub
        End If 
    	Next
      End If
      
    
      reg.EnumKey HKLM, key, subkeys
      If Not IsNull(subkeys) Then
        For Each sk In subkeys
          FindAndDeleteKey key & "\" & sk
        Next
      End If
    End Sub
    
    Sub DelKey(root, key)
      reg.EnumKey root, key, subkeys
      If Not IsNull(subkeys) Then
        For Each sk In subkeys
          DelKey root, key & "\" & sk
        Next
      End If
      rc = reg.DeleteKey(root, key)
      msgbox "Deleting [HKLM\" & key & "]"
     End Sub
    
    Sub Message()
    	If result = True Then
    	msgbox "Corrupt Driver Deleted and Spooler Restarted"
    		else
    	msgbox "No Problems Found"
    	End If
    End sub
    
    Sub RestartSpooler()
    	
    Set colListOfServices = objWMIService.ExecQuery _
    ("Select * from Win32_Service Where DisplayName ='Print Spooler'")
    For Each objService in colListOfServices
          objService.StopService()
        Wscript.Echo "Stopped Spooler service"
          Wscript.Sleep(5000)
        objService.StartService()
        Wscript.Echo "Started Spooler service"
    	
    Next
    
    End Sub
    

    • Marked as answer by 5cript3d Wednesday, June 12, 2013 3:01 PM
    Wednesday, June 12, 2013 3:01 PM
  • We are having the same issue described (corrupt or garbled output on multiple pages on HP UPD print). I appreciate the work around scripted solution posted as the "answer", and we are looking at using it. However, this isn't really a fix, it is a work-around. Does anyone know if Microsoft is aware of the problem and is working on a permanent solution?

    http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/e2acb625-027d-47a9-b4a7-1616e270bcbc

    http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/19bb64cc-249e-4f36-a02d-2b43703d5a0d

    http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/08bc6b4b-0190-40b0-be16-8b82249148e4

    New Windows Server 2008 R2 print servers, Windows 7 64bit clients using, machine-policy printer connections. KB2647753 installed on both servers and clients. Symptoms observed with "HP Universal Printing PCL 6" (v5.5.0, v5.6.0, and v5.6.1) driver, but not observed on Ricoh Aficio "PCL6 Driver for Universal Print" driver. Symptoms not observed on WinXP SP3 32bit clients.

     
    Monday, June 17, 2013 7:00 PM
  • This is close to resolution. See http://social.technet.microsoft.com/Forums/windowsserver/en-US/e2acb625-027d-47a9-b4a7-1616e270bcbc/print-drivers-on-windows-7-clients-missing-dependent-files#f33d49b3-237d-4714-a06d-edefbb7668f8
    Thursday, September 26, 2013 3:31 PM
  • hello all,

     Last Week after Microsoft Patchday we have more than 60 different Clients from 1000 Client that can't print because PCL Error.  What a horror. From 2008 R2 Printserver we can print to the Printer. From Client we can't print. User has no Admin Right and we must deinstall the printer, reboot and reinstall the same printer. We have 500 HP and Ricoh Printer with Universal Printer Driver Version 5, 5.3, 5.5

    What is the trigger, is this a Microsoft or a HP Problem

    What is the summary from this problem


    Chris


    • Edited by -- Chris -- Friday, November 29, 2013 9:37 AM
    Friday, November 29, 2013 9:09 AM
  • I think Microsoft has released a fix on November 15... but I am unsure of its applicability. See http://support.microsoft.com/kb/2864755 which describes the cause (if not the effect entirely) in Windows 7 (client OS). The KB 2864755 points to a resolution http://support.microsoft.com/kb/2896881 although the hotfix description in KB 2896881 is a resolution only for Windows Server 2008 R2 SP1 in Terminal Services mode (not Windows 7)!!

    It seems like Microsoft has dropped the ball on this one. We also need a similar hotfix for Windows 7.

    The above is a cross-posted with forum question http://social.technet.microsoft.com/Forums/windowsserver/en-US/e2acb625-027d-47a9-b4a7-1616e270bcbc/print-drivers-on-windows-7-clients-missing-dependent-files#f33d49b3-237d-4714-a06d-edefbb7668f8

    • Proposed as answer by George Perkins Monday, December 02, 2013 4:36 PM
    Monday, December 02, 2013 4:32 PM
  • I got a phone call from Microsoft Development after asking our Microsoft Premier Agreement Technical Account Manager to escalate. They believe everything is in order and we should apply the hotfix in KB 2896881.

    The symptom we have is documented in KB 2864755. It indicates Windows 7. That KB redirects to 2896881.

    Although 2896881 isn’t our symptom, because 2864755 redirects us, we should accept 2896881 as our solution. The updated DLLs are shared by Windows Server 2008 R2 and Windows 7; therefore as 2864755 indicates, 2896881 is applicable to the workstation OS symptoms we have observed.

    We believe the hotfix is stable, and will apply it to the server OS as well. Some servers do printing and may benefit.

    Friday, January 24, 2014 5:38 PM