0x00010008 - FLG_ADDREG_TYPE_MULTI_SZ | FLG_ADDREG_APPENDĪfter your driver is loaded as an upper filter, it is responsible for forwarding I/O requests to the next driver in the stack. Load the redirector as an upperfilter on this specific device.

If your driver's device stack contains any drivers that are not UMDF, your INF file must include an AddReg section that specifies the reflector as an upper filter driver: If your driver's device stack contains only UMDF drivers, skip this step.

To install a lower filter driver, simply reverse the arguments for UmdfServiceOrder.įor more info about these and other UMDF-specific INF directives, see Specifying WDF Directives in INF Files. The first parameter specifies the lowest UMDF driver in the device stack. The drivers are added to the device stack in the order that they are listed in the UmdfServiceOrder entry. UmdfService=UMDFFilter,UMDFFilter_Install UmdfService=UMDFFunction,WUDFFuncDriver_Install In this topic, we'll specify an upper filter driver: In addition to any UMDF-specific directives your driver may specify, you must specify the UmdfService and UmdfServiceOrder directives. Starting in UMDF version 2, your driver instead calls WdfFdoInitSetFilter.

Also, you cannot install UMDF version 1 and version 2 drivers in the same device stack.Ī UMDF 1 filter driver should call IWDFDeviceInitialize::SetFilter from the its IDriverEntry::OnDeviceAdd callback function. This topic applies to both UMDF versions 1 and 2.Īs you structure your device stack, keep in mind that the framework currently supports only one contiguous block of UMDF drivers per stack. You cannot use UMDF to write a class filter driver. This topic describes how to install and configure a User-Mode Driver Framework (UMDF) device-specific (upper or lower) filter driver.

A lower filter driver attaches below a device's function driver, while an upper filter attaches above a device's function driver. A filter driver can support a specific device or all devices in a setup class.

How to play undf files