| 0x001F0001 | The IO was completed by a filter. |
The IO was completed by a filter. |
| 0x801F0001 | A handler was not defined by the filter for this operation. |
A handler was not defined by the filter for this operation. |
| 0x801F0002 | A context is already defined for this object. |
A context is already defined for this object. |
| 0x801F0003 | Asynchronous requests are not valid for this operation. |
Asynchronous requests are not valid for this operation. |
| 0x801F0004 | Disallow the Fast IO path for this operation. |
Disallow the Fast IO path for this operation. |
| 0x801F0005 | An invalid name request was made. The name requested cannot be retrieved at this time. |
An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0x801F0006 | Posting this operation to a worker thread for further processing is not safeat this time because it could lead to a system deadlock. |
Posting this operation to a worker thread for further processing is not safeat this time because it could lead to a system deadlock. |
| 0x801F0007 | The Filter Manager was not initialized when a filter tried to register. Makesure that the Filter Manager is getting loaded as a driver. |
The Filter Manager was not initialized when a filter tried to register. Makesure that the Filter Manager is getting loaded as a driver. |
| 0x801F0008 | The filter is not ready for attachment to volumes because it has not finishedinitializing (FltStartFiltering has not been called). |
The filter is not ready for attachment to volumes because it has not finishedinitializing (FltStartFiltering has not been called). |
| 0x801F0009 | The filter must cleanup any operation specific context at this time becauseit is being removed from the system before the operation is completed bythe lower drivers. |
The filter must cleanup any operation specific context at this time becauseit is being removed from the system before the operation is completed bythe lower drivers. |
| 0x801F000A | The Filter Manager had an internal error from which it cannot recover,therefore the operation has been failed. This is usually the resultof a filter returning an invalid value from a pre-operation callback. |
The Filter Manager had an internal error from which it cannot recover,therefore the operation has been failed. This is usually the resultof a filter returning an invalid value from a pre-operation callback. |
| 0x801F000B | The object specified for this action is in the process of beingdeleted, therefore the action requested cannot be completed atthis time. |
The object specified for this action is in the process of beingdeleted, therefore the action requested cannot be completed atthis time. |
| 0x801F000C | Non-paged pool must be used for this type of context. |
Non-paged pool must be used for this type of context. |
| 0x801F000D | A duplicate handler definition has been provided for an operation. |
A duplicate handler definition has been provided for an operation. |
| 0x801F000E | The callback data queue has been disabled. |
The callback data queue has been disabled. |
| 0x801F000F | Do not attach the filter to the volume at this time. |
Do not attach the filter to the volume at this time. |
| 0x801F0010 | Do not detach the filter from the volume at this time. |
Do not detach the filter from the volume at this time. |
| 0x801F0011 | An instance already exists at this altitude on the volume specified. |
An instance already exists at this altitude on the volume specified. |
| 0x801F0012 | An instance already exists with this name on the volume specified. |
An instance already exists with this name on the volume specified. |
| 0x801F0013 | The system could not find the filter specified. |
The system could not find the filter specified. |
| 0x801F0014 | The system could not find the volume specified. |
The system could not find the volume specified. |
| 0x801F0015 | The system could not find the instance specified. |
The system could not find the instance specified. |
| 0x801F0016 | No registered context allocation definition was found for the given request. |
No registered context allocation definition was found for the given request. |
| 0x801F0017 | An invalid parameter was specified during context registration. |
An invalid parameter was specified during context registration. |
| 0x801F0018 | The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0x801F0019 | The requested device object does not exist for the given volume. |
The requested device object does not exist for the given volume. |
| 0x801F001A | The specified volume is already mounted. |
The specified volume is already mounted. |
| 0x801F0020 | No waiter is present for the filter's reply to this message. |
No waiter is present for the filter's reply to this message. |