fltlib.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x1f0001 | 78.11011 | The IO was completed by a filter. |
| 0x801f0001 | 78.11011 | A handler was not defined by the filter for this operation. |
| 0x801f0002 | 78.11011 | A context is already defined for this object. |
| 0x801f0003 | 78.11011 | Asynchronous requests are not valid for this operation. |
| 0x801f0004 | 78.11011 | Disallow the Fast IO path for this operation. |
| 0x801f0005 | 78.11011 | An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0x801f0006 | 78.11011 | Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0x801f0007 | 78.11011 | The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0x801f0008 | 78.11011 | The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0x801f0009 | 78.11011 | The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers. |
| 0x801f000a | 78.11011 | The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback. |
| 0x801f000b | 78.11011 | The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0x801f000c | 78.11011 | Non-paged pool must be used for this type of context. |
| 0x801f000d | 78.11011 | A duplicate handler definition has been provided for an operation. |
| 0x801f000e | 78.11011 | The callback data queue has been disabled. |
| 0x801f000f | 78.11011 | Do not attach the filter to the volume at this time. |
| 0x801f0010 | 78.11011 | Do not detach the filter from the volume at this time. |
| 0x801f0011 | 78.11011 | An instance already exists at this altitude on the volume specified. |
| 0x801f0012 | 78.11011 | An instance already exists with this name on the volume specified. |
| 0x801f0013 | 78.11011 | The system could not find the filter specified. |
| 0x801f0014 | 78.11011 | The system could not find the volume specified. |
| 0x801f0015 | 78.11011 | The system could not find the instance specified. |
| 0x801f0016 | 78.11011 | No registered context allocation definition was found for the given request. |
| 0x801f0017 | 78.11011 | An invalid parameter was specified during context registration. |
| 0x801f0018 | 78.11011 | The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0x801f0019 | 78.11011 | The requested device object does not exist for the given volume. |
| 0x801f001a | 78.11011 | The specified volume is already mounted. |
| 0x801f0020 | 78.11011 | No waiter is present for the filter's reply to this message. |
| 28 entries | ||