Showing results for 
Search instead for 
Did you mean: 
New Member
New Member

Faded print from a single laptop using same driver as anybody else

Product Name: Other - specify product in post

Hi there,


I have one laptop, windows 7 x64, and using the same driver everyone uses for a Xerox Workcentre 7132, which prints in faded whatever in B/W or Colour.

I've checked drivers versions, and they're (still) all the same as the other laptops. Neverless this one started printing in "fade mode".

The printer is on PCL mode and the driver version is PCLXL.DLL vs.6.0.5479.0


Any clues?


Thanks in advance.

Tags (1)
0 Kudos
2 Replies
Community Manager
Community Manager

Re: Faded print from a single laptop using same driver as anybody else

Hi ribeil02,

Thank you for using the Support Forum. Please make sure that the driver is not set on the draft mode.  Here are the steps to check on the draft mode.

  1. Click on the [Start] button, and then select [Devices and Printers] from the menu. The Devices and Printers window will be displayed.
  2. Right click on the printer icon and select [Printer Properties] from the menu. The Properties window will be displayed.
  3. Click on the [General] tab.
  4. Click on the [Printing Preferences] button. The Printing Preferences window will be displayed.
  5. Click on the [Advanced] tab.
  6. Click on [+] next to the Image Options option.
  7. Select either [Off] or [On] from the Draft Mode pull-down menu.
  8. Click on [Apply].
  9. Click [OK] twice.
  10. Close the window.

If the draft mode is off then please consider contacting your support centre for further assistance.

Community Manager

Be sure to click Kudos for those who have helped you.
Select Accept as Solution for posts that have helped to solve your issue(s)!

New Member
New Member

Re: Faded print from a single laptop using same driver as anybody else

Hi Cheryl,


sorry to get back so late, but this user only returned today to the office and we've tried your suggestion and unfortunately we didn't found some options you've mentioned.

We managed to solve this thing out with a driver reinstalation and everything got back to normal.

Thanks for your support.