FIX: A legacy HP printer driver may crash when you run a 32-bit application on a computer that is running a 64-bit version of Windows 7 or of Windows Server 2008 R2
Content provided by Microsoft
Applies to: Windows 7 EnterpriseWindows 7 Enterprise NWindows 7 Home BasicWindows 7 Home PremiumWindows 7 Home Premium NWindows 7 ProfessionalWindows 7 Professional NWindows 7 StarterWindows 7 Starter NWindows 7 UltimateWindows 7 Ultimate NWindows Server 2008 R2 DatacenterWindows Server 2008 R2 Datacenter without Hyper-VWindows Server 2008 R2 EnterpriseWindows Server 2008 R2 Enterprise without Hyper-VWindows Server 2008 R2 StandardWindows Server 2008 R2 Standard without Hyper-VWindows Server 2008 for Itanium-Based SystemsMore
Consider the following scenario. You run a 32-bit application on a computer that is running a 64-bit version of Windows 7 or of Windows Server 2008 R2. You have a legacy Hewlett Packard (HP) printer driver installed. In this scenario, the printer driver may crash. Additionally, entries may be logged in a Windows Error Reporting (WER) report that points to the HP printer driver as the cause of the crash.
This problem occurs when the EnablePDEV method and the DisablePDEV method occur on different threads in the Splwow64.exe process.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
There are no prerequisites for installing this hotfix.
You may have to restart the computer after you apply this hotfix.
The English (United States) version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
For all supported Itanium-based versions of Windows Server 2008 R2
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
ERROR: at System.Diagnostics.Process.Kill()
at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank