FACILITY_USERMODE_FILTER_MANAGER: the user mode filter manager.
The source of the error code is the user mode filter manager.[1][2]
0x001F0001: The IO was completed by a filter.[3]0x801F0001: A handler was not defined by the filter for this operation.[3]0x801F0002: A context is already defined for this object.[3]0x801F0003: Asynchronous requests are not valid for this operation.[3]0x801F0004: Disallow the Fast IO path for this operation.[3]0x801F0005: An invalid name request was made. The name requested cannot be retrieved at this time.[3]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.[3]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.[3]0x801F0008: The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).[3]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.[3]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.[3]0x801F000B: The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.[3]0x801F000C: Non-paged pool must be used for this type of context.[3]0x801F000D: A duplicate handler definition has been provided for an operation.[3]0x801F000E: The callback data queue has been disabled.[3]0x801F000F: Do not attach the filter to the volume at this time.[3]0x801F0010: Do not detach the filter from the volume at this time.[3]0x801F0011: An instance already exists at this altitude on the volume specified.[3]0x801F0012: An instance already exists with this name on the volume specified.[3]0x801F0013: The system could not find the filter specified.[3]0x801F0014: The system could not find the volume specified.[3]0x801F0015: The system could not find the instance specified.[3]0x801F0016: No registered context allocation definition was found for the given request.[3]0x801F0017: An invalid parameter was specified during context registration.[3]0x801F0018: The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.[3]0x801F0019: The requested device object does not exist for the given volume.[3]0x801F001A: The specified volume is already mounted.[3]0x801F0020: No waiter is present for the filter's reply to this message.[3]0x001F0001: The IO was completed by a filter.[2]0x801F0001: A handler was not defined by the filter for this operation.[2]0x801F0002: A context is already defined for this object.[2]0x801F0003: Asynchronous requests are not valid for this operation.[2]0x801F0004: Disallow the Fast IO path for this operation.[2]0x801F0005: An invalid name request was made. The name requested cannot be retrieved at this time.[2]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.[2]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.[2]0x801F0008: The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).[2]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.[2]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.[2]0x801F000B: The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.[2]0x801F000C: Non-paged pool must be used for this type of context.[2]0x801F000D: A duplicate handler definition has been provided for an operation.[2]0x801F000E: The callback data queue has been disabled.[2]0x801F000F: Do not attach the filter to the volume at this time.[2]0x801F0010: Do not detach the filter from the volume at this time.[2]0x801F0011: An instance already exists at this altitude on the volume specified.[2]0x801F0012: An instance already exists with this name on the volume specified.[2]0x801F0013: The system could not find the filter specified.[2]0x801F0014: The system could not find the volume specified.[2]0x801F0015: The system could not find the instance specified.[2]0x801F0016: No registered context allocation definition was found for the given request.[2]0x801F0017: An invalid parameter was specified during context registration.[2]0x801F0018: The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.[2]0x801F0019: The requested device object does not exist for the given volume.[2]0x801F001A: The specified volume is already mounted.[2]0x801F001B: The specified Transaction Context is already enlisted in a transaction[2]0x801F001C: The specifiec context is already attached to another object[2]0x801F0020: No waiter is present for the filter's reply to this message.[2]0x801F0023: The filesystem database resource is in use. Registration cannot complete at this time.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0
- fltWinError.h from Windows SDK 10.0.14393.0