| Contains Resolution: |
|
|
Ran into this on our servers. Workaround #1 from HP Support Alerts resolved this and is easy to implement: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01682861&dimid=1001553288&dicid=alr_mar09&jumpid=em_alerts/us/mar09/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts
Workaround #1
The current suggested workaround for customers that wish to continue to use the latest discrete PCL 6, PCL 5, or Postscript drivers from hp.com will need to perform the following:
1.Open Notepad and save the file as hpzbdi32.msi or hpzbdi64.msi. This zero-byte file will not contain any data.
2.Navigate to the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3 directory and locate the hpzbdi32.msi or hpzbdi64.msi file. Rename the file to hpzbdi32.old or hpzbdi64.old.
3.Copy and paste the newly created zero-byte file named hpzbdi32.msi or hpzbdi64.msi into the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3 directory.
4.Verify functionality.
NOTE: Depending on configuration, it may be necessary to stop the spooler, perform the steps in the workaround, and restart the spooler once the steps have been completed. NOTE: Please note that if the customer performs this workaround and a reinstallation of the driver is performed, the zero-byte msi file will be overwritten by the original msi file in the original driver package. All steps in the workaround would need to be performed again.
|
|
|
|