Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Handle leak in Svchost.exe when a WMI query is triggered by using the Win32_PowerSettingCapabilities class in Windows 7 or in Windows Server 2008 R2

Handle leak in Svchost.exe when a WMI query is triggered by using the Win32_PowerSettingCapabilities class in Windows 7 or in Windows Server 2008 R2

View products that this article applies to.

Symptoms

Assume that a Windows Management Instrumentation (WMI) query is executed to determine the power settings of a computer that is running Windows 7 or Windows Server 2008 R2. The query is triggered by using the Win32_PowerSettingCapabilities class. In this situation, the handle count of the Svchost.exe process that hosts the power service increases. Additionally, when the handle count reaches the maximum number of handles that a process can have, no services that share this process open handles to any object.

↑ Back to the top

Cause

This issue occurs because the handles to the power policy registry keys that are opened by the power service (Umpo.dll) are not closed correctly. This behavior causes the handle leak.

↑ Back to the top

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 Web site:
http://support.microsoft.com/contactus/?ws=support
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 Windows 7 Service Pack 1 (SP1) or 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 use the hotfix in this package, 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
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.18xxx    		Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.22xxx    		Windows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Umpo.dll6.1.7601.18331119,29603-Dec-201308:15x86
Umpo.dll6.1.7601.22529119,29603-Dec-201308:10x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Umpo.dll6.1.7601.18331163,32803-Dec-201308:44x64
Umpo.dll6.1.7601.22529164,86403-Dec-201308:44x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Umpo.dll6.1.7601.18331289,79203-Dec-201307:43IA-64
Umpo.dll6.1.7601.22529290,30403-Dec-201307:54IA-64

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about the Win32_PowerSettingCapabilities class, visit the following Microsoft website:
General information about the Win32_PowerSettingCapabilities class
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

The following is a sample PowerShell script that queries the power settings and reproduces this issue:
$PowerPlan=Get-WmiObject -namespace "root\cimv2\power" -class Win32_PowerPlan | where {$_.IsActive}
do{
     $PowerSettings = $PowerPlan.GetRelated("win32_PowerSettingDataIndex") | foreach {
     $powersettingindex = $_;
     $PowerSettingIndex.GetRelated("Win32_PowerSetting") | select @{Label="Power Setting";Expression={$_.instanceid}},
                                                                  @{Label="AC/DC";Expression={$powersettingindex.instanceid.split("\")[2]}},
                                                                  @{Label="Summary";Expression={$_.ElementName}},
                                                                  @{Label="Description";Expression={$_.description}},
                                                                  @{Label="Value";Expression={$powersettingindex.settingindexvalue}}     }
 $PowerSettings | ft "AC/DC",Summary,Value -autosize
} while(1)

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_008fb7c6b6df6436d32d3a2377f20f97_31bf3856ad364e35_6.1.7601.18331_none_6f1df10dae299b39.manifest
File versionNot applicable
File size708
Date (UTC)03-Dec-2013
Time (UTC)19:55
PlatformNot applicable
File nameX86_9cccb1a494a7bc69c2807770af31a6bf_31bf3856ad364e35_6.1.7601.22529_none_bcc0d78d92c52a89.manifest
File versionNot applicable
File size708
Date (UTC)03-Dec-2013
Time (UTC)19:55
PlatformNot applicable
File nameX86_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.18331_none_5ff935abaac87727.manifest
File versionNot applicable
File size15,950
Date (UTC)03-Dec-2013
Time (UTC)09:00
PlatformNot applicable
File nameX86_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.22529_none_6095a698c3d6c2df.manifest
File versionNot applicable
File size15,950
Date (UTC)03-Dec-2013
Time (UTC)08:45
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File propertyValue
File nameAmd64_7ac3ed40b29a2b670cd4d9aa663960df_31bf3856ad364e35_6.1.7601.22529_none_2f04bbb872c318c6.manifest
File versionNot applicable
File size1,066
Date (UTC)03-Dec-2013
Time (UTC)19:56
PlatformNot applicable
File nameAmd64_7f239f99698ec98dd70fcd5d2ffa8c3b_31bf3856ad364e35_6.1.7601.18331_none_6824b4a99ed941e5.manifest
File versionNot applicable
File size1,066
Date (UTC)03-Dec-2013
Time (UTC)19:56
PlatformNot applicable
File nameAmd64_90f5424f5bfe0ac12381dd1de0ab7504_31bf3856ad364e35_6.1.7601.22529_none_6986c57305348db8.manifest
File versionNot applicable
File size712
Date (UTC)03-Dec-2013
Time (UTC)19:56
PlatformNot applicable
File nameAmd64_a015a8b007f662681f05d770cb3e3b53_31bf3856ad364e35_6.1.7601.18331_none_cb193c2a1ef42a2b.manifest
File versionNot applicable
File size712
Date (UTC)03-Dec-2013
Time (UTC)19:56
PlatformNot applicable
File nameAmd64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.18331_none_bc17d12f6325e85d.manifest
File versionNot applicable
File size15,954
Date (UTC)03-Dec-2013
Time (UTC)09:14
PlatformNot applicable
File nameAmd64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.22529_none_bcb4421c7c343415.manifest
File versionNot applicable
File size15,954
Date (UTC)03-Dec-2013
Time (UTC)09:37
PlatformNot applicable
File nameWow64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.18331_none_c66c7b819786aa58.manifest
File versionNot applicable
File size12,100
Date (UTC)03-Dec-2013
Time (UTC)08:28
PlatformNot applicable
File nameWow64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.22529_none_c708ec6eb094f610.manifest
File versionNot applicable
File size12,100
Date (UTC)03-Dec-2013
Time (UTC)08:23
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_d9a1294cf6e77e6198e7acc0a625c034_31bf3856ad364e35_6.1.7601.18331_none_eef9421800b63a0e.manifest
File versionNot applicable
File size1,064
Date (UTC)03-Dec-2013
Time (UTC)19:55
PlatformNot applicable
File nameIa64_ff48867798c09c878158347a6095e4ae_31bf3856ad364e35_6.1.7601.22529_none_019f1c1cb4ac9f5d.manifest
File versionNot applicable
File size1,064
Date (UTC)03-Dec-2013
Time (UTC)19:55
PlatformNot applicable
File nameIa64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.18331_none_5ffad9a1aac68023.manifest
File versionNot applicable
File size15,952
Date (UTC)03-Dec-2013
Time (UTC)08:28
PlatformNot applicable
File nameIa64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.22529_none_60974a8ec3d4cbdb.manifest
File versionNot applicable
File size15,952
Date (UTC)03-Dec-2013
Time (UTC)08:28
PlatformNot applicable
File nameWow64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.18331_none_c66c7b819786aa58.manifest
File versionNot applicable
File size12,100
Date (UTC)03-Dec-2013
Time (UTC)08:28
PlatformNot applicable
File nameWow64_microsoft-windows-usermodepowerservice_31bf3856ad364e35_6.1.7601.22529_none_c708ec6eb094f610.manifest
File versionNot applicable
File size12,100
Date (UTC)03-Dec-2013
Time (UTC)08:23
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2639077
Revision : 1
Created on : 1/7/2017
Published on : 1/15/2014
Exists online : False
Views : 287