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.

A memory leak occurs in the Lsass.exe process on a domain controller that is running Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install the Identity Management for UNIX role on a domain controller that is running Windows Server 2012.
  • You click Server for NIS, and then you select the Network Information Service (NIS) domain on which the domain controller is located.
  • In the Properties dialog box for the selected domain, you change the Password Synchronization field from Crypt encryption to MD5 encryption.
  • A domain user tries to change the password.

In this scenario, a memory leak occurs in the Lsass.exe process.

↑ Back to the top


Resolution

This hotfix is also available at Microsoft Update Catalog.

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: 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 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The 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 Server 2012 file information notes
Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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, 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.2.920 0.20xxxWindows Server 2012RTMLDR
  • 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 2012" 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 x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Pswdsync.dll6.2.9200.20765107,00804-Jul-201314:13x64
Psync-ppdlic.xrm-msNot Applicable2,87504-Jul-201315:42Not Applicable
Psync.mofNot Applicable2,36102-Jun-201214:54Not Applicable
Psync_namespace.mofNot Applicable12202-Jun-201214:54Not Applicable
Psync_provreg.mofNot Applicable49902-Jun-201214:54Not 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


Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_216db4ed84a6240d982b0ce4673c9174_31bf3856ad364e35_6.2.9200.20765_none_cb2aaa316f7844fe.manifest
File versionNot Applicable
File size716
Date (UTC)06-Jul-2013
Time (UTC)00:24
PlatformNot Applicable
File nameAmd64_microsoft-windows-p..ord-synchronization_31bf3856ad364e35_6.2.9200.20765_none_bede703bdf6b84e3.manifest
File versionNot Applicable
File size90,969
Date (UTC)06-Jul-2013
Time (UTC)00:24
PlatformNot Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2841306
Revision : 1
Created on : 1/7/2017
Published on : 8/15/2013
Exists online : False
Views : 195