Windows 2000 Critical Update, February 17, 2000

Microsoft has released a patch that corrects the following problems:

• A vulnerability that could permit a malicious user to view files on a Web server and reveal where Web folders are physically located on the server. Under certain conditions, the vulnerability could be used to cause e-mail programs to crash. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
  251170  (http://support.microsoft.com/kb/251170/EN-US/ ) Malformed Argument in Hit-Highlighting Allows Access to Server
  252463  (http://support.microsoft.com/kb/252463/EN-US/ ) Index Server Error Message Reveals Location of Web Folders
• An issue that involves a potential data-damage problem that can occur when you save files as .htm to an HTTP server from Microsoft Office 2000 programs such as Microsoft Word for Windows and Microsoft Excel.
• An issue that involves a VBScripting problem where the year is reported incorrectly when using the Wareki or Taiwan calendar. This problem does not occur if you are using the Gregorian calendar. Note that this is not a year 2000 problem, as it affects all dates. For additional information about year issues with a non-Gregorian calendar, click the article number below to view the article in the Microsoft Knowledge Base:
  253342  (http://support.microsoft.com/kb/253342/EN-US/ ) Year is Reported Incorrectly on a Non-Gregorian Calendar

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

The Windows 2000 Critical Update, February 17, 2000, is available from the following Microsoft Web site: You can also download this critical update (for installation later or on a different computer) from the following Microsoft Web sites: For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base: