Expand Minimize

FwpmCalloutDeleteByKey0 function

The FwpmCalloutDeleteByKey0 function deletes a callout from the filter engine.

Note  FwpmCalloutDeleteByKey0 is a specific version of FwpmCalloutDeleteByKey. See WFP Version-Independent Names and Targeting Specific Versions of Windows for more information.

Syntax


NTSTATUS NTAPI FwpmCalloutDeleteByKey0(
  _In_  HANDLE engineHandle,
  _In_  const GUID *key
);

Parameters

engineHandle [in]

A handle for an open session to the filter engine. A callout driver calls the FwpmEngineOpen0 function to open a session to the filter engine.

key [in]

A pointer to a GUID that uniquely identifies the callout that is being deleted from the filter engine. This must be a pointer to the same GUID that was specified when the callout driver called the FwpmCalloutAdd0 function to add the callout to the filter engine.

Return value

The FwpmCalloutDeleteByKey0 function returns one of the following NTSTATUS codes.

Return codeDescription
STATUS_SUCCESS

The callout was successfully deleted from the filter engine.

STATUS_FWP_IN_USE

One or more filters in the filter engine specify the callout for the filter's action.

STATUS_FWP_CALLOUT_NOT_FOUND

There is not a callout in the filter engine that matches the GUID specified in the key parameter.

Other status codes

An error occurred.

 

Remarks

A callout driver calls the FwpmCalloutDeleteByKey0 function to delete a callout from the filter engine, using the GUID key to identify the callout to be deleted.

Callout drivers do not typically delete their callouts from the filter engine. In most situations, this is handled by a user-mode Windows Filtering Platform management application.

A callout can be deleted from the filter engine only if there are no filters in the filter engine that specify the callout for the filter's action.

Requirements

Version

Available starting with Windows Vista.

Header

Fwpmk.h (include Fwpmk.h)

IRQL

PASSIVE_LEVEL

See also

FwpmCalloutAdd0
FwpmCalloutDeleteById0
FwpmEngineOpen0

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft