This is page contains raw error codes. It is meant as a software developer reference, not a customer support site.
| Code | HRESULT | Description | #define |
|---|---|---|---|
| 1 | 0x001F0001 | The IO was completed by a filter. | ERROR_FLT_IO_COMPLETE |
| 1 | 0x801F0001 | A handler was not defined by the filter for this operation. | ERROR_FLT_NO_HANDLER_DEFINED |
| 1 | 0x001F0001 | The IO was completed by a filter. | ERROR_FLT_IO_COMPLETE |
| 1 | 0x801F0001 | A handler was not defined by the filter for this operation. | ERROR_FLT_NO_HANDLER_DEFINED |
| 2 | 0x801F0002 | A context is already defined for this object. | ERROR_FLT_CONTEXT_ALREADY_DEFINED |
| 3 | 0x801F0003 | Asynchronous requests are not valid for this operation. | ERROR_FLT_INVALID_ASYNCHRONOUS_REQUEST |
| 4 | 0x801F0004 | Disallow the Fast IO path for this operation. | ERROR_FLT_DISALLOW_FAST_IO |
| 5 | 0x801F0005 | An invalid name request was made. The name requested cannot be retrieved at this time. | ERROR_FLT_INVALID_NAME_REQUEST |
| 6 | 0x801F0006 | Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. | ERROR_FLT_NOT_SAFE_TO_POST_OPERATION |
| 7 | 0x801F0007 | The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. | ERROR_FLT_NOT_INITIALIZED |
| 8 | 0x801F0008 | The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). | ERROR_FLT_FILTER_NOT_READY |
| 9 | 0x801F0009 | 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. | ERROR_FLT_POST_OPERATION_CLEANUP |
| 10 | 0x801F000A | 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. | ERROR_FLT_INTERNAL_ERROR |
| 11 | 0x801F000B | The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. | ERROR_FLT_DELETING_OBJECT |
| 12 | 0x801F000C | Non-paged pool must be used for this type of context. | ERROR_FLT_MUST_BE_NONPAGED_POOL |
| 13 | 0x801F000D | A duplicate handler definition has been provided for an operation. | ERROR_FLT_DUPLICATE_ENTRY |
| 14 | 0x801F000E | The callback data queue has been disabled. | ERROR_FLT_CBDQ_DISABLED |
| 15 | 0x801F000F | Do not attach the filter to the volume at this time. | ERROR_FLT_DO_NOT_ATTACH |
| 16 | 0x801F0010 | Do not detach the filter from the volume at this time. | ERROR_FLT_DO_NOT_DETACH |
| 17 | 0x801F0011 | An instance already exists at this altitude on the volume specified. | ERROR_FLT_INSTANCE_ALTITUDE_COLLISION |
| 18 | 0x801F0012 | An instance already exists with this name on the volume specified. | ERROR_FLT_INSTANCE_NAME_COLLISION |
| 19 | 0x801F0013 | The system could not find the filter specified. | ERROR_FLT_FILTER_NOT_FOUND |
| 20 | 0x801F0014 | The system could not find the volume specified. | ERROR_FLT_VOLUME_NOT_FOUND |
| 21 | 0x801F0015 | The system could not find the instance specified. | ERROR_FLT_INSTANCE_NOT_FOUND |
| 22 | 0x801F0016 | No registered context allocation definition was found for the given request. | ERROR_FLT_CONTEXT_ALLOCATION_NOT_FOUND |
| 23 | 0x801F0017 | An invalid parameter was specified during context registration. | ERROR_FLT_INVALID_CONTEXT_REGISTRATION |
| 24 | 0x801F0018 | The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. | ERROR_FLT_NAME_CACHE_MISS |
| 25 | 0x801F0019 | The requested device object does not exist for the given volume. | ERROR_FLT_NO_DEVICE_OBJECT |
| 26 | 0x801F001A | The specified volume is already mounted. | ERROR_FLT_VOLUME_ALREADY_MOUNTED |
| 27 | 0x801F001B | The specified Transaction Context is already enlisted in a transaction | ERROR_FLT_ALREADY_ENLISTED |
| 28 | 0x801F001C | The specifiec context is already attached to another object | ERROR_FLT_CONTEXT_ALREADY_LINKED |
| 32 | 0x801F0020 | No waiter is present for the filter's reply to this message. | ERROR_FLT_NO_WAITER_FOR_REPLY |
| 35 | 0x801F0023 | The filesystem database resource is in use. Registration cannot complete at this time. | ERROR_FLT_REGISTRATION_BUSY |
No comments:
Post a Comment