[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9412
  • Last Modified:

PrintIsolationHost.exe Windows 2008R2 Server

Hello,

I am running Windows 2008R2 as a print server and noticed that the following error keeps appearing:

Faulting application name: PrintIsolationHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3b1
Faulting module name: hpzuiwn7.dll, version: 0.3.7071.0, time stamp: 0x4a5bdfcb
Exception code: 0xc0000005
Fault offset: 0x00000000000d6971
Faulting process id: 0x534
Faulting application start time: 0x01ccf19af2bb7704
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\hpzuiwn7.dll
Report Id: 306a6540-5d8e-11e1-bd1d-005056b60001

I do not see hpzuiwn7 as the print processor listed for any of our printers, does anyone know how to get rid of this error?  We have to restart the spool services more often than normal (once or twice a week) and in reviewing the event viewer I came across this.

Thanks for your assistance.
0
efx-wpg
Asked:
efx-wpg
  • 3
  • 2
1 Solution
 
hdhondtCommented:
0
 
hdhondtCommented:
Further to my last comment:

In earlier versions of Windows, printer drivers were run by the spooler service. A faulty driver would crash the spooler, but not the entire system (as happened before Win2k). In W2008 each driver is run by its own instance of PrintISolationHost, so the spooler no longer crashes if the driver is faulty. Instead that instance of PrintIsolationHost crashes. The benefit is that other printers are not affected, as the spooler is still running.

The fix should be the same as for spooler crashes: replace the driver. This is normally done by a complete reinstall (i.e. removing the driver files after deleting the printer). That may work in this case as well, but if the driver has a built-in fault, then the best way is to replace it with a different one, as suggested in the link I posted.
0
 
ahahumCommented:
I have this issue too and it just appeared within the past week.  I haven't made any changes to the drivers.

I have several printers using this driver and I'm not sure how to determine which printer is causing the issue.  Any ideas?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
hdhondtCommented:
It's the driver that's at fault, not the printer
0
 
efx-wpgAuthor Commented:
How do  you see what printer is using the faulty driver?  I thought I would be able to see this based on the tech net article but I must be missing something.  Can someone explain how to find out what printer is causing the issue?  All the print processor's I see appear not to be using the "wrong" driver, so I am lost.
0
 
ahahumCommented:
I'm in the same boat, EFX-WPG - no one is complaining their documents are failing to print so I don't have a way to determine which printer is causing the issue with multiple printers using the driver.

I'm using the drivers built into windows so that they can be deployed easily with GPP.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now