Primary classification: NOT_SUPPORTED as a published-contract claim. The public API contract does not document that passing the unchanged, root-only VOLUME_NAME_NT result—such as \Device\HarddiskVolumeN—to user-mode NtCreateFile reopens the mounted filesystem’s root directory rather than the volume/device object.
This classification means the requested use cannot be claimed as officially supported from the published contract. It does not mean that the call must fail or cannot produce a root-directory handle on particular Windows versions.
Why the composition is not established
GetFinalPathNameByHandleW(... | VOLUME_NAME_NT) documents its result as an NT device-object path and explicitly says this type of path cannot be used directly by Windows programs as an ordinary path ^1^.
NtCreateFile separately permits ObjectName to be a fully qualified file specification or the name of a device object. It can open a file, directory, device, or volume, but it does not define a special rule saying that a bare volume-device name denotes the filesystem root ^2^.
The closest documented distinction is in the Win32 CreateFileW contract:
- A volume name without the trailing backslash opens the volume.
- A volume name with the trailing backslash opens the filesystem root.
That rule is documented for Win32 volume paths processed by CreateFileW, not for a native OBJECT_ATTRIBUTES.ObjectName passed to NtCreateFile ^3^ ^4^.
Consequently, the public references do not establish that these native names are equivalent:
\Device\HarddiskVolumeN
\Device\HarddiskVolumeN\
Requested sub-classifications
Trailing backslash
Undocumented for this native operation.
The published NtCreateFile contract does not say whether the trailing separator is required, prohibited, or immaterial when the name identifies a volume device and the intended target is its filesystem root. The documented Win32 rule must not be projected onto native parsing without an explicit contract.
Therefore, neither adding nor removing the slash converts this technique into a documented native-root reopening procedure.
NTFS versus ReFS
No documented distinction resolves the issue.
The GetFinalPathNameByHandleW documentation lists ReFS support, but that only establishes support for retrieving the final path. It does not establish how a root-only NT device path is subsequently interpreted by NtCreateFile ^1^.
No supplied public contract provides separate NTFS and ReFS guarantees for this composition.
FILE_OPEN_REPARSE_POINT
Conditionally documented, but it does not settle the root-versus-volume question.
When the file being opened is itself a reparse point, FILE_OPEN_REPARSE_POINT bypasses normal processing and attempts to open that reparse-point file directly ^2^. It does not document that a bare volume-device name is transformed into, or guaranteed to designate, the mounted filesystem root.
Also note that the documented compatibility list for FILE_DIRECTORY_FILE does not include FILE_OPEN_REPARSE_POINT. Therefore, adding FILE_DIRECTORY_FILE to force directory type would not make the proposed combination documented ^2^. A closely related Microsoft Q&A answer likewise concludes that the public compatibility list does not establish that exact directory-option combination as supported ^5^.
Using the resulting handle for relative opens
Supported only if the first call actually returned a filesystem-directory handle; that prerequisite is not guaranteed by this bootstrap.
OBJECT_ATTRIBUTES documents that a non-null RootDirectory can refer to a filesystem directory and that ObjectName is then interpreted relative to it ^6^. The WDK description similarly supports a pathname relative to the directory file represented by RootDirectory ^7^.
Those rules do not establish that the proposed root-only device-name call produced such a directory handle. If it produced a volume/device handle instead, the relative-directory contract would not apply.
Secondary question
Classification: DOCUMENTATION_DOES_NOT_GUARANTEE.
The general OBJECT_ATTRIBUTES page says that RootDirectory can refer to a filesystem directory and does not impose handle-provenance requirements ^6^. However, the user-mode NtCreateFile reference more specifically describes RootDirectory as a directory handle “obtained by a preceding call to NtCreateFile” ^2^.
Because the specific API reference does not promise that a directory handle returned by CreateFileW is interchangeable for this purpose, the public contract cannot sustain either:
-
YES — any valid filesystem-directory handle, or -
NO — must originate from NtCreateFile.
Observed interoperability does not close that documentary gap.
Contract-safe alternatives and escalation
For a published Win32 contract, retain or duplicate the filesystem-root handle originally opened with the trailing-backslash Volume GUID path instead of reconstructing it from VOLUME_NAME_NT. CreateFileW explicitly documents that the trailing-backslash volume path opens the filesystem root ^3^.
For an authoritative ruling on native reopening and Win32 handle provenance, open a Microsoft support incident and request escalation to Windows Filesystems / I/O Manager / Object Manager / Windows SDK documentation. Include:
- A minimal reproducer with the exact
UNICODE_STRING, access mask, sharing, disposition, and options. - NTFS and ReFS cases.
- The requested classifications.
- A request for a supported-contract statement rather than runtime diagnosis.
Microsoft’s public Windows developer guidance identifies a support incident as the route for organizations with a support contract ^8^. Documentation feedback can additionally request that the NtCreateFile and GetFinalPathNameByHandleW contracts explicitly cover this composition, but feedback alone is not an engineering support determination.
References
- GetFinalPathNameByHandleW function (fileapi.h)
- NtCreateFile function (winternl.h)
- CreateFileW function (fileapi.h)
- Naming a Volume
- NTFS single-component NtCreateFile relative to a held directory during junction conversion: original-object-or-refusal contract? - Microsoft Q&A
- OBJECT_ATTRIBUTES structure (ntdef.h)
- NtCreateFile function (ntifs.h)
- Help and guidance for Windows developers