NTDLL 6.1 Named Exports

The table below lists all the named NTDLL exports that were added for version 6.1. Some new functions for version 6.1 that are exported only by ordinal are listed separately. Of the new functions exported by name, hardly any are yet documented, though a few are at least declared in one or another header file from the WDK or SDK.

Documentation status is conveyed by colour coding. NTDLL functions that actually are documented as exports from NTDLL are shown with no background colour. So too are the NTDLL implementations of documented functions from the C Run-Time Library. Functions that are documented in the Windows Driver Kit (WDK), typically as exports from the NT kernel for use by ring 0 software such as device drivers, but sometimes with non-specific talk of being callable from user mode, are lightly shaded blue. Documented functions that are known not to have been documented immediately they were introduced are a darker blue if the only known documentation is in the WDK, else pink. If the delayed documentation came specifically from its listing among the Settlement Program Interfaces in late 2002, then the function is less pink since Microsoft at least acknowledged that the documentation was late. A function is shaded grey if it seems not to be documented but is known to be the entire low-level implementation of some function in a higher-level DLL such as KERNEL32 or ADVAPI32. Identifying these is a work in progress. Functions that look to be completely undocumented are highlighted yellow. However, an undocumented function is shaded yellow, as semi-documented, if it is at least declared in one or another header file from the WDK or, exceptionally, the SDK. If you browse with scripting enabled, hovering over any text that has a background colour should produce a tooltip that explains the formatting.

That RtlFillMemoryUlonglong appears only as late as Windows 7 is conspicuous. It has for some years been documented in the WDK’s section for Installable File Systems, and declared in NTIFS.H as an importable function. Yet no import library supplied with the WDK for Windows Vista (for instance) resolves the corresponding import symbol. All builds of both the NT kernel and NTDLL from at least as far back as Windows 2000 do have code for an RtlFillMemoryUlonglong function, but they don’t export that function. Could it be that the function was meant to be exported all along, consistently with the documentation, but was neglected by an oversight that took years for anyone to notice (or bother correcting)?