Microsoft Publisher creates splwow64.exe error

Hiya,

I have a client who is using Microsoft publisher version 2002.  They have a HP laptop with Windows Vista Home Premium.   When they use Publisher, it displays a dialog box that says splwow64.exe bad image.  In the box the following text appears:

C:\WIndows\system32\spool\Drivers\unidrvui.dll is either not designed to run on Windows or it contains an error.  Try installing the program again using the original media or contact your system administrator...

Can you tell me how to take care of this perplexing issue?  They have Microsoft Office 2010 Student and home edition installed also.  

Thanks for helping me,
JRA
calavera44Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
calavera44Connect With a Mentor Author Commented:
Hi all,

I did some further work with Publisher and Word.  I launched both of the programs and saved a document.  Then returned the computer to the end user who has used it now for a week or so.  No errors reported.  So, I conclude from her confirmation that all is well.  I think that the issue was a problem with the unidrvui.dll file.  The fix was to rename those files and run the system file checker.

JRA
0
 
jcimarronCommented:
0
 
calavera44Author Commented:
Hi jcimarron,

I updated the driver from download at HP web site for the printer.  Still the same issue.  Any other ideas?

JRA
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
jcimarronCommented:
calavera44--Did you reboot after installing new driver?
0
 
calavera44Author Commented:
jcimarron,

You know, I did reboot.  Alas, still the same issue.

JRA
0
 
jcimarronConnect With a Mentor Commented:
calavera44--splwow64.exe is part of the Microsoft OS.  Run SFC /SCANNOW from a command prompt.
http://support.microsoft.com/kb/929833
0
 
calavera44Author Commented:
Hi jcimarron,

I will do that later on today.  I let you know.

JRA
0
 
calavera44Author Commented:
Hi jcimarron

Alas, running the sfc /scannow did not have any result.  Same issue.  I did run as adminstrator.

Any other thoughts?
0
 
jcimarronCommented:
calavera44--Nothing too intelligent.  Have you gone to the website of the printer manufacturer to see if a new driver is available?  
Uninstall and reinstall the printer.
You could also rename the existing splwow64.exe to, say, splwow64.bad, and then run SFC /SCANNOW again.  After that see if a new splwow64.exe has been installed.  If not, rename splwow64.bad to splwow64.exe
Is this happening only when using Publisher?
0
 
calavera44Author Commented:
HI,

I did what you suggested.  splwow64 has been replaced.  It happens in Word as well.

JRA
0
 
jcimarronCommented:
calavera44--I do not understand your last post.  Are you getting no more errors in Publisher, but do get an error in Word?
Did you run SFC again?
Do you have a new unidrvui.dll ?
0
 
calavera44Author Commented:
jcimarron

Hi, what I am saying is that splwow64 was renamed by me and then replaced by the sfc /scannow.  Still was a problem with the error.  I then renamed unidrvui.dll
It turns out there were 2 files of that name!  I know, how can that be but I looked at their properties and same name.   So I renamed those files and then did a sfc /scannow

I looked at it today and launched Publisher, no error.  I launched Word, no error.  I tried to print and the dialog box came up okay, no error.  I am going to check it again more comprehensively tomorrow.  Maybe it will be good to go.  I am so sick of this computer!  I just want it to be fixed and off the bench.

Anyway, I'll keep you posted.

JRA
0
 
calavera44Author Commented:
Hi,
Thanks jcimarron, you put me on the right path to fix this issue.  Your recommendation to try running sfc /scannow was the key to solving this issue.  I think that renaming the unidrvui.dll  file enabled the sfc to copy that in to the Windows folder as a new file.

So it's gone, back to the client and no issues.

JRA
0
 
jcimarronCommented:
calavera44--That is good news.  Thanks for telling us what you did to fix the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.