Application path for ccSvcHst.exe
Article ID: 203046
Updated On:
Products
Issue/Introduction
What is the application path for ccSvcHst.exe?
Environment
SEP 12.x, 14.x, 15
Resolution
- C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\<version string>\Bin64
- C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\<version string>\Bin
For example, if * is a wildcard, you could put in:
C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\*\Bin64
C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\*\Bin
The difficulty in exact versions is the build number at the very end. For example, there are two 14.3.558 versions. Here is one example, and note the .105 at the very end:
C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.3.558.0000.105\Bin
Here is a KB that covers the full version numbers for 14 version releases. You can match up what you have and tie in the version into the path. Note that 14.3 should be:
14.x - https://knowledge.broadcom.com/external/article/154575/
12.x - Here is a table with the versions:
| Name | Version/Build | Release Date (General Availability) |
|---|---|---|
| 12.1.6 MP10 (12.1 RU6 MP10) | 12.1.7454.7000 | November 26, 2018 |
| 12.1.6 MP10 (12.1 RU6 MP10) | 12.1.7445.7000 | March 30, 2018 |
| 12.1.6 MP9b | 12.1.7385.6902 | January 23, 2018 (Patch to fix MP9a.) |
| 12.1.6 MP9a | 12.1.7384.6902 | January 17, 2018 (Patch for cosmetic issue obsoleted by Microsoft patch on January 18) |
| 12.1.6 MP9 (12.1 RU6 MP9) | 12.1.7369.6900 | October 25, 2017 |
| 12.1.6 MP8 (12.1 RU6 MP8) | 12.1.7266.6800 | June 2, 2017 |
| 12.1.6 MP7 (12.1 RU6 MP7) | 12.1.7166.6700 | January 31, 2017 |
| 12.1.6 MP6 (12.1 RU6 MP6) | 12.1.7061.6600 | September 16, 2016 |
| 12.1.6 MP5 (12.1 RU6 MP5) SEPM, Windows, Linux client only) |
12.1.7004.6500 | June 24, 2016 |
| 12.1.6 MP4 (12.1 RU6 MP4) | 12.1.6867.6400 | March 15, 2016 |
| 12.1.6 MP3 (12.1 RU6 MP3) SEPM, Windows, Linux client only) |
12.1.6608.6300 | November 4, 2015 |
| 12.1.6 MP2 (12.1 RU6 MP2) SEPM and Mac client only) |
12.1.6465.6200 | October 1, 2015 |
| 12.1.6 MP1a (12.1 RU6 MP1a) (SEPM and Windows client only) |
12.1.6318.6100 | August 2015 |
| 12.1.6 MP1 (12.1 RU6 MP1) (SEPM and Windows client only) |
12.1.6306.6100 | July 2015 |
| 12.1.6 (12.1 RU6) | 12.1.6168.6000 | June 1, 2015 |
| 12.1.5 (12.1 RU5) | 12.1.5337.5000 | September, 2014 |
| 12.1.4 MP1b (12.1 RU4 MP1b (EE SEP client only) |
12.1.4112.4156 | August, 2014 |
| 12.1.4 MP1a (12.1 RU4 MP1a) (SEPM only) |
12.1.4104.4130 | April, 2014 |
| 12.1.4 MP1 (12.1 RU4 MP1) | 12.1.4100.4126 | April, 2014 |
| 12.1.4a (12.1 RU4a) (SEPM only) |
12.1.4023.4080 | February, 2014 |
| 12.1.4 (12.1 RU4) | 12.1.4013.4013 | October, 2013 |
| 12.1.3 (12.1 RU3) | 12.1.3001.165 | June, 2013 |
| 12.1.2 MP1 (12.1 RU2 MP1) | 12.1.2100.2093 | April, 2013 |
| 12.1.2 (12.1 RU2) | 12.1.2015.2015 | November, 2012 |
| 12.1.1 MP1 (12.1 RU1 MP1) | 12.1.1101.401 | May, 2012 |
| 12.1.1 (12.1 RU1) | 12.1.1000.157 | November, 2011 |
| 12.1 RTM | 12.1.671.4971 | July, 2011 |
You may want to verify the full path on a few by looking at an installed client to make sure an extra build number isn't added.
Feedback
