Hi @Rock Haywood ,
Thank you for reaching out and providing a clear description of your scenario.
Regarding your questions, below are a few points that may help clarify the documented behavior:
API guarantee: According to the NtCreateFile function (winternl.h), RootDirectory allows a relative path to be resolved using an existing directory handle. However, the published API contract does not explicitly guarantee that creation will remain within the originally opened directory or fail when its reparse-point information is modified concurrently.
Flags and limitations: The OBJECT_ATTRIBUTES structure (ntdef.h) describes OBJ_DONT_REPARSE as preventing name parsing through encountered reparse points. However, it does not establish an atomicity guarantee for this specific race condition. Similarly, no documented combination of access rights, sharing modes, or FILE_OPEN_REPARSE_POINT is known to provide the requested guarantee.
Official confirmation and support options: Since your question requires an authoritative determination of Windows filesystem behavior, I recommend contacting Windows Developer Support to open a technical support incident. Depending on your existing support agreement, a paid support incident may be required.
When submitting your request, including the exact Windows build, NTFS configuration, API flags, and a minimal reproducer would help the support team investigate the specific concurrency scenario.
I hope this helps clarify the available documentation and the appropriate next steps. If you found this helpful, you can refer to this guidance to confirm it and help others with similar questions.
Thank you.