Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

An issue preventing Trend Micro Products from starting successfully on machines running on Windows Server 2012 R2 and 2016

    • Updated:
    • 24 Jan 2018
    • Product/Version:
    • ScanMail for Exchange 12.5
    • Platform:
    • Windows 2012 Standard
Summary

Microsoft is aware of a new publicly disclosed class of vulnerabilities referred to as “speculative execution side-channel attacks” that affect many modern processors and operating systems including Intel, AMD, and ARM.

Microsoft has released several updates to help mitigate these vulnerabilities:

Currently, Trend Micro has identified that the following products’ service may fail to start after applying Widows Security Update KB4056895 and KB4056898 (available for Windows Server 2012 R2), and KB4056890 (available for Windows Server 2016):

ProductVersionLanguageOS
ScanMail for Microsoft Exchange12.5ENWindows Server 2012 R2
Windows Server 2016
Details
Public

SMEX 12.5 Master Service start failure is caused by the same known issue existing in these three Windows Security Updates.

This Microsoft known issue is resolved in KB4057401 (available for Windows Server 2012 R2) and KB4057142 (available for Windows Server 2016). To avoid ScanMail Master Service start failure, make sure to cover these two Windows Security Updates during deployment.

  • KB4056895 and KB4056898 (available for Windows Server 2012 R2)

    Known issues in this update:

    SymptomWorkaround
    When calling ColnitializeSecurity, the call fails if passing RPC_C_IMP_LEVEL_NONE under certain conditions.
    When calling ColnitializeSecurity, the call may fail when passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error message that's returned on the failure is: STATUS_BAD_IMPERSONATION_LEVEL.
    This issue is resolved in KB4057401.
  • KB4056890 (available for Windows Server 2016)

    Known issues in this update:

    SymptomWorkaround
    When calling ColnitializeSecurity, the call will fail when passing RPC_C_IMP_LEVEL_NONE under certain conditions.
    When calling ColnitializeSecurity, the call may fail when passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error returned on failure is STATUS_BAD_IMPERSONATION_LEVEL.
    This issue is resolved in KB4057142.

References:

January 3, 2018—KB4056890 (OS Build 14393.2007)

January 8, 2018—KB4056895 (Monthly Rollup)

January 3, 2018—KB4056898 (Security-only update)

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1119222
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.