EVT_WDF_IO_TARGET_REMOVE_COMPLETE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// wdfiotarget.h
EVT_WDF_IO_TARGET_REMOVE_COMPLETE EvtWdfIoTargetRemoveComplete;
VOID EvtWdfIoTargetRemoveComplete(
[in] WDFIOTARGET IoTarget
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
[Applies to KMDF and UMDF]
A driver's EvtIoTargetRemoveComplete event callback function performs operations when the removal of a specified remote I/O target is complete.
IoTarget [in]A handle to an I/O target object.
To register an EvtIoTargetRemoveComplete callback function, place the callback function's address in the I/O target's WDF_IO_TARGET_OPEN_PARAMS structure.
The framework calls your driver's EvtIoTargetRemoveComplete callback function after the driver's EvtIoTargetQueryRemove callback function returns STATUS_SUCCESS, or after the device has been removed unexpectedly (surprise-removed).
A driver's EvtIoTargetRemoveComplete callback function must permanently close the remote I/O target by calling WdfIoTargetClose. Because the target device has been removed, the EvtIoTargetRemoveComplete callback function should also perform any additional target-removal operations that might be necessary, such as releasing system resources that the driver might have allocated when it opened the target.
The EvtIoTargetRemoveComplete callback function is optional. If the driver does not supply this callback function, the framework permanently closes the I/O target.
For more information about the EvtIoTargetRemoveComplete callback function, see Controlling a General I/O Target's State.