"Bad Image" error when trying to print from Outlook & FoxPro 9

[RichDay]

"Bad Image" error when trying to print from Outlook & FoxPro 9

Environment:
Lenovo 3695H5U workstation on Windows Domain Server
Windows 7 Prof. 64 Sp1
8GB RAM
Intel Xeon CPU E3-1225 V2 3.2ghz
Up-to-date on Windows updates
User has admin rights
Symantec Endpoint.Cloud and Malwarebytes say it's clean


Problem:
This PC has been in place for 4 months with no problems. On 3/4/2013 the user tried to print an email from Outlook 2010 and got a "Close Preview:Outlook.exe - Bad Image" error. The body of the error says...

"C:\windows\system32\prnfldr.dll is either not designed to run on Windows or...).


They get a similar error when trying to print from Visual Foxpro 9 w/sp3.

In both cases, it's always saying that prnfldr.dll is the problem.


There is an identical PC in the same area. I copied this file from the working PC to this one, but the problem persists.


The strange thing this is that Outlook will sometimes print without incident. Visual Foxpro always gets this error.

Has anyone ever seen this before?


Thanks!

 

[Kaktussoft]

Try from elevated command prompt:

sfc/scannow

Any errors?

 

[Kaktussoft]

Environment:
Lenovo 3695H5U workstation on Windows Domain Server
Windows 7 Prof. 64 Sp1
8GB RAM
Intel Xeon CPU E3-1225 V2 3.2ghz
Up-to-date on Windows updates
User has admin rights
Symantec Endpoint.Cloud and Malwarebytes say it's clean


Problem:
This PC has been in place for 4 months with no problems. On 3/4/2013 the user tried to print an email from Outlook 2010 and got a "Close Preview:Outlook.exe - Bad Image" error. The body of the error says...

"C:\windows\system32\prnfldr.dll is either not designed to run on Windows or...).


They get a similar error when trying to print from Visual Foxpro 9 w/sp3.

In both cases, it's always saying that prnfldr.dll is the problem.


There is an identical PC in the same area. I copied this file from the working PC to this one, but the problem persists.


The strange thing this is that Outlook will sometimes print without incident. Visual Foxpro always gets this error.

Has anyone ever seen this before?


Thanks!

c:\windows\syswow64 folder has prnfldr.dll as well. did you replace that file as well from a good working machine?

 

[RichDay]

I just contacted our IT people and failed to bring me up to date on the latest attempts to fix this.

They say they did run it and it found errors that could not be fixed. It did not specify what those errors were. They then ran a Windows Repair utility. After that was run, the problem was not fixed and the sfc scan, again, reported errors that could not be fixed.

Sorry, I thought I had the most recent information when I posted this.

 

[Kaktussoft]

I just contacted our IT people and failed to bring me up to date on the latest attempts to fix this.

They say they did run it and it found errors that could not be fixed. It did not specify what those errors were. They then ran a Windows Repair utility. After that was run, the problem was not fixed and the sfc scan, again, reported errors that could not be fixed.

Sorry, I thought I had the most recent information when I posted this.

Win7 startup repair can't detect and fix it! Windows is working fine and boots fine.

What errors did sfc detect and wasn't able to fix? See http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html . Post sfcdetails.txt

prnfldr.dll has never been changed by service pack or windows update. Just grab them from a working win7 machine. The file is in c:\windows\system32 and c:\windows\syswow64

 

[RichDay]

I really appreciate the help with this.

 

[Kaktussoft]

I really appreciate the help with this.

You posted cbs.log, not what I requested! but I analyze it now

 

[Kaktussoft]

I really appreciate the help with this.

these are the problems

 

[Kaktussoft]

Run this tool System Update Readiness Tool fixes Windows Update errors in Windows 8, Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008
Afterwards post 2 files. The System Update Readiness Tool creates a log file that captures any issues that the tool found or fixed. The log file is located here:

• %SYSTEMROOT%\Logs\CBS\CheckSUR.log
• %SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log

Run tool twice to see if it fixed it