Article ID: 309601
Article Last Modified on 3/29/2007
APPLIES TO
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 3
This article was previously published under Q309601
SYMPTOMS
This issue does not affect any Windows 2000 hotfixes that are available from the Microsoft Download Center or on the Windows Update Web site, including Windows 2000 Security Updates. This issue affects only a small number of post-Service Pack 3 (SP3) hotfixes, which were created between April 2, 2002, and July 29, 2002, and which are available only from Microsoft Product Support Services. These hotfixes are listed in the "Resolution" and the "More Information" sections of this article.
If this issue affects your system, the Windows 2000 SP3 Installer will pause during Setup and alert you to the fixes that are in conflict. If you do not receive this alert message, you do not have to worry about this issue. If you choose to continue Setup without taking action, you can still finish the SP3 installation and then apply the updated fix afterward.
If you install a post-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.
Additionally, you may experience the following behaviors:
- During the Inspecting your current configuration portion of SP3 for Windows 2000 Setup, you may receive the following message:
This service pack contains files that are missing some of the fixes which were previously installed on this computer. To prevent possible problems, these files will not be installed by the service pack.
In order to have the fixes contained in both the service pack and in the previously installed hotfixes, you must obtain and install the updated versions of the following hotfixes before or after you install the following the service pack installation. These hotfixes are also listed in the svcpack.log file. - During the Inspecting your current configuration portion of a hotfix installation, you may receive the following message:
Setup cannot install this hotfix because one or more of its files are out of date. Please download and install the latest version of fix Q
xxxxxx.
CAUSE
This issue occurs because of the testing process that is performed before the release of a service pack.
Before SP3 for Windows 2000 was released, extensive testing was performed to make sure that all of the included fixes and updates worked correctly. During the time before SP3 was released, during testing, new customer-requested updates were not incorporated into SP3. Instead, Microsoft scheduled the new customer-requested updates into a future service pack for Windows 2000. To provide solutions to customer requests as quickly as possible, these updates were created as post-SP3 versions of hotfixes, and then released to the customers who needed them. These post-SP3 hotfixes are not included in SP3, but may be included in later service packs for Windows 2000.
Additionally, during further tests of these post-SP3 hotfixes, updates or fixes for problems that were found were incorporated into SP3 for Windows 2000. These updates and fixes will also be included in later service packs. However, it was not possible to include these updates or fixes in the post-SP3 hotfixes because they had already been distributed to the customers who requested them.
With the release of SP3 for Windows 2000, the post-SP3 hotfixes have now been re-created to include all necessary improvements and updates. These updated hotfixes are available to customers to upgrade post-SP3 hotfix versions so that customers do not lose functionality and have no conflicts when they install SP3 for Windows 2000 or when they install updates on a computer with SP3 for Windows 2000.
RESOLUTION
To resolve this issue, obtain and install the updated versions of the hotfixes that are listed in the More Information section of this article.
NOTE: You can install the updated versions of these hotfixes either before or after you install SP3 for Windows 2000.
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Active Directory Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326797 Some Windows 2000 Active Directory hotfixes may cause a conflict with SP3 for Windows 2000
326936 Some Windows 2000 Active Directory hotfixes may cause a conflict with SP3 for Windows 2000: 2 of 2
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 SMB Redirector Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326798 Some Windows 2000 SMB Redirector hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Shell Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326799 Some shell hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Kernel Hotfixes: 1 of 2 in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326935 Some Windows 2000 kernel hotfixes may cause a conflict with SP3 for Windows 2000: 1 of 2
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Kernel Hotfixes: 2 of 2 in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326800 Some Windows 2000 kernel hotfixes may cause a conflict with SP3 for Windows 2000: 2 of 2
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Spooler Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326801 Some Windows 2000 spooler hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Network Shell Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326802 Some Windows 2000 network shell hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 OLE Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326803 Some Windows 2000 OLE hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Windows 2000 Internet Information Services (IIS) Hotfixes in the More Information section of this article, click the article number below to view the article in the Microsoft Knowledge Base:
326804 Some Windows 2000 Internet Information Services hotfixes may cause a conflict with SP3 for Windows 2000
- For additional information about how to update the post-SP3 versions of the hotfixes that are listed under Other Hotfixes in the More Information section of this article, click the appropriate article number below to view the article in the Microsoft Knowledge Base:
NOTE: These updated hotfix versions are referenced by using the same Knowledge Base article number as that of the post-SP3 versions.263939 Disk performance may degrade over time
292053 Can change expired password without authorization when using IAS or RRAS in Windows 2000
307331 EnableTrace() function requires trace providers to be registered before
312571 The event log stops logging events before reaching the maximum log size
313494 Microsoft Cryptography API may not work if the default CSP has been set incorrectly
325455 Ftp.exe Does Not Handle Japanese Path Names Correctly
318332 You receive a "System Error 1230" error message when you browse the network
318871 Problems transferring highly fragmented packets in NDIS
318873 The PKI Dialog Box Appears Multiple Times If You Click Cancel
319725 SLIP connections broadcast NetBIOS names when the client is turned off
320261 Terminal Services performance problems occur because Explorer.exe maintains instrumentation data and counters in the registry
320661 You cannot take DFS replica members offline
321036 Modem settings are missing after you remove and re-insert your modem
321733 A "Delayed Write Failed" error message occurs when you write a file to a server
321793 STOP 0x000000C2 BAD_POOL_CALLER error message on a cluster node
321867 Windows NT 4.0 Usrmgr.exe does not display an error message when you change a password to a weak password
322018 L2TP may not use the default IP address
322141 Ntfrs.exe does not clean up the staging folders on members with no outbound partners in Windows 2000
STATUS
Microsoft has confirmed that this is a problem in the hotfixes that are identified in this article.
MORE INFORMATION
The following post-SP3 hotfixes are known to cause the behavior described in the Symptoms section of this article.
Windows 2000 Active Directory Hotfixes
316803 Earlier clients may fail to change passwords or join in a Windows 2000 domain
318533 Windows 2000 post-Service Pack 3 Active Directory rollup hotfix
320828 Data that is protected by user's private key can be accessed by a domain administrator who resets the user's password
323661 The "No 'Entire Network' in My Network Place" policy is not used in the Add Network Place Wizard
323538 IAS authentication is unsuccessful after you install the 292053 hotfix
323758 SFM Macintosh logon audit event is not logged when you use Microsoft UAM
324406 Printing to a redirected LPT1 from Windows XP to Windows 2000 prints multiple separator pages
324574 Certificate does not display the ampersand (&) in a company name
324612 Plug and Play devices are not detected after you restart your Windows 2000-based computer
back to the "Resolution" section back to the "Resolution" section
Windows 2000 Shell Hotfixes
288180 The ExitWindowsEx() function may not log off the user or shut down the computer if the computer is locked
322346 You cannot access protected data after you change your password
325804 User Context may not have sufficient access rights when you use the LogonUser property
back to the "Resolution" section
Windows 2000 Kernel Hotfixes: 1 of 2
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
back to the "Resolution" section
Windows 2000 Kernel Hotfixes: 2 of 2
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 "Invalid Password" error when joining a domain with Sysprep image
322842 A lock occurs between two threads of system GDI in Windows 2000
back to the "Resolution" section
Windows 2000 Spooler Hotfixes
324184 Access violation in Lsass.exe because of LDAP Version 2 search with referrals
back to the "Resolution" section
Windows 2000 Network Shell Hotfixes
321166 "Your Password Is Expired" error message when you access resources from Macintosh on Windows 2000 Server running AppleTalk Network Integration
back to the "Resolution" section
Windows 2000 OLE Hotfixes
321854 Only members of the Administrators group can retrieve the ntSecurityDescriptor attribute from an IDirectorySearch result set
back to the "Resolution" section
Windows 2000 Internet Information Services (IIS) Hotfixes
322042 Input language of Terminal Server client does not match that of Terminal Server session
back to the "Resolution" section
Other Hotfixes
324120 Cannot log on to domain after adding a computer to a domain
325641 Cannot connect in the Active Directory Users and Computers Tool
326109 EMF print jobs that contain Type 1 fonts may not print
324377 Cannot use domain Local Groups for Active Directory certificate mapping
318815 Cannot connect to Web sites that require SSL 3.0
264959 Redirector does not inform Cache Manager of memory extends
318789 Redirector does not cache files when the SPARSE attribute is set
319967 You cannot open a file that you moved to a DFS share
322019 Data loss occurs when you copy files over the network
265396 Slow network performance occurs when you select a file on a share that uses NTFS
321126 The "Look In" and "Save As" boxes in common dialog boxes are slow
322820 "Hide Specified Control Panel Applets" policy does not work in Windows 2000
323045 Access violation error message in Explorer.exe
321787 Access violation when you run Windows Installer in a Terminal Services session
321788 STDIN/STDOUT redirection may not work if started from a file association
302510 Stop 0x0000001e error message in Win32k.sys when users log off from a server running Terminal Services
Keywords: kbbug kbfix kbenv KB309601
