| Previous | Next |
| ERROR_FLT_INSTANCE_NAME_COLLISION | ERROR_FLT_VOLUME_NOT_FOUND |
ERROR_FLT_FILTER_NOT_FOUND
The lookup target is a registered filter, not a filesystem file
ERROR_FLT_FILTER_NOT_FOUND is returned by FltGetFilterFromName when no registered minifilter driver matches the supplied name. The comparison is case-insensitive, and a successful lookup produces an opaque filter object with a rundown reference. This status is therefore about Filter Manager registration state, not about a missing driver file on disk.
Common causes include querying before the target driver has registered, using a service or display name that differs from the minifilter registration name, or looking up a filter while it is being unloaded. The last case can instead surface a deleting-object status, so lifecycle timing matters.
What to check
- Use
fltmc filtersto identify the name that Filter Manager currently exposes, then compare it with the exact name passed toFltGetFilterFromName. - Confirm that the target is a minifilter that completed
FltRegisterFilter, not merely a service whose binary exists or a legacy filesystem filter. - Coordinate startup order if one minifilter depends on another. A retry is meaningful only after the required filter has registered.
- After a successful lookup, balance the acquired rundown reference with
FltObjectDereference; holding it can delay teardown.
References
Looking for a different code? Search another status or error code.