Article ID: 326797
Article Last Modified on 3/29/2007
APPLIES TO
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
This article was previously published under Q326797
SYMPTOMS
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:
- You lose some of the functionality of SP3 for Windows 2000.
-or-
- You lose the functionality of the post-SP3 hotfix.
This issue does not affect any Windows 2000 hotfixes available at the Microsoft Download Center or through Windows Update, including Windows 2000 security hotfixes. This issue affects only a small number of fixes that were made available only to users who called Microsoft Product Support Services between July 23, 2002 and August 8, 2002. These hotfixes are listed in the "Resolution" and "More Information" sections of this article.
CAUSE
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.
RESOLUTION
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 fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
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:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
The following post-SP3 hotfixes cause the behavior described in the "Symptoms" section of this article:
288180 The ExitWindowsEx() Function May Not Log Off the User or Shut Down the Computer If the Computer is Locked
312827 An Incorrect Authentication Package Name May Appear in Audit Event 529
319672 Directory Service Access Audits for a SAM Object Server Have Incomplete Object Names
319709 An Access Violation Occurs in Lsass Because of a Stack Overflow
320099 A Security Policy Does Not Process Restricted Groups Correctly
320670 Event ID 528 May Not Be Logged If LsaLogonUser() Is Called
320711 Accessing Active Directory with LDAP by Using Sun JNDI Calls May Not Work
320903 Clients Cannot Log On by Using Kerberos over TCP
321217 You Receive an 'Action Could Not Be Completed' Error Message When You Select Many Recipients in the Global Address List
321933 Services Are Not Listed in the Security Configuration and Analysis Snap-in
322175 You Must Restart the Computer After Joining a Domain with Service Pack 2
322842 A Lock Occurs Between Two Threads of System GDI in Windows 2000
324141 Changing the Password on a Locked-Out Account Generates a "Domain Not Available" Message
324184 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:
309601 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:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For 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:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
Keywords: kbbug kbfix kbwin2000presp4fix kbqfe kbhotfixserver KB326797
