Long ago I deployed the Xerox Global Print Driver PCL type 3 v5377.600.0.0 (for WorkCentre 133) from Windows 2012 Server Essentials to about 10 x64 Windows 8.1 clients, and today noticed by chance that this folder on my PC contained 13gb of files, including entire folders copied from various locations on my C: drive: C:\Windows\System32\spool\drivers\x64\3\Xerox\Product Data\Public\DCPs\x2UNIVR1\V5.0
I checked this folder on another Windows 8.1 PC on our network and they too had a ton of unrelated files (see screenshot) amounting to about 5gb of data. But four others that I checked did not have this issue.
In 10 years of PC support I have never seen such an issue and the only thing that came to mind is that I believe on my PC and the second with this problem, I had previously run he online repair command DISM /Online /Cleanup-Image /RestoreHealth and had noticed also when running SFC /scannow that one of the error was related to a Xerox driver.
Beyond that I am stumped and am hoping someone has a clue as to why this would happen?
Thank you for using the Support Forum. I have not seen this before. Please take a look at the support site for the Global driver and see if you can find an answer. If not please consider contacting your support centre for further assistance.
Any new information about this subject?
It's kind of scary...
Now, it's the second time this happend on my computer Windows 8.1-64bit.
The printer is a Xerox ColorCube 8580, it used to be a 8570.
Sometime in April 2015 probably, I installed the new printer drivers
X-GPD_5.404.8.0_PCL6_x64.exe and X-GPD_5.404.8.0_PCL_x64.exe
downloaded from Xerox.
On May 21 about 10 Gbyte of Data was copied to the path
out of the root of C:\.
After checking the data I decided to move it away, since there is not much free space available on my C.
Both times the sudden copying of data turned the drive C red because there is not much space left.
Yesterday again, on 9.32 am I printed out on the Xerox printer and on 9.36 the timestamp is on the copied folders below the Xerox-path.
I have no clue what it needs to make the difference. I don't print a lot, but definitely, I was printing out a couple of times in between the two occurences.
That morning I printed out at least one page using greyscale rather than color.
Could this cause all that trouble?
I'm pretty clueless what to do or how to fix it.
I know this topic is old, but we ran across a similar issue yesterday and I wanted to provide some additional information, although we don't yet know why exactly this is happening. We run Windows Server 2003 Terminal Services and noticed a few days ago that the C: drive was filling up. Investigation revealed that the folder getting all of the files was C:\WINDOWS\system32\spool\drivers\w32x86\3\Xerox\Product Data\Public\DCPs\x2UNIVSJ\V5.0. Files seemed to show up in there at random from a variety of different staff members. Today, we realized that the people whose files were winding up there were people who were logging on to the terminal server. We then realized that the files were copied while we were running a VBscript at logon that connects two Xerox printers to the local session. Our VBscript looks like this:
Set objNetwork = CreateObject("Wscript.Network")
objNetwork.AddWindowsPrinterConnection "\\ps\Xerox WorkCentre 7345 PS"
objNetwork.AddWindowsPrinterConnection "\\ps\Xerox EXi 570 Print Server"
That VBscript has been in place for months with no issues, so we're stil not sure what is going on, but preventing the script from running at user logon prevents the problem from happening.
We ran across a similar issue. The Client is running Windows 7 SP1 64bit, installed Xerox printer drivers are:
- Xerox ColorQube 9303 PS 5295.1700.0.0
- Xerox ColorQube 8900X PS 5351.500.0.0
The folder c:\windows\system32\spool\drivers\x64\3\xerox\Product Data\Public\DCPs\x2DMAMPZ\ was 15 GB in size, filling up the client´s harddrive.
It seems that during driver installation each and every non-standard folder was copied from the root of the PC´s C:\ drive to c:\windows\system32\spool\drivers\x64\3\xerox\Product Data\Public\DCPs\x2DMAMPZ\V5\ in addition to the folder "DMAM", which should have been the only folder to resize under this path.
What went wrong, why is this happening?
I deleted the extra files yesterday. Today those extra folders were recreated , according to the timestamps this happend between 09:57-10:00 AM. I did not add any Xerox printer, did not restart or relogin during this time. What is happening here???
And on another note:
I found the same problem on our Windows Server 2008R2 terminalserver. Here the folder containing the extra files is:
So another Xerox driver, same problem. Something is going seriously wrong here.
i think this is an issue with a older version of the driver
have you guys updated to the recent driver thay you can download on the xerox.com site?
This problem is still present as of version 5617.700.0.0 of Xerox Global Print Driver. All the computers in our organization that have the Xerox drivers installed have this issue, we have discovered it because many users had they workstations locked due to missing free disk space on C: driver, the C:\Windows\System32\spool\drivers\x64\3\Xerox\Product Data\Public\DCPs can grow to 20 or more GBs.
After every boot I see WmiPrvSE (a system Windows process that among other things runs the printer drivers) using a full CPU core and writing to C:\Windows\System32\spool\drivers\x64\3\Xerox\Product Data\Public\DCPs
Please fix this as soon as possible or provide a workaround.
Same thing here 10 to 15 GB on 2008 R2 server running Xenapp. We also found that after the DCPs are downloaded that we are running into issues with Excel crashing if you try and expand the margins. (WMI was a good catch too also see that too) Xerox has an article that I found explaining the DCPs and how to point it to a location on your network so you can manage what DCPs are install. This weekend I am going to try and point a couple of the Xenapp hosts out to a dummy folder and see if it stops the DCPs from doing whatever it is that they are doing.
Here is the article that I was referencing.