Just started to test SEP 15, and installed it on my test machine using the default policy.
It identified a file, NTOSKRNL.EXE, with the following filehash:
5379732000000000000000000000000000000000000000000000000000000000
This hash is not correct, as using the powershell get-filehash command provides this instead:
C732B1DD3480285B6666641BC417A0C897884331229F47B055B79A9E42DF4282
Which is a known file on VT. Any idea why Symantec's hash calculation would be incorrect? Or what I should do next?