BOOT_DRIVER_CALLBACK_FUNCTION - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntddk.h
BOOT_DRIVER_CALLBACK_FUNCTION BootDriverCallbackFunction;
VOID BootDriverCallbackFunction(
PVOID CallbackContext,
BDCB_CALLBACK_TYPE Classification,
PBDCB_IMAGE_INFORMATION ImageInformation
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
A boot-start driver's BOOT_DRIVER_CALLBACK_FUNCTION routine can monitor boot-start driver initialization events and return data to the kernel to enable the kernel to decide whether to initialize each boot-start driver. The function prototype to register a boot-start driver callback routine is as follows.
CallbackContextThe value that the driver passed as the _CallbackContext_ parameter to IoRegisterBootDriverCallback when it registered this BOOT_DRIVER_CALLBACK_FUNCTION implementation.
ClassificationA BDCB_CALLBACK_TYPE enumeration value that either identifies the status of boot-start driver initialization or indicates that a boot-start driver is about to be initialized.
ImageInformationA pointer to a BDCB_IMAGE_INFORMATION structure that contains information that is specific to the type of callback. The structure type depends on the value passed for CallbackType, as shown in the following table.
| Value of CallbackType | Corresponding structure to use |
|---|---|
| BdCbStatusUpdate | BDCB_STATUS_UPDATE_TYPE |
| BdCbInitializeImage | BDCB_CLASSIFICATION |
To be notified of boot-start driver initialization operations, an early launch anti-malware (ELAM) driver can call IoRegisterBootDriverCallback. To unregister, call IoUnRegisterBootDriverCallback.
IoUnregisterBootDriverCallback