NetAdapterCx limitations
This topic describes caveats you should be aware of when calling WDF functions from a NetAdapterCx client driver.
| Function | Description |
|---|---|
| WdfDeviceInitAssignSDDLString | By default NetDeviceInitConfig assigns SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RW_RES_R as the default SDDL. If you specify a more restrictive SDDL, the application might not be able to send query OIDs to the adapter. |
| WdfDeviceInitSetFileObjectConfig | The client driver must not set WdfFileObjectWdfCanUseFsContext in the FileObjectClass member of WDF_FILEOBJECT_CONFIG. |
| WdfDeviceInitAssignName, WdfDeviceInitSetReleaseHardwareOrderOnFailure, WdfDeviceInitSetDeviceType, WdfDeviceInitSetCharacteristics, WdfDeviceInitSetIoType, WdfDeviceInitSetPowerPageable | NetDeviceInitConfig calls these routines on behalf of the client driver. The client driver should not call these. |
| WdfDeviceCreateDeviceInterface | If the client driver calls WdfDeviceCreateDeviceInterface with the ReferenceString parameter equal to NULL, NDIS intercepts I/O requests sent to the device interface. To avoid this behavior, specify any reference string. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for