NTFS Does Not Always Update the Remaining Length in the Reparse Buffer When Second Data Stream Is Created (289621)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Professional SP1

This article was previously published under Q289621

SYMPTOMS

When a second data stream is created, the NTFS file system does not always update the remaining length in the reparse buffer. NTFS may not set the remaining path length in ReparseData->Reserved if the related file object is opened by ID.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Microsoft is researching this problem and will post more information in this article when the information becomes available.

Modification Type:MajorLast Reviewed:11/19/2003
Keywords:kbbug kbenv kbpending kbProgramming KB289621