> Source: [sk113333](https://support.checkpoint.com/results/sk/sk113333)

# sk113333 - Errors during Threat Emulation update 

| Property | Value |
|----------|-------|
| Solution ID | sk113333 |
| Date Created | 2016-09-13 |
| Last Modified | 2020-02-04 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Threat Emulation engine update (or any Threat Emulation updateable component) download fails with "`Threat Emulation update failed, cannot download <Name_of_Component>. Failed running download process.`" log in SmartLog / SmartView Tracker.

  *Example* :  
  [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk113333/LogDetails1609130630.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk113333/LogDetails1609130630.png "Click the image to see it in full size in a new tab/window")
* "`Error: Threat Emulation update failed, cannot download JAVA. Failed running download process.`" status appears for Threat Emulation blade in SmartView Monitor.

  *Example* :  
  [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk113333/SmartView Monitor1609130638.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk113333/SmartView Monitor1609130638.png "Click the image to see it in full size in a new tab/window")
* The `$FWDIR/log/te_file_downloader.elg` file shows:

  ```
  
  [ERROR] http_client_get: Operation failed. curl returned:Errorcode=35. Error String:SSL connect error
  Error Buffer=<NULL>
  [ERROR] FDT_get_data: Failed to get data (curl error: -1) from https://updates.checkpoint.com/WebService/services/DownloadMetaDataService 
  [TE (TD::All)] file_DataCB: ==> status: 2
  [TE (TD::Critical)] file_DataCB: Got bad FDT status 2
  [TE (TD::Critical)] get_file: Failed getting data from FDT for product (te_image), error: General Error
  [NOTICE] http_client_destroy: Free HttpClient memory - Done.
  [TE (TD::Critical)] main_te_fileDownloader: failed getting file
   
  ```

## Cause

Check Point Update Center*updates.checkpoint.com* has moved to SHA-256 based certificates (refer to [sk103839](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk103839)).  
However, the version of Threat Emulation engine that is used does not support SHA-256 based certificates.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R77.30 Gaia OS](http://supportcontent.checkpoint.com/solutions?id=sk104859#Gaia Downloads) - released on 16 Dec 2016
* [Threat Emulation Offline update](http://supportcontent.checkpoint.com/solutions?id=sk92509) Slim Package - *version 46189 (46.990000189) and above*
* [Jumbo Hotfix Accumulator for R77.30](http://supportcontent.checkpoint.com/solutions?id=sk106162) - since *Take_184*

**Related solutions:**

* [sk95235: Threat Emulation Engine Update - What's New?](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk95235)
* [sk92509: Offline updates for Threat Emulation images and engine](http://supportcontent.checkpoint.com/solutions?id=sk92509)

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
