Article ID: 326797 - View products that this article applies to.
This article was previously published under Q326797
This article has been archived. It is offered "as is" and will no longer be updated.
If you install a post-Service Pack 3 (SP3) version of any of the Windows 2000 hotfixes that are listed in the "More Information" section of this article on a computer on which SP3 for Windows 2000 is installed, or if you install SP3 for Windows 2000 on a computer on which these post-SP3 hotfixes are installed, you may experience either of the following symptoms:
This issue occurs because post-SP3 versions of the hotfixes may not include the latest updates and fixes that are compatible with the installation of Service Pack 3 (SP3) for Windows 2000.
The post-SP3 versions of the Windows 2000 hotfixes that are listed in the "More Information" section of this article have been repackaged to verify the inclusion of previous fixes.
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 this specific problem.
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, submit a request to 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=supportNote 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This update contains different files for uniprocessor and multiprocessor computers. You must consider that if you need to integrate this update in an image file that you create by using the Sysprep 1.1 utility. If the update is applied before you create the Sysprep image, it is best to test the image to make sure that you do not experience issues such as Windows Explorer performance degradation. If the computers to which you want to deploy the Sysprep image use different hardware platforms than that of the source computer, some of the specific updated files may not correspond to the correct hardware abstraction layer (HAL) for the destination computer.
Microsoft recommends that you apply this update after the installation of the Sysprep image on the destination computers. For additional information about how to do this by using a Cmdlines.txt file, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/249149/EN-US/ )Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
The following post-SP3 hotfixes cause the behavior described in the "Symptoms" section of this article:
(http://support.microsoft.com/kb/288180/EN-US/ )The ExitWindowsEx() Function May Not Log Off the User or Shut Down the Computer If the Computer is Locked
(http://support.microsoft.com/kb/312827/EN-US/ )An Incorrect Authentication Package Name May Appear in Audit Event 529
(http://support.microsoft.com/kb/319672/EN-US/ )Directory Service Access Audits for a SAM Object Server Have Incomplete Object Names
(http://support.microsoft.com/kb/319709/EN-US/ )An Access Violation Occurs in Lsass Because of a Stack Overflow
(http://support.microsoft.com/kb/320099/EN-US/ )A Security Policy Does Not Process Restricted Groups Correctly
(http://support.microsoft.com/kb/320670/EN-US/ )Event ID 528 May Not Be Logged If LsaLogonUser() Is Called
(http://support.microsoft.com/kb/320711/EN-US/ )Accessing Active Directory with LDAP by Using Sun JNDI Calls May Not Work
(http://support.microsoft.com/kb/320903/EN-US/ )Clients Cannot Log On by Using Kerberos over TCP
(http://support.microsoft.com/kb/321217/EN-US/ )You Receive an 'Action Could Not Be Completed' Error Message When You Select Many Recipients in the Global Address List
(http://support.microsoft.com/kb/321933/EN-US/ )Services Are Not Listed in the Security Configuration and Analysis Snap-in
(http://support.microsoft.com/kb/322175/EN-US/ )You Must Restart the Computer After Joining a Domain with Service Pack 2
(http://support.microsoft.com/kb/322842/EN-US/ )A Lock Occurs Between Two Threads of System GDI in Windows 2000
(http://support.microsoft.com/kb/324141/EN-US/ )Changing the Password on a Locked-Out Account Generates a "Domain Not Available" Message
(http://support.microsoft.com/kb/324184/EN-US/ )Access Violation in Lsass.exe Because of LDAP Version 2 Search with Referrals
For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/309601/EN-US/ )Some Windows 2000 Hotfixes May Cause a Conflict with Service Pack 3 (SP3) for Windows 2000
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173For additional information about how to install multiple hotfixes with only one restart, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/EN-US/ )The Datacenter Program and Windows 2000 Datacenter Server Product
(http://support.microsoft.com/kb/296861/EN-US/ )Use QChain.exe to Install Multiple Hotfixes with One Reboot
Article ID: 326797 - Last Review: February 27, 2014 - Revision: 5.6