HRESULT 0x801F0007 (ERROR_FLT_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The minifilter tried to register before the Filter Manager driver was available.

Previous	Next
ERROR_FLT_NOT_SAFE_TO_POST_OPERATION	ERROR_FLT_FILTER_NOT_READY

ERROR_FLT_NOT_INITIALIZED

Registration failed before Filter Manager was ready

ERROR_FLT_NOT_INITIALIZED is returned when a minifilter calls FltRegisterFilter but the Windows Filter Manager is not available as a loaded driver. The failure occurs before a filter has registered callbacks, acquired its opaque PFLT_FILTER handle, or begun attaching to volumes. It is therefore not evidence that a particular file, filesystem, or volume rejected the filter.

A normal minifilter startup sequence is global initialization, FltRegisterFilter, then FltStartFiltering. The Microsoft MiniSpy sample follows this order after it has initialized its own state and configuration. A failure at the first Filter Manager call points to the driver environment or loading sequence, not to a later instance-attachment policy.

What to check

Confirm that the binary is installed and loaded as a file-system minifilter rather than as an ordinary kernel driver with an unrelated service configuration.
Separate this status from ERROR_FLT_FILTER_NOT_READY. The latter means registration succeeded but filtering has not started; this status means the Filter Manager itself was unavailable during registration.
Review the kernel event log and the driver service configuration for an earlier load or dependency failure. Do not attempt FltStartFiltering without a successful FltRegisterFilter result.
After the service starts successfully, fltmc filters can confirm whether the expected minifilter is registered in the running system.

References

Looking for a different code? Search another status or error code.