technical support ticket for Windows 11 filesystem API behaviour.

Rock Haywood 0 Reputation points
2026-11-17T18:15:26.79+00:00

Hello Microsoft Support,

I am requesting assistance with opening a technical support ticket for Windows 11 filesystem API behaviour.

We are developing a Windows application and require an authoritative clarification concerning the Microsoft NtCreateFile API.

Our technical question:

When a Windows application opens and retains a verified directory handle, then uses that handle as OBJECT_ATTRIBUTES.RootDirectory in NtCreateFile to create a new file or directory:

Does Windows guarantee that the new object will either be created inside the originally opened parent directory or that creation will fail, even if another process concurrently modifies the parent directory's reparse-point information?

We need confirmation of:

Whether this guarantee is supported on Windows 11 with NTFS.

Which API flags, access rights and sharing options are required.

Whether OBJ_DONT_REPARSE is necessary and supported in this scenario.

Whether any filesystem or reparse-tag limitations apply.

If the guarantee is unavailable, what Microsoft-supported preventative mechanism is recommended.

We are seeking an authoritative technical answer or referral to the appropriate Windows filesystem engineering support team.

We are not requesting troubleshooting, software installation or remote access.

Please advise how to open the appropriate technical support case and whether there is any charge before proceeding.

Thank you.

Windows development | Windows API - Win32
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-17T18:16:39.8933333+00:00

    The published Windows API contract does not guarantee that a directory-relative NtCreateFile will either create inside the originally opened NTFS directory object or fail when another process concurrently converts that directory into a reparse point; open a Microsoft business support incident to obtain an authoritative, case-specific engineering determination.^1^

    Open the appropriate support case

    1. Go to Microsoft’s Windows developer support page and, under Enterprise support, select Create a support incident. This route requires a Microsoft support contract.^2^
    2. If your organization has an existing support agreement, associate its Access ID and Agreement ID with the Support for Business account, then submit an on-premises professional support incident.^3^
    3. Select the closest available Windows / Windows application development / Windows API product and problem categories.
    4. State that the request is for a published supportability and filesystem-semantics determination, not code review, implementation work, remote access, or ordinary troubleshooting.
    5. Ask that the case be routed or escalated to the team responsible for Windows I/O Manager, NTFS, and reparse-point semantics.

    If no support agreement is available, use Microsoft Professional Support’s pay-per-incident option. An incident covers one support issue and the reasonable effort needed to resolve it; the fee is incident-based rather than hourly. The public FAQ does not publish a universal fixed price, so the applicable charge must be shown or confirmed during case creation. An unresolved case is not automatically free—its billing status is at Microsoft’s discretion.^4^

    Keep the submission as one narrowly framed issue to avoid it being divided into multiple chargeable incidents.

    Suggested incident description

    Title: Windows 11 NTFS atomicity contract for directory-relative NtCreateFile during concurrent reparse-point conversion

    Environment: Windows 11 x64, local NTFS volume, user-mode application.

    Question: When a verified directory handle is retained and supplied as OBJECT_ATTRIBUTES.RootDirectory, with a validated single-component relative ObjectName, does Microsoft support a guarantee that NtCreateFile either:

    1. creates the new object in the directory object represented by the retained handle, or
    2. fails before creating an object elsewhere,

    if another process concurrently sets, changes, or removes reparse-point data on that directory?

    Please address conversion completed before the call, conversion during name resolution/insertion, and conversion after child creation.

    Please identify:

    • supported Windows 11 versions and NTFS qualifications;
    • required parent-handle access and sharing modes;
    • required child DesiredAccess, ShareAccess, CreateDisposition, and CreateOptions;
    • whether OBJ_DONT_REPARSE is supported for this exact user-mode, directory-relative create;
    • whether FILE_OPEN_REPARSE_POINT changes the guarantee;
    • reparse-tag or filesystem-filter limitations;
    • the Microsoft-supported preventative mechanism if no object-or-refusal guarantee exists.

    Attach a minimal reproducer, exact OS build (winver), volume type, reparse tag, all numeric flag values, returned NTSTATUS/IO_STATUS_BLOCK, and a concurrency timeline. Microsoft recommends supplying the application/component topology, relevant event logs, and reproducible steps when contacting technical support.^5^

    What the current public contract establishes

    • A non-null RootDirectory makes ObjectName relative to the directory represented by that handle.^6^
    • The documentation does not define an atomic boundary between that relative create and a concurrent operation that changes the parent’s reparse state. Consequently, the requested race guarantee, exact access mask, and share-mode recipe cannot be supplied authoritatively from the published contract.^1^
    • OBJ_DONT_REPARSE is documented to refuse name parsing when a reparse point is encountered, returning STATUS_REPARSE_POINT_ENCOUNTERED.^7^ However, that parsing rule does not document atomicity against concurrent conversion of the already-held root directory.
    • FILE_OPEN_REPARSE_POINT has a different purpose: it opens the reparse-point object itself without normal reparse processing. It is not documented as a concurrency or containment guarantee.^8^
    • NTFS cannot establish a reparse point on a nonempty directory.^9^ Keeping a directory nonempty may therefore prevent that specific conversion operation, but Microsoft’s documentation does not present this as the general supported security mechanism for the race described.
    • Oplocks provide notification and coordination around conflicting opens; the published oplock procedure does not promise prevention of all reparse-point metadata changes or the requested containment property.^10^

    Until Microsoft supplies a written contract for the exact parameter combination, treat observed behavior on individual Windows 11 builds as implementation evidence rather than a compatibility or security guarantee.


    References

    1. NTFS single-component NtCreateFile relative to a held directory during junction conversion: original-object-or-refusal contract? - Microsoft Q&A
    2. Help and guidance for Windows developers
    3. Using Access ID and agreement ID to create on-premises professional support incidents | Microsoft Learn
    4. Microsoft Professional Support (pay-per-incident): FAQ | Microsoft Support
    5. Contacting Support
    6. NtCreateFile function (winternl.h)
    7. OBJECT_ATTRIBUTES structure (ntdef.h)
    8. NtCreateFile function (ntifs.h)
    9. Reparse points
    10. Requesting and granting oplocks
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.