Update Rollup 1 for Windows
2000 SP4 and Known Issues
| Article ID |
: |
891861 |
| Last Review |
: |
August 8, 2005 |
| Revision |
: |
13.0 |
Important
This article contains information about how to modify the registry. Make sure to
back up the registry before you modify it. Make sure that you know how to
restore the registry if a problem occurs. For more information about how to back
up, restore, and modify the registry, click the following article number to view
the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/) Description of the Microsoft
Windows registry
On This Page
SUMMARY
This article describes
Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 (SP4). Update Rollup 1
for Windows 2000 SP4 was released on June 28, 2005. This update rollup contains
security-related updates that were produced for Windows 2000 between the release
of Windows 2000 SP4 and April 30, 2005. On April 30, 2005, the contents of
Update Rollup 1 were locked for final testing by Microsoft and customer beta
testing. This update rollup also contains several important non-security
updates. This article contains detailed information about this update rollup,
answers frequently asked questions, and lists the updates that are included in
this update rollup.
INTRODUCTION
Update Rollup 1 for
Windows 2000 SP4 makes it easier for customers to enhance and maintain the
security and stability of their Windows 2000-based computers. For more
information about the problems that are fixed in Update Rollup 1 for Windows
2000 SP4, click the following article number to view the article in the
Microsoft Knowledge Base:
900345
(http://support.microsoft.com/kb/900345/) Problems that are fixed in the
Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 that is dated June 28,
2005
MORE
INFORMATION
Known issues
After the release of
Update Rollup 1 for Windows 2000 SP4, we identified several issues that may
occur when you install this update rollup. These issues are isolated, and affect
few customers. These issues are described in this article. This article also
explains how to resolve these issues. If you are affected by these issues, we
suggest that you do not install Update Rollup 1 for Windows 2000 SP4 until the
corresponding hotfix is available. We plan to reissue Update Rollup 1 for
Windows 2000 SP4 soon. Several hotfixes will be integrated into the new version
of Update Rollup 1 for Windows 2000 SP4.
Error
messages
You may receive one of
the following error messages when you visit the Windows Update Web
site:
| • |
MSXML3.DLL File Not
Found |
| • |
Error
0x80244001 |
| • |
Error 0x800700C1
|
If you performed an
express install of Update Rollup 1 for Windows 2000 SP4 before July 18, 2005,
the Msxml3.dll file might be reduced to a size of 0 bytes.
Note
You could only perform an express install of Update Rollup 1 for Windows 2000
SP4 before July 18 by using the new Microsoft Update Web site or by using
Windows Server Update Services (WSUS). This problem does not occur unless you
manually upgrade to Microsoft Update from Windows Update version 4 or by using
Software Update Services (SUS) 1.0.
We have addressed this issue by
making a minor change to the way that this update rollup is published on Windows
Update. No files were changed to fix this problem.
If you receive one of
these error messages after you install Update Rollup 1 for Windows 2000 SP4, you
may be experiencing this problem. Use one of the following three methods to
repair the Msxml3.dll file:
| • |
Download and install the
824151 security update. For more information about how to download and
install the 824151 security update, click the following article number to
view the article in the Microsoft Knowledge Base:
824151
(http://support.microsoft.com/kb/824151/) MS04-030: Vulnerability
in WebDAV XML message handler could lead to a denial of service
|
|
• |
Start the recovery console
from any Microsoft Windows setup CD. Then, copy the Msxml3.dll file from
the $NtUpdateRollupPackUninstall$ Update Rollup backup directory to the
%SystemRoot%\system32 directory. |
|
• |
Reinstall Update Rollup 1 for
Microsoft Windows 2000 Service Pack 4
(SP4). |
You receive a "Stop 0x000001E"
error message when you restart the computer after you install Update Rollup 1
for Windows 2000 SP4
You may receive the
following error message when you restart the computer after you install Update
Rollup 1 for Windows 2000 SP4:
Stop
0x000001E
This problem may occur
if you use a computer that has an older non-Plug-and-Play ISA, EISA, or Micro
Channel Architecture (MCA) SCSI controller. If you have already installed Update
Rollup 1 for Windows 2000 SP4 and have restarted the computer successfully, you
do not have this problem.
If you use one of these controllers and have
not already installed Update Rollup 1 for Windows 2000 SP4, we recommend that
you do not install the update. We are preparing a hotfix to prevent this
problem.
If you received this error message, start the recovery console
from any Windows setup CD. Then, copy the Scsiport.sys file from the
$NtUpdateRollupPackUninstall$ Update Rollup backup directory to the
%systemroot%\system32\drivers directory. Restart the computer after you copy the
file.
The following code is an example copy command.
Note
Make sure that you replace c:\windows with the name of your actual
Windows directory.
Copy c:\Windows\$NtUpdateRollupPackUninstall$\scsiport.sys c:\windows\system32\drivers
A hotfix for
this problem will be available soon. We plan to reissue Update Rollup 1 for
Windows 2000 SP4 with this hotfix included. The reissued update rollup will help
simplify future installations of Update Rollup 1 for Windows 2000 SP4. The
reissued update rollup will also reduce the chance of this problem occurring.
On a computer that uses
dynamic disks, two system drives may appear after you install Update Rollup 1
for Windows 2000 SP4
Warning
Serious problems might occur if you modify the registry incorrectly by using
Registry Editor or by using another method. These problems might require that
you reinstall your operating system. Microsoft cannot guarantee that these
problems can be solved. Modify the registry at your own risk.
On a
computer that uses dynamic disks, two system drives may appear after you install
Update Rollup 1 for Windows 2000 SP4. This problem occurs in the Mountmgr.sys
file. This problem only affects computers that use the dynamic disks feature.
This problem does not appear to affect functionality.
If you experience
this problem, the system alternates between the original system drive and the
new virtual system drive letter every time that you restart. If you experience
this problem, follow these steps:
| 1. |
Verify that the system drive
has the correct drive letter by using Windows Explorer, Disk Management,
or the SystemDrive environment variable from the SET command at a command
prompt. If the system drive does not have the correct drive letter,
restart the system. If you see a non-standard system drive, do not install
or remove any programs or hotfixes. If you do install or remove programs,
future compatibility may be affected. |
|
2. |
Start Registry Editor.
|
|
3. |
Remove the full path of the
Userinit.exe entry. To do this, follow these steps:
| a. |
Locate and then click the
following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current
Version\Winlogon |
| b. |
Right-click the Userinit entry, and then replace the REG_SZ
value of C:\WINNT\system32 with a
REG_SZ value of userinit.exe.
| |
|
4. |
Click Add/Remove Programs in Control Panel, and then click
Change/Remove for Update Rollup 1 for
Windows 2000 SP4 to uninstall the
update. |
A hotfix that
addresses this problem will be available soon. We plan to reissue Update Rollup
1 for Windows 2000 SP4 soon with this hotfix included. The reissued update
rollup will help simplify future installations of Update Rollup 1 for Windows
2000 SP4. The reissued update rollup will also reduce the chance of customers
experiencing this problem.
You cannot save files
from Microsoft Office programs directly to a floppy disk
Microsoft has
identified a problem in the Fastfat.sys file. This problem does not affect all
systems. On systems that are affected, you cannot save files from Microsoft
Office programs directly to a floppy disk. (Microsoft Office programs include
programs such as Microsoft Word and Microsoft Excel.) Microsoft plans to provide
an update to fix this problem on the Microsoft.com/downloads Web
site.
You use one of the following methods to work around this
problem:
| • |
Copy the Fastfat.sys file from
the $NtUpdateRollupPackUninstall$ Update Rollup backup directory to the
%SystemRoot%\system32\drivers directory. |
| • |
Save the Fastfat.sys file to the
hard disk. Then, copy the file to the floppy disk. |
| • |
Save the Fastfat.sys file by
using an alternative format, such as Rich Text Format
(RTF). |
A hotfix that addresses
this problem will be available soon. We plan to reissue Update Rollup 1 for
Windows 2000 SP4 soon with this hotfix included. The reissued update rollup will
help simplify future installations of Update Rollup 1 for Windows 2000 SP4. The
reissued update rollup will also reduce the chance of customers experiencing
this problem.
You cannot connect to a
Citrix server that has ICA sessions after you install Microsoft Update Rollup 1
for Windows 2000
After you install
Update Rollup 1 for Windows 2000 SP4 on a Citrix MetaFrame XP server or on a
Citrix MetaFrame Presentation Server 3.0-based server, you experience the
following problems when you connect to a Citrix server that has ICA
sessions:
| • |
You receive a Stop error
message. |
| • |
The Windows Graphical
Identification and Authentication (GINA) logon user interface does not
appear. |
| • |
The system console may be
unresponsive. |
| • |
The Winlogon.exe process uses
excessive CPU. |
For more information
about this problem and to obtain a hotfix from Citrix, visit the following
Citrix Web site:
Microsoft provides
third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy
of this third-party contact information.
A hotfix that addresses this
problem will be available soon. If you experience this problem, you will be able
to install the Microsoft hotfix or the Citrix hotfix before or after you install
Update Rollup 1 for Windows 2000 SP4 to resolve this problem. The hotfix will
not be included in the reissued Update Rollup 1 for Windows 2000 SP4 package
because of the limited number of customers affected.
An Exchange 5.5 message
transfer agent (MTA) that uses an X.400 connector on Windows 2000 SP4 may stop
transferring mail after you install Microsoft Update Rollup 1 for Windows
2000
A hotfix that addresses
this problem will be available soon. Customers who experience this problem will
be able to install the Microsoft hotfix before or after they install the Update
Rollup to resolve this problem. The hotfix will not be included in the reissued
Update Rollup package because of the limited number of customers
affected.
Customers who use Sophos
Anti-Virus for Windows version 5 may experience a delay when they log on to
their networks
After customers install
Microsoft Update Rollup 1 for Windows 2000 SP4, customers who use Sophos
Anti-Virus for Windows version 5 may experience a delay when they log on to
their networks. A computer may take 15 minutes to log on to the network when the
following message appears:
"preparing
network connections"
Sophos provides details
about how to resolve this problem to Sophos customers. For more information,
visit the following Sophos Web site:
Microsoft provides
third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy
of this third-party contact information.
Some versions of
Internet Security Systems products may not start after you install Microsoft
Update Rollup 1 for Windows 2000
This problem occurs
because you have obsolete signature files and an obsolete Blackdrv.sys file. To
resolve this problem, update to the current signature file. Updating to the
current signature file resolves the problem for all versions of Internet
Security Systems BlackICE. For more information, visit the following Microsoft
Knowledge Base article:
901159
(http://support.microsoft.com/kb/901159/) Some Internet Security Systems
products stop running after you install the revised MS05-019 security update or
after you install Update Rollup 1 for Windows 2000 SP4
Download
information
To download and install
Update Rollup 1 for Windows 2000 SP4, visit the following Microsoft Windows
Update Web site, and then install high-priority update 891861:
You can also download
this update rollup to deploy to multiple Windows 2000-based computers. The
package is available from the Microsoft Download Center.
The following
file is available for download from the Microsoft Download Center:
Download the Windows2000-KB891861-x86-ENU.EXE package
now.
(http://www.microsoft.com/downloads/details.aspx?FamilyID=c0a2ca36-1179-431c-80e6-60a494d3823d&DisplayLang=en)
Release
Date: June 27, 2005
For more information about how to download Microsoft
Support files, click the following article number to view the article in the
Microsoft Knowledge Base:
119591
(http://support.microsoft.com/kb/119591/) How to obtain Microsoft support
files from online services
Microsoft scanned this
file for viruses. Microsoft used the most current virus-detection software that
was available on the date that the file was posted. The file is stored on
security-enhanced servers that help prevent any unauthorized changes to the
file.
To download the package from the Windows Update Catalog, use the
Advanced Search Options feature to search for article ID number 891861. For more
information about how to download updates from the Windows Update Catalog, click
the following article number to view the article in the Microsoft Knowledge
Base:
323166
(http://support.microsoft.com/kb/323166/) How to download Windows updates
and drivers from the Windows Update Catalog
By including the most
important updates for Windows 2000, Update Rollup 1 for Windows 2000 SP4 may
help customers make Windows 2000-based computers more secure. Update Rollup 1
for Windows 2000 SP4 also makes it easier for customers to build new deployment
images. This update rollup requires less predeployment testing, because the
number of updates that are included in this update rollup is smaller than the
number of updates that are typically included in a service pack. Most customers
installed current versions of many of the files when older updates were
installed. Additionally, Microsoft has already released most of the contents of
this update rollup as individual updates and hotfixes. Individual hotfixes that
are not included in this update rollup will be available as individual
downloads.
Because Microsoft believes that Update Rollup 1 for Windows
SP4 meets the needs of customers better than a new service pack for Windows
2000, Microsoft will not release another service pack for Windows 2000.
Therefore, Windows 2000 SP4 is the final service pack for Windows 2000.
Customers who have not yet installed Windows 2000 SP4 should consider installing
Windows 2000 SP4 as soon as possible. Windows 2000 with SP4 is a prerequisite
for Update Rollup 1 for Windows 2000 SP4.
Frequently asked
questions
Q1: Why does
Microsoft believe that Update Rollup 1 for Windows 2000 SP4 meets the needs of
customers better than a new service pack for Windows 2000?
A1: Microsoft
talked to many customers about their plans for maintaining their Windows 2000
deployments. The most frequent requests were for Microsoft to make keeping
Windows 2000-based computers up to date as easy as possible, and for Microsoft
to reduce the predeployment testing that customers have to perform. Update
rollups may help customers make their computers more secure. Update rollups also
help customers build new system images without applying and tracking individual
hotfixes. Update Rollup 1 for Windows 2000 SP4 requires less predeployment
testing because the number of updates that are included in the update rollup is
smaller than the number of updates that are typically included in a service
pack. Additionally, Microsoft has already released most of the contents of this
update rollup as individual updates and hotfixes.
Because Windows 2000 is
a mature product, many of the Windows 2000 hotfixes that were released after the
release of Windows 2000 SP4 address relatively obscure problems. These problems
affect a small number of customers. At this point, an update rollup provides the
most usefulness at the least risk of instability.
Q2: How will Microsoft list Update Rollup 1 for
Windows SP4 on the Windows Update Web site?
A2: Update Rollup 1 for
Windows SP4 is listed as a high-priority update in the "Critical and Service
Packs" category on the Windows Update Web site. During the next few months,
Windows Update will transition Windows 2000 customers to a new version of
Windows Update. After this transition, Update Rollup 1 for Windows 2000 SP4 will
be listed in the "High Priority Updates" category.
Q3: Should I install Update Rollup 1 for Windows
SP4 even if I have kept my Windows 2000 SP4 systems up to date?
A3:Yes.
Update Rollup 1 for Windows 2000 SP4 contains important fixes that have not
previously been part of individual security updates. Additionally, this update
rollup contains enhancements that may help increase system security, increase
reliability, reduce support costs, and support the current generation of PC
hardware. To address minor compatibility problems that were introduced by
earlier security updates, hotfixes may have updated some files that were
installed by the earlier updates. This update includes the latest versions of
these files. Therefore, even if a system is fully up to date, Windows Update
still detects and installs this update rollup. Customers who use managed
security update deployment solutions should decide whether to deploy Update
Rollup 1 within their infrastructure.
Q4: Will Update Rollup 1 for Windows 2000 SP4 be
distributed over Automatic Updates?
A4: At first, this update rollup
will not be distributed over Automatic Updates. This delay is because of the
transition from the Windows Update version 4 infrastructure to the version 6
infrastructure. This update rollup will be made available as an automatic update
in September, 2005.
Q5:
Will there be an administrative blocking tool for Update Rollup 1 for Windows
2000 SP4 like there was for Windows XP SP2?
A5: No, Update Rollup 1 for
Windows 2000 SP4 is not a service pack. Therefore, this update rollup does not
require the same level of deployment control. This update rollup is treated like
other security or reliability updates. These updates are typically distributed
by Windows Update and by Automatic Updates.
Q6: Do I have to install the individual security
bulletin updates before I install Update Rollup 1 for Windows 2000 on new
installations of Windows 2000?
A6: No. First install Windows 2000 SP4,
and then install the update rollup. After you install the update rollup, run
Windows Update to find updates that were released after April 30, 2005, or that
were not included in the update rollup.
Q7: Are customers required to install Update Rollup
1 for Windows 2000 SP4?
A7: Customers are not required to install Update
Rollup 1 for Windows 2000 SP4. Microsoft designed the update rollup to make it
easy to keep Windows 2000-based computers up to date. Therefore, we strongly
recommend that customers install Update Rollup 1 for Windows 2000 SP4 as soon as
they can.
Q8: After
Update Rollup 1 for Windows SP4 is installed on a computer that is running
Windows 2000 SP4, will the service pack level of Windows 2000 change?
A8:
No. The service pack level of the computer remains at Windows 2000 SP4. After
you install Update Rollup 1 for Windows SP4, the computer will be up to date
from a life-cycle policy perspective until the end-of-life date for Windows
2000. The end-of-life date for Windows 2000 will be no sooner than January 1,
2010.
Q9: Is this the
first time that Microsoft has produced an update rollup instead of a service
pack?
A9: No. Microsoft has produced update rollups before. For more
information about update rollups that were previously released by Microsoft,
click the following article numbers to view the articles in the Microsoft
Knowledge Base:
826939
(http://support.microsoft.com/kb/826939/) Update Rollup 1 for Windows XP
is available
311401
(http://support.microsoft.com/kb/311401/) Windows 2000 Security Rollup
Package 1 (SR311401), January 2002
Q10: If Update
Rollup 1 for Windows 2000 SP4 offers significant benefits over a new service
pack, why does Microsoft not always use update rollups instead of service
packs?
A10: Service packs and update rollups play different, yet
complimentary roles. Service packs deliver important updates and new features
that customers request before the next release of a major operating system.
Update rollups deliver a group of updates between more major releases. Microsoft
uses update rollups when there is a longer than typical gap between service pack
releases. Later in the life cycle of a product, update rollups make it easier
for customers to keep their computers up to date. When customers install an
update rollup, customers do not have to individually install all the updates
that are available for a product.
Q11: How does Microsoft decide which hotfixes to include in an update
rollup?
A11: Microsoft examines the number of times that customers
request and download each hotfix from Microsoft Web sites and from Product
Support. Microsoft also evaluates the potential cost savings for customers. This
evaluation is based on experience in the Windows 2000 data center environment at
Microsoft.
Q12: What
kinds of updates are included in Update Rollup 1 for Windows 2000 SP4?
A12: Update Rollup 1 for Windows 2000 SP4 contains all the security
updates that were produced for Windows 2000 after the release of SP4 until April
30, 2005. On April 30, 2005, the contents for Update Rollup 1 were locked down
for final testing by Microsoft, by external beta sites, and by customer sites.
Update Rollup 1 for Windows 2000 SP4 also contains a small number of important
non-security updates. Update Rollup 1 for Windows 2000 SP4 contains updates that
meet the following criteria:
| • |
Updates that broadly apply to a
variety of customers |
| • |
Updates that are frequently
downloaded by customers |
| • |
Updates that have the potential
to help customers significantly decrease their IT costs
For
example, Update Rollup 1 for Windows 2000 SP4 contains updates to address
problems that are time-consuming for support professionals to troubleshoot
and fix. |
| • |
Updates that were included on new
computers by major Windows original equipment manufacturers (OEMs) after
Windows 2000 SP4 was released |
Q13: What
specific updates and hotfixes are included in Update Rollup 1 for Windows 2000
SP4?
A13: The following table lists all the updates and hotfixes that are
included in Update Rollup 1 for Windows 2000 SP4.
Fixes that are included
in Update Rollup 1 for Windows 2000 SP4
Update Rollup 1 for
Windows 2000 SP4 includes the following updates and hotfixes:
|
Security
Bulletin |
Article title |
Article
number |
| MS02-050 |
Certificate validation flaw could permit
identity spoofing |
329115 (http://support.microsoft.com/kb/329115/) |
| MS03-022 |
Vulnerability in ISAPI Extension for Windows
Media Services may cause code execution |
822343 (http://support.microsoft.com/kb/822343/) |
| MS03-025 |
Flaw in Windows message handling through
Utility Manager could enable privilege elevation |
822679 (http://support.microsoft.com/kb/822679/) |
| MS03-041 |
Vulnerability in Authenticode verification
could allow remote code execution |
823182 (http://support.microsoft.com/kb/823182/) |
| MS03-023 |
Buffer overrun in the HTML converter could
allow code execution |
823559 (http://support.microsoft.com/kb/823559/) |
| MS03-026 |
Buffer overrun in RPC could allow code
execution |
823980 (http://support.microsoft.com/kb/823980/) |
| MS03-034 |
Flaw in NetBIOS could lead to information
disclosure |
824105 (http://support.microsoft.com/kb/824105/) |
| MS03-045 |
Buffer overrun in the ListBox and in the
ComboBox Control could allow code execution |
824141 (http://support.microsoft.com/kb/824141/) |
| MS03-039 |
A buffer overrun in RPCSS could allow an
attacker to run malicious programs |
824146 (http://support.microsoft.com/kb/824146/) |
| MS03-044 |
Buffer overrun in Windows Help and Support
Center could lead to system compromise |
825119 (http://support.microsoft.com/kb/825119/) |
| MS03-042 |
Buffer Overflow in Windows Troubleshooter
ActiveX Control Could Allow Code Execution |
826232 (http://support.microsoft.com/kb/826232/) |
| MS03-043 |
Buffer overrun in Messenger service could
allow code execution |
828035 (http://support.microsoft.com/kb/828035/) |
| MS03-049 |
Buffer overrun in the Workstation service
could allow code execution |
828749 (http://support.microsoft.com/kb/828749/) |
| MS04-007 |
An ASN.1 vulnerability could allow code
execution |
828028 (http://support.microsoft.com/kb/828028/) |
| MS04-008 |
Vulnerability in Windows Media Services
could allow a Denial of Service attack |
832359 (http://support.microsoft.com/kb/832359/) |
| MS04-012 |
Cumulative Update for Microsoft
RPC/DCOM |
828741 (http://support.microsoft.com/kb/828741/) |
| MS04-006 |
A vulnerability in the Windows Internet Name
Service (WINS) could allow code execution |
830352 (http://support.microsoft.com/kb/830352/) |
| MS04-011 |
Security Update for Microsoft
Windows |
835732 (http://support.microsoft.com/kb/835732/) |
| MS04-014 |
Vulnerability in the Microsoft Jet Database
Engine could permit code execution |
837001 (http://support.microsoft.com/kb/837001/) |
| MS04-016 |
Vulnerability in DirectPlay could allow
denial of service |
839643 (http://support.microsoft.com/kb/839643/) |
| MS04-024 |
A vulnerability in the Windows shell could
allow remote code execution |
839645 (http://support.microsoft.com/kb/839645/) |
| MS04-023 |
Vulnerability in HTML Help could allow code
execution |
840315 (http://support.microsoft.com/kb/840315/) |
| MS04-020 |
A vulnerability in POSIX could allow code
execution |
841872 (http://support.microsoft.com/kb/841872/) |
| MS04-022 |
A vulnerability in Task Scheduler could
allow code execution |
841873 (http://support.microsoft.com/kb/841873/) |
| MS04-019 |
A vulnerability in Utility Manager could
allow code execution |
842526 (http://support.microsoft.com/kb/842526/) |
| MS04-030 |
Vulnerability in WebDAV XML message handler
could lead to a denial of service |
824151 (http://support.microsoft.com/kb/824151/) |
| MS04-032 |
Security update for Microsoft
Windows |
840987 (http://support.microsoft.com/kb/840987/) |
| MS04-038 |
Vulnerability in NNTP could allow code
execution |
883935 (http://support.microsoft.com/kb/840987/) |
| MS04-037 |
Vulnerability in Windows shell could allow
remote code execution |
841356 (http://support.microsoft.com/kb/841356/) |
| MS04-031 |
Vulnerability in NetDDE could allow remote
code execution |
841533 (http://support.microsoft.com/kb/841533/) |
| MS04-045 |
Vulnerability in WINS could allow remote
code execution |
870763 (http://support.microsoft.com/kb/870763/) |
| MS04-043 |
Vulnerability in HyperTerminal could allow
code execution |
873339 (http://support.microsoft.com/kb/873339/) |
| MS04-044 |
Vulnerabilities in Windows Kernel and LSASS
could allow elevation of privilege |
885835 (http://support.microsoft.com/kb/885835/) |
| MS04-041 |
A vulnerability in WordPad could allow code
execution |
885836 (http://support.microsoft.com/kb/885836/) |
| MS05-003 |
Vulnerability in the Indexing Service could
allow remote code execution |
871250 (http://support.microsoft.com/kb/871250/) |
| MS05-008 |
Vulnerability in Windows shell could allow
remote code execution |
890047 (http://support.microsoft.com/kb/890047/) |
| MS05-011 |
Vulnerability in server message block could
allow remote code execution |
885250 (http://support.microsoft.com/kb/885250/) |
| MS05-010 |
Vulnerability in the License Logging service
could allow code execution |
885834 (http://support.microsoft.com/kb/885834/) |
| MS05-015 |
Vulnerability in hyperlink object library
could allow remote code execution in Windows Server 2003 |
888113 (http://support.microsoft.com/kb/888113/) |
| MS05-001 |
Vulnerability in HTML Help could allow code
execution |
890175 (http://support.microsoft.com/kb/890175/) |
| MS05-013 |
Vulnerability in the DHTML editing component
ActiveX control could allow code execution |
891781 (http://support.microsoft.com/kb/891781/) |
| MS05-002 |
Vulnerability in cursor and icon format
handling could allow remote code execution |
891711 (http://support.microsoft.com/kb/891711/) |
| MS05-012 |
Vulnerability in OLE and COM could allow
remote code execution |
873333 (http://support.microsoft.com/kb/873333/) |
| MS05-016 |
Vulnerability in Windows Shell that could
allow remote code execution |
893086 (http://support.microsoft.com/kb/893086/) |
| MS05-019 |
Vulnerabilities in TCP/IP could allow remote
code execution and denial of service |
893066 (http://support.microsoft.com/kb/893066/) |
| MS05-017 |
Vulnerability in MSMQ could allow code
execution |
892944 (http://support.microsoft.com/kb/892944/) |
| MS05-018 |
Vulnerabilities in Windows kernel could
allow elevation of privilege and denial of service |
890859 (http://support.microsoft.com/kb/890859/) |
| MS05-020 |
Cumulative security update for Internet
Explorer |
890923 (http://support.microsoft.com/kb/890923/) |
| MS03-022 |
Vulnerability in ISAPI Extension for Windows
Media Services may cause code execution |
822343 (http://support.microsoft.com/kb/822343/) |
| MS05-014 |
Cumulative security update for Internet
Explorer |
867282 (http://support.microsoft.com/kb/867282/) |
For more information
about the problems that are fixed in Update Rollup 1 for Microsoft Windows 2000
SP4, click the following article number to view the article in the Microsoft
Knowledge Base:
900345
(http://support.microsoft.com/kb/900345/) Problems that are fixed in the
Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 that is dated June 28,
2005
Update Rollup 1 for
Windows 2000 SP4 TAPI information
Update Rollup 1 for
Windows 2000 SP4 changes how telephony server and client computers communicate
using the Telephony Application Programming Interface (TAPI).
After you
install Update Rollup 1 for Windows 2000 SP4, a Windows 2000 telephony client
accepts only encrypted RPC packets from a telephony server. The client does not
communicate with a telephony server that sends non-encrypted RPC packets.
However, this restriction does not apply to TAPI deployments where the client
computers are using mailslot instead of remote procedure call (RPC) for
communications with the telephony server. This restriction also does not apply
where the telephony server uses mailslot for communications.
By default,
a Windows 2000 client uses mailslot to communicate with the telephony server. A
Windows 2000 client uses RPC only when the client is explicitly configured as
connection-oriented. To configure the client this way, use the tcmsetup
command together with the -x switch. For example, use the following
command:
tcmsetup /r /x /c
ServerName
Notes
Update Rollup 1 for
Windows 2000 SP4 does not contain updates for Windows components that are not
included with a clean slipstream install of Windows 2000 SP4. If components were
previously installed or updated, you must download individual security updates
by using Windows Update.
Examples of these updates include the following:
| • |
MS03-011 - Flaw in Microsoft VM
Could Enable System Compromise (KB816093)
The Microsoft VM is not
included in SP4 natively. However the VM may be resident on systems which
were updated to SP4 from a prior SP or installed by a third party software
package. |
| • |
Internet Explorer 6 and Outlook
Express 6
Windows 2000 originally included Internet Explorer 5.01.
Service packs for Windows 2000 only affect this version. We recommend that
you install Internet Explorer 6 SP1 and the current cumulative Internet
Explorer security updates on Windows 2000
computers. |
APPLIES TO
| • |
Microsoft Windows 2000
Server |
| • |
Microsoft Windows 2000
Professional Edition |
| • |
Microsoft Windows 2000 Advanced
Server |
| • |
Microsoft Windows 2000 Datacenter
Server |
