File Screening Metadata Integrity
Applies To: Windows Server 2008
To enforce file screening, the file screening minifilter driver uses configuration information that is stored in a metadata file. If there is a problem with this metadata file, the file screening minifilter driver cannot attach to the volume, and users might be able to save unauthorized files.
Events
| Event ID | Source | Message |
|---|---|---|
datascrn |
The screening minifilter driver failed to attach to volume "%2 (%5)" because the minifilter metadata on the volume is the wrong version (version 0x%3 when version 0x%4 was expected). This is most likely caused by a driver upgrade followed by a restore of old metadata or by a metadata corruption. While the driver is detached file screening enforcement and management will be unavailable on the volume. Try to reinstall the driver or restore a newer version of your file screening configuration metadata. | |
datascrn |
The screening minifilter driver failed to attach to volume "%2 (%3)" because the minifilter metadata on the volume is corrupt. While the minifilter is detached file screening enforcement and management will be unavailable on the volume. Attempt to restore the screening configuration metadata for this volume from backup. | |
datascrn |
An unexpected error occurred while deleting metadata entry for directory "%4" on volume "%2 (%5)". Error status: %3 This may have resulted in incorrect file screening configuration. It is recommended that you review the file screening configuration on the volume for misconfigured or orphan entries using the management tools. | |
datascrn |
An unexpected error occurred while renaming metadata entry for directory "%4" on volume "%2 (%5)". Error status: %3 This may have resulted in incorrect file screening configuration or a blocked file being stored. It is recommended that you review the file screening configuration on the volume for misconfigured or missing entries using the management tools. | |
datascrn |
The screening minifilter driver detected and deleted an invalid screening configuration record on volume "%2 (%3)". The minifilter was unable to determine what directory was affected. You can either restore the file screen configuration for the volume from backup or use the management tools to review the configuration and reconfigure any missing entries. |