When opened, the file appears to only have metadata about itself and not the expected file contents.
<?xml version="1.0" encoding="UTF-16"?><!--GETRSFileHeaderSize=0x00000420--><GETEncryptedDataFile
version="x.x.x"><FileInformation><filename>D:\New Text Document.txt</filename><created>Tue, 23 Apr
2013 12:48:04 UT-0800</created></FileInformation><AlignmentLength>512</AlignmentLength><WrappedKeys
The root cause was determined to be an interaction between the SEE-RS legacy filter driver and another software's legacy filter driver (in this case McAfee HIPS). Microsoft has a detailed explanation of the findings in this case posted to the following page: http://blogs.msdn.com/b/ntdebugging/archive/2013/03/25/understanding-file-system-minifilter-and-legacy-filter-load-order.aspx
To put it simply, because of the way the windows filter-manager positioned the legacy filter drivers in relation to the newer "minifilter" drivers, data did not flow through the filter driver stack in the proper order. As a result SEE-RS did not function as expected.
Symantec was able to determine that use of a "null" or "dummy" legacy filter driver would force Windows filter-manager to split the filter stack frames so that data would flow through the filter-stack properly.
To determine if you are experiencing this issue:
If the altitude column is not in descending numerical order please contact SEE-RS support to investigate and determine the best solution.
Software that utilizes a legacy filter driver other than SEE-RS