I am in IT Support and have a customer that is having problems with a VersaLink C405. The device was purchase about 45 days ago. When sendng documents from Windows 10 Creator PC's, the colors come out wrong. They have one document that is a table with a light blue background and it prints out pinkish gray. Same document from a non Creator PC prints fine. I have tried different drivers, V3, V4 PCL6 to eliminate any PS issues. The main docs are from Word 2013, but also a label application gives color issues as well. For a workaround, I shared the printer connection from a non Creator laptop and jobs printed through there are perfectly fine. Any body seen this? It has the latest General Release of 68.10.91 for firmware. Any ideas?
As far as I know that has never been reported anywhere, and since the drivers are independently made using different files from different teams, and the V4 introduces MS, not just Xerox, and the files for the V3 are identical for all OS's, what you are seeing should not be possible, because the Applications should be the issue, but a shared driver on another Windows 10 (non creator's) would still have the same issue in that scenario.
I have Version 1703 (OS Build 16199.1000)
Build 16199.rs_prerelease.170513-2252 Insider preview running and see no such issue.
If I were you I would call Xerox for support assuming you have a maintenance agreement with them, they will want a config sheet for the device and will need a few things to get started on escalating the issue over to MS to possibly fix it since it would appear they caused the issue from what you are describing.
A Print to File for the same job before and after the creators update using the same driver would speed the issue along nicely.
Thanks for the response! The customer did not get a service contract when they purchased. I am going to be working with them to secure one. So I will wait before contacting support.
I'll see what I can do about getting the proper files ready and we will escalate this through Support afte that. I totally agree that this should not be occurring, but the workaround is by sharing the connection from the non-Creator edition.