UnregisterInterfaceTimestampConfigChange function (iphlpapi.h)
Cancels notifications about timestamp capability changes by unregistering the callback function you registered in a call to RegisterInterfaceTimestampConfigChange.
To avoid deadlock, you shouldn't call UnregisterInterfaceTimestampConfigChange in the context of the thread that's executing a callback that was specified to RegisterInterfaceTimestampConfigChange. This is because UnregisterInterfaceTimestampConfigChange waits for outstanding notification callbacks to complete before it returns. Consequently, UnregisterInterfaceTimestampConfigChange mustn't be called in a way that prevents an outstanding notification callback from completing. No further callbacks will take place after UnregisterInterfaceTimestampConfigChange returns.
For more info, and code examples, see Packet timestamping.
IPHLPAPI_DLL_LINKAGE VOID UnregisterInterfaceTimestampConfigChange( HIFTIMESTAMPCHANGE NotificationHandle );
Type: _In_ HIFTIMESTAMPCHANGE
The handle that was returned by RegisterInterfaceTimestampConfigChange. This identifies the registration to be canceled.
A DWORD return code indicating success or failure.
|Minimum supported client||Windows 10 Build 20348|
|Minimum supported server||Windows 10 Build 20348|