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

Create a technical support case if you need further support.

Manually verifying if a necessary root certificate is missing in OfficeScan (OSCE)

    • Updated:
    • 13 Mar 2020
    • Product/Version:
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • N/A N/A
    • Windows 10
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2000 Advanced Server
    • Windows 2000 Professional
    • Windows 2000 Server
    • Windows 2003 32-Bit
    • Windows 2003 64-Bit
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server Core
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012
    • Windows 2012 Datacenter
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Server R2
    • Windows 2012 Standard
    • Windows 2012 Standard R2
    • Windows 2012 Web Server Edition
    • Windows 2016
    • Windows 2016 Server Core
    • Windows 2016 Server Datacenter
    • Windows 2016 Server Standard
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit

There have been a lot of cases for Windows (XP, 2003, 2008, etc.) platforms, wherein the OSCE agent is unable to update the scan engine or program to the latest version due to signature verification failure in a closed network.

Most of these cases are due to the Agent PC missing a necessary root certificate. This article demonstrates how to manually check if a root certificate is missing.

This solution uses the XP platform as an example.

To view certificates in the Microsoft Management Console (MMC) snap-in:

  1. Open a Command Prompt window.
  2. Type "MMC" and press the ENTER key.
    To view certificates in the local machine, you must be in the Administrator role.
  3. On the File menu, click Add/Remove Snap-In.
  4. Click Add.
  5. In the Add Standalone Snap-in dialog box, select Certificates.
  6. Click Add.
  7. In the Certificates snap-in dialog box, select the Computer account and click Next.
  8. In the Select Computer dialog box, click Finish.
  9. In the Add Standalone Snap-in dialog box, click Close.
  10. On the Add/Remove Snap-in dialog box, click OK.

    Optional. On the File menu, click Save or Save As. Save the console file to reuse later.

  11. Go to Console Root > Certificates > Trusted Root Certification Authorities > Certificates to view the installed certificates.

    Check certificate

To manually verify if a necessary root certificate is missing:

  1. On the problematic agent machine, manually check the digital signature of the problematic new version of a file (e.g. vsapint.sys) from File Properties. If you can’t find the new version binary for the engine (e.g. v9.9) in the client installation folder, you can go to the OSCE server’s shared folder and view the file using the following Server Message Block (SMB) path:


  2. Right-click the file and choose Properties.
  3. Go to the Digital Signatures tab and select the signature.
  4. Choose Details, then click View Certificate.
  5. Go to the Certificate Path tab and select the top certificate.
  6. Check the Certificate Status, which is shown in the lower panel.
    • Normal Situation (root certificate is NOT missing)

      Root Certificate

    • Problematic Situation (root certificate is missing)

      Root Certificate

      Root Certificate

    If you see the “The issuer of this certificate could not be found” message, this indicates that the certificate you have selected is missing from the PC and you need to manually import it.

Solution Id:
Did this article help you?

Thank you for your feedback!

*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.