So I also have these Intel services for which I don't know the whole purpose:
-Intel Capability Licensing Service Interface
-Intel Dynamic Application Loader Host Interface Service
-Intel Management and Security Application Local Management Service
-Intel Managementand Security Application User Notification Service
I also observe that in the folder with HeciServer.exe that is in c:\Program Files\Intel\iCLS Client\ there are also iclsClient.dll and iclsProxy.dll but also openssl libraries and certificates, so obviously at least Intel's HeciServer phones home.
Even stranger, all these services add immense amount of additional entries in PATH, because there are 32 and64 bit versions and they need all every folder thaey use (and they use a lot) in the PATH. Which also means that they somehow don't know what they are doing as with manifests they wouldn't need PATH entries for DLLs at all. And I can't imagine that one service invoke command line for another one.
-Intel Capability Licensing Service Interface
-Intel Dynamic Application Loader Host Interface Service
-Intel Management and Security Application Local Management Service
-Intel Managementand Security Application User Notification Service
I also observe that in the folder with HeciServer.exe that is in c:\Program Files\Intel\iCLS Client\ there are also iclsClient.dll and iclsProxy.dll but also openssl libraries and certificates, so obviously at least Intel's HeciServer phones home.
Even stranger, all these services add immense amount of additional entries in PATH, because there are 32 and64 bit versions and they need all every folder thaey use (and they use a lot) in the PATH. Which also means that they somehow don't know what they are doing as with manifests they wouldn't need PATH entries for DLLs at all. And I can't imagine that one service invoke command line for another one.
Intel made a lot of mess now.