Recognize Interoperability Problems as a Fact of Life

The first step to solving a problem is recognizing that it exists.  We’ve just covered this.  There will always be interoperability problems.  These problems are not (usually) the result of bad design or engineering within FESF.  They aren’t even usually the result of bad design or engineering of the product with which FESF is attempting to interoperate.  Interoperability problems are simply an inherent part of creating File System Isolation Minifilters.  Therefore, you should do what you can to set your customers’ expectations appropriately.

Also, keep in mind that when customers report “everything was working until I installed your product”, it does not necessarily mean that there’s a problem in FESF.  It is at least equally likely that some other product (the customer’s antivirus or cloud filter or online backup program) is the component that’s failing.  Your support teams might consider explaining this to customers.

Recommended Strategy: Establish customer expectations that interoperability problems may occur.  When you DO have an interoperability issue, get us the bug report as soon as you can along with all the data that you can provide.