Geoff Chappell, Software Analyst
API-MS-Win-Core-LocalRegistry-L1-1-0
All functions in the API-MS-Win-Core-LocalRegistry-L1-1-0 set are documented
exports from ADVAPI32:
- RegCloseKey
- RegCreateKeyExA
- RegCreateKeyExW
- RegDeleteKeyExA
- RegDeleteKeyExW
- RegDeleteTreeA
- RegDeleteTreeW
- RegDeleteValueA
- RegDeleteValueW
- RegDisablePredefinedCacheEx
- RegEnumKeyExA
- RegEnumKeyExW
- RegEnumValueA
- RegEnumValueW
- RegFlushKey
- RegGetKeySecurity
- RegGetValueA
- RegGetValueW
- RegLoadKeyA
- RegLoadKeyW
- RegLoadMUIStringA
- RegLoadMUIStringW
- RegNotifyChangeKeyValue
- RegOpenCurrentUser
- RegOpenKeyExA
- RegOpenKeyExW
- RegOpenUserClassesRoot
- RegQueryInfoKeyA
- RegQueryInfoKeyW
- RegQueryValueExA
- RegQueryValueExW
- RegRestoreKeyA
- RegRestoreKeyW
- RegSaveKeyExA
- RegSaveKeyExW
- RegSetKeySecurity
- RegSetValueExA
- RegSetValueExW
- RegUnLoadKeyA
- RegUnLoadKeyW
The implementations in ADVAPI32 version 6.1 and higher are just stubs which transfer
the handling to wherever the schema redirects the API Set.
New Locations
Non-trivial implementations of all functions in this API Set are exported from
KERNEL32 version 6.1 and higher.
Schema Redirection
The Windows 7 schema redirects this API Set to KERNEL32. Thus:
- high-level executables, which do not use the API Set, continue to import these
functions from ADVAPI32;
- low-level executables have their imports from the API Set redirected to KERNEL32;
- as a particular case of the preceding, the stub implementations in ADVAPI32
import from underlying implementations in KERNEL32.