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. Windows PowerShell scripts stop working in Windows Server 2008 R2 SP1

Windows PowerShell scripts stop working in Windows Server 2008 R2 SP1

View products that this article applies to.

Symptoms

You have a server that is running Windows Server 2008 R2 Service Pack 1 (SP1). When you use Windows PowerShell scripts to monitor Active Directory replication status across domain controllers through a Windows Management Instrumentation (WMI) query that uses a specific class on a high frequency, the scripts stop working after a short period.

Additionally, when this issue occurs, other WMI queries may fail. Therefore, other monitoring scripts may break.

↑ Back to the top

Cause

This issue occurs because the WMI query uses a specific class that does not release resources correctly, and this causes a memory 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, go to the following Microsoft website:
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 Server 2008 R2 SP1.

For more information about how to obtain a 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 may be prompted to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
Windows Server 2008 R2 file information notes
Important 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.
  • The files that apply to a specific product, SR_Level (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.22xxxWindows 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" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Replprov.dll6.1.7601.2261967,07207-Mar-201402:38x64
Replprov.mofNot applicable18,23620-Nov-201004:05Not applicable

↑ 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 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

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_32ae18b49b6574220f61ac550a46e9f9_31bf3856ad364e35_6.1.7601.22619_none_dcf5e85a9499e8ba.manifest
File versionNot applicable
File size730
Date (UTC)07-Mar-2014
Time (UTC)08:33
PlatformNot applicable
File nameAmd64_microsoft-windows-a..replicationprovider_31bf3856ad364e35_6.1.7601.22619_none_7f03d41419251aab.manifest
File versionNot applicable
File size11,116
Date (UTC)07-Mar-2014
Time (UTC)05:41
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,706
Date (UTC)07-Mar-2014
Time (UTC)08:33
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2928490
Revision : 1
Created on : 1/7/2017
Published on : 4/10/2014
Exists online : False
Views : 155