High CPU utilization when you use the Print Management snap-in to add a printer in Windows 7 or Windows Server 2008 R2

Symptoms

Consider the following scenario:
  • You have the Print Server role installed on a computer that is running Windows 7 or Windows Server 2008 R2. 
  • You disable User Account Control (UAC) on the computer.
    Note The "User Account Control: Run all administrators in Admin Approval Mode" Group Policy setting is disabled.
  • You use the Print Management snap-in to grant the Print, Manage Printers, Manage Documents, and View Server permissions to a user account in the Print Server Properties dialog box.
  • The user tries to add a printer in the Print Management snap-in.
In this scenario, the Printui.exe process may be created and then exited indefinitely. This behavior may cause CPU usage to reach 100 percent. Additionally, the user who tries to add the printer must log off the computer to stop the creation-termination loop.

Cause

This issue occurs because the Printui.exe process cannot be elevated. When a user tries to add a printer in the Print Management snap-in, the Printui.dll file checks if the user has UAC elevated rights. If the user does not have the UAC elevated rights, the Printui.exe process tries to re-launch with the elevated rights. However, when the "User Account Control: Run all administrators in Admin Approval Mode" Group Policy setting is disabled, the Printui.exe process cannot be elevated.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information
Egenskaper

Artikel-id: 2783429 – senaste granskning 10 jan. 2013 – revision: 1

Feedback