Splwow64.exe error X2utilH8.dll missing

[FDBT]

This is an old thread, but I know it likely is still hapening to a lot of folks.

We've had this common problem off and on for years now with our Xerox copiers and the Xerox print drivers that are installed via our Windows print server onto the client PCs (our users have no permissions to install printers themselves, so we have to use RunAs to obtain admin permissions to fix the problem).  The problem directly stems from the Dependent Files registry entry for the print driver being blank or corrupted on the Windows client PC (Windows 7 64-bit), but I don't know why this registry glitch happens.

When it does happen (and I'll usually get 3 or 4 users a day having this problem), I have a 60 second fix that I do on the client PCs to make them ready to go again (until the next time it happens):

1) Remove the Xerox copiers from the user's list of printers on their PC.

2) RunAs REGEDIT.EXE as an admin user.

3) Delete any Xerox print driver keys that you find under HKLM\System\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3

4) RunAs Services.msc as an admin user.

5) Stop and Start the Print Spool service (or reboot the PC and have the user log in again).

6) Now re-add the Xerox copiers for the user (or you can set up a GPO to automatically add the Xerox copiers when the user logs in).

Printing to the Xerox copier should work now. 

I have been able to apply this workaround remotely too, but the user then has to reboot the computer and login again and then manually re-add the Xerox copier(s), unless you use a GPO to automatically add the copier(s) at login.

[Kimzi]

Hi, Mariano_vina!

You will have to do this on the client having the issue, does this happen on several clients?

Check if the file does exist on the Clients.

If so I suggest you write a tiny startup script and run it through the AD when users login or restart their machine.

Best Regards

Kimzi

--------------------------------------------
Please remember to select "Accept as Solution" for posts that helped you solve the issue.

[mariano_vina]

Dear Kimzi,

I actually have the same issue, with GPD PCL6, and my customer have about 500 workstations. The process that you mentioned in the last thread, must be on the client workstation or in the print server side?

If this works, will be much appreciated!

Regards!

Mariano.

[Kimzi]

Hey!

If the file actually exist I would suggest you try this:

1. Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Enviroments\Windws x64\x86\Drivers

2. Here you'll see a key/map named Version-3 - delete all the sub-keys inside this.

3. Open CMD and write "net stop spooler"

4. Go to C:\Windows\System32\spool\printers\ and C:\Windows\System32\spool\drivers\x64\3.. delete the files stored here.

5. In CMD write "net start spooler"

This has helped others with the same error, but only if you actually do have the dll file.

Best Regards

Kimzi

--------------------------------------------
Please remember to select "Accept as Solution" for posts that helped you solve the issue.

[Fabio]

maybe your antivirus is deleting those files?

[afraizer]

I am also seeing this error and have not found a solution.

[rcmillion]

We are also seeing this error and I have searched your online knowledge bases with no hits.

[CherylO-Xerox]

Hello DJink 

If you have not already resolved this issue, we suggest you search our online knowledgebase for this product(s).  

Alternatively, you can visit our Contact Us page for other support options.

[DJink]

we are getting this error over and over - have tried the clientside rendering fix but errors comes back after a few days  - is there a fix for this. a universal driver - i see one released feb 15 - we are currently using PCL6 drivers - 5196.1100 (for 7000 series) and 5196.1200 (for 5000 series) - should we switch back to PS and the newer universal driver?  This is becoming urgent as we have a large fleet of printers and 1000's of pcs - any help would be appreciated.