Geoff Chappell, Software Analyst
The table below lists all the functions that first appear as KERNEL32 exports in version 10.0, i.e., for Windows 10.
The functions that are highlighted yellow appear to be undocumented, as far as shows up in a search online today (12th March 2016).
| Function | Remarks |
|---|---|
| CreateProcessAsUserA | also named export from ADVAPI32 3.51 and higher; implemented as jump to KERNELBASE |
| DiscardVirtualMemory | forwarded to api-ms-win-core-memory-l1-1-2; documented for Windows 8.1 Update and higher |
| FreeMemoryJobObject | |
| GetProcessDefaultCpuSets | forwarded to api-ms-win-core-processthreads-l1-1-3 |
| GetSystemCpuSetInformation | forwarded to api-ms-win-core-processthreads-l1-1-3 |
| GetThreadSelectedCpuSets | forwarded to api-ms-win-core-processthreads-l1-1-3 |
| OfferVirtualMemory | forwarded to api-ms-win-core-memory-l1-1-2; documented for Windows 8.1 Update and higher |
| QueryIoRateControlInformationJobObject | |
| QueryProtectedPolicy | forwarded to api-ms-win-core-processthreads-l1-1-2; documented for Windows 8.1 and higher |
| QuirkIsEnabledForPackage3Worker | |
| QuirkIsEnabledForPackage4Worker | |
| ReclaimVirtualMemory | forwarded to api-ms-win-core-memory-l1-1-2; documented for Windows 8.1 Update and higher |
| SetIoRateControlInformationJobObject | |
| SetProcessDefaultCpuSets | forwarded to api-ms-win-core-processthreads-l1-1-3 |
| SetProtectedPolicy | forwarded to api-ms-win-core-processthreads-l1-1-2; documented for Windows 8.1 and higher |
| SetThreadSelectedCpuSets | forwarded to api-ms-win-core-processthreads-l1-1-3 |
| WaitForDebugEventEx | forwarded to api-ms-win-core-debug-l1-1-2; documentation is “preliminary” |
| WerGetFlagsWorker | |
| WerSetFlagsWorker |
In version 10.0, one function that is exported from all known x64 builds becomes exported also from x86 builds:
Note, however, that it remains documented only for x64 builds.
Version 10.0 discontinues two exports: