| Previous | Next |
| ERROR_FLT_FILTER_NOT_FOUND | ERROR_FLT_INSTANCE_NOT_FOUND |
ERROR_FLT_VOLUME_NOT_FOUND
The named volume is absent from Filter Manager's active list
ERROR_FLT_VOLUME_NOT_FOUND is returned when FltGetVolumeFromName cannot find a matching volume in Filter Manager's global volume list. The API accepts several native and DOS-style volume name formats, but a familiar drive letter does not guarantee that the requested name currently identifies an attached, accessible Filter Manager volume.
The result can be caused by a name mismatch, a volume that is not mounted, a volume that has already been dismounted, or a target outside the expected file-system volume model. It is not interchangeable with an access-denied result, which means a matching volume was found but the caller lacked the required read access.
What to check
- Obtain the canonical volume name with the relevant Filter Manager APIs rather than constructing a native name from a drive letter or a cached mount-point mapping.
- Check whether the volume was recently mounted, dismounted, or replaced. Do not retain a stale name across storage topology changes.
- Query from an appropriate execution context:
FltGetVolumeFromNameruns atPASSIVE_LEVELand opens the volume while resolving it. - Release the returned volume object with
FltObjectDereferenceafter a successful lookup so that teardown is not held up by an unnecessary reference.
References
- Microsoft: FltGetVolumeFromName
- Microsoft: FltGetVolumeGuidName
- OSR: Filter Manager volume and instance abstractions
Looking for a different code? Search another status or error code.