cancel
Showing results for 
Search instead for 
Did you mean: 
4 Replies
CathyO-Xerox
Community Manager
Community Manager

Re: C605 Duplexing Letterhead Printing on the Wrong Side

Hello mdetwiler@greenoffic,

At this point I would recommend contacting the Support Department for more assistance: 1-800-821-2797.

Thanks,
CathyO-Xerox
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)!

Re: C605 Duplexing Letterhead Printing on the Wrong Side

Is this a known issue? Need to know how to proceed since the customer sees this as an issue. Sounds like it has been an issue that was maybe fixed in firmware at one point.

0 Kudos

Re: C605 Duplexing Letterhead Printing on the Wrong Side

Yes, that is how the media is being loaded to make the C605 print correctly. The issue is, the device is duplexing Letterhead even though the driver is set to 1-Sided print. This forces the user to load the paper different than the image on the Bypass tray and significantly slows the printing of Letterhead. I have duplicated this behaviour on multiple VersaLink devices and firmware versions.

0 Kudos
CathyO-Xerox
Community Manager
Community Manager

Re: C605 Duplexing Letterhead Printing on the Wrong Side

Hello there,

Are you loading the letterhead printed side down?

Thanks,
CathyO-Xerox
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)!

C605 Duplexing Letterhead Printing on the Wrong Side

Product Name: VersaLink C505 Multifunction Printer
Operating System: Windows 10 x64

I am having the same issue on a C605 running the latest software (v. 62.66.11). Setting the bypass tray to Letter/Letterhead/White and sending a print job from MS Word 365, the device duplexes the Letterhead and prints on the back of the page. I tested using the latest PCL6 and PS GPD drivers. They both get the same results. I duplicated on multiple devices running different firmware versions.

There are similar issues posted from 2017 that references a firmware update that did not correct the issue.

Is this still an issue? Is there a fix?

0 Kudos