This function writes all the attributes of the specified open key into the registry.
LONG RegFlushKey( HKEY hKey );
[in] Handle to a currently open key, which is validated but ignored. It can also be one of the following predefined reserved handle values:
ERROR_SUCCESS indicates success. A nonzero error code defined in Winerror.h indicates failure. To get a generic description of the error, call FormatMessage with the FORMAT_MESSAGE_FROM_SYSTEM flag set. The message resource is optional; therefore, if you call FormatMessage it could fail.
If RegFlushKey is called, the operating system attempts to flush the entire registry to the platform-supported storage. The implementation of this function OEM-dependent, which results in the following scenarios:
- If an OEM does not support persistent registry storage, then a call to this function fails.
- If an OEM does support persistent registry storage, then a call to this function flushes the entire registry to the OEM for storage.
- If the OEM fails the flush request, then RegFlushKey fails.
Unlike RegCloseKey, the RegFlushKey function returns only when all the data has been written to the registry.
By default, Windows CE does not support a lazy flush of the registry; therefore, it is important that all applications call RegFlushKey to save important registry information. Call RegFlushKey after a group of changes have been made, but not for every individual registry change. Frequent calling of RegFlushKey can degrade performance. Platforms that need to implement a lazy-flush or power-down flush can do so by calling RegFlushKey at anytime from a shell, from a low priority thread, or in the power-off switch handler in the keyboard driver.
|Runs on||Versions||Defined in||Include||Link to|
|Windows CE OS||2.10 and later||Winreg.h||Coredll.lib, Fsreg.lib|
Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
Last updated on Tuesday, July 13, 2004
© 1992-2000 Microsoft Corporation. All rights reserved.