The document is archived and information here might be outdated
Incompatible Filter Driver Errors
Updated: April 21, 2010
Applies To: System Center Data Protection Manager 2010
The following table provides troubleshooting guidance for incompatible filter errors.
Data Protection Issues
If the WIM FS Filter driver (Wimfltr.sys) is installed on the protected server, an incompatible filter error occurs.
Perform the following steps to continue protection.
On the protected server, browse to the registry path HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agents\2.0.
Add wimfltr to the ExcludedFilters value, which contains the luafv value.
Restart the DPMRA service on the protected server.
On the DPM server, run a consistency check, and then run a synchronization job.
DPM is unable to continue protection for data sources on the protected server because it has detected an incompatible filter.
Perform the following steps to continue protection:
On the protected server, browse to the application event log to check for events from the DPMRA service that indicate the name of the incompatible filter.
If there are no incompatible filters listed in the event log, check to see if any file system filters were recently installed on the protected server.
After you identify the incompatible filter, we recommend that you uninstall the filter.
If you do not want to uninstall the incompatible filter, DPM can protect the data using a consistency check mechanism instead of volume filter tracking. This will degradate performance; however, you will be able to continue protection.
Perform the steps in the following procedure to protect the data using the consistency check mechanism.
On the protected server, browse to the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0.
Create a DWORD registry value named ForceFixup and set it to 1.