Select the product you need help with
The Windows Remote Management service stops responding in Windows 7 or in Windows Server 2008 R2Article ID: 981845 - View products that this article applies to. On This PageSYMPTOMSOn a computer that is running Windows 7 or Windows Server 2008 R2, the Windows Remote Management service stops responding. In this scenario, you cannot communicate with the computer by using the Web Services-Management (WS-Management) protocol.
Additionally, the memory usage of the service keeps increasing.
CAUSEThis issue occurs because the Windows Remote Management service encounters a deadlock condition. RESOLUTIONHotfix informationA 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, your computer must be running Windows 7 or Windows Server 2008 R2. Additionally, you must have Windows Remote Management installed on the computer.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English (United States) 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 notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
For all supported x86-based versions of Windows 7Collapse this table
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2Collapse this table
For all supported IA-64-based versions of Windows Server 2008 R2Collapse this table
WORKAROUNDWorkaround for Windows 7 and for Windows Server 2008 R2To work around the issue, restart the Windows Remote Management service.Note You may be unable to stop the service when the memory usage of the service is very large. In this situation, you have to restart the computer to recover the issue. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONThe Windows Remote Management service runs in an Svchost.exe process. You can use the Process ID (PID) of this Svchost.exe process to monitor the memory usage of the Windows Remote Management service. You can do this by using Task Manager or Resource Manager. To determine the related PID, open a command prompt, type the following command, and then press ENTER:
tasklist -svc
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 For more information, visit the following Microsoft Web sites:
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Windows Remote Management Architecture
(http://msdn.microsoft.com/en-us/library/aa384464(VS.85).aspx)
WinRM Service
(http://technet.microsoft.com/en-us/library/dd315594(WS.10).aspx)
Installation and Configuration for Windows Remote Management
(http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx)
Additional file informationAdditional file information for Windows 7 and for Windows Server 2008 R2Additional files for all supported x86-based versions of Windows 7Collapse this table
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2Collapse this table
Additional files for all supported IA-64-based versions of Windows Server 2008 R2Collapse this table
PropertiesArticle ID: 981845 - Last Review: April 29, 2010 - Revision: 1.0 APPLIES TO
|
Back to the top
