Attempting to scan some .mht files results in a virus detection due to a malformed container violation.
This issue currently only appears to affect .mht files created with Windows Problem Steps Recorder(WPSR).
Some *.mht fies which are not compliant with RFC 822 and/or RFC 2046-defined MIME format specification can trigger malformed container errors (structure mismatch). In such a case, this behavior is by design.
If you wish to allow malformed container files do as follows.
To configure Symantec Protection Engine to allow malformed container files: