And it's worth noting that atkexComSvc.exe can't just be reinstalled like you would AiSuite, it's always bundled with their other softwares. It may be possible to disable this service, at your own risk. I don't know how vital it is but since it's currently being blocked from starting and isn't running in the background, it probably isn't needed for everyday use. However, if you use system monitoring programs or want to use ASUS motherboard firmware updating tools (such as the Intel ME tool that they released a few years ago) you may actually need this running.
Installing AiSuite in an attempt to get a new version of this exe is no solution for those who don't want the software at all, in case someone seriously suggests it. AiSuite is also notoriously hard to uninstall cleanly.
Just read this article from Danila T.
I called up support to verify, they are actually making me pay again to upgrade, considering its their upper tier subscription you would think we would have been given something, even if its the "lower" Standard tier
Kaspersky, you are already on thin ice with world politics, and some of your loyal customers you do have should not be abandoned this way.
I knew it. Today when perusing the Windows 10 reliability history, I saw that atkexComSvc.exe (a piece of software that is installed as a service when you install AiSuite or chipset drivers from an ASUS CD etc) had failed to launch at boot. The last database updates were done on the 9th-10th of this month, but I only noticed this issue now when the system was booted. I don't even have AiSuite or any other ASUS software installed (nor have I ever) except for this executable which must've come from the drivers CD, I don't know for sure since this PC was built and prepped by a store.
This file is needed by AiSuite and other ASUS software, so it's no wonder why they're malfunctioning now...
Пытаюсь поставить KESLinux 11.1.0-3013 на Suse Linux Enterprise Server 12 SP5. ОС предоставлена в качестве тестовой.
Продукт устанавливается из RPM, как и агент 11.0.1-19. Проходит без ошибок. Никаких ошибок и при при запуске скрипта настройки после установки. Из файла настроек скриптом после установки тоже пробовал брать настройки, в т.ч. с перекомпиляцией ядра.
Компьютер с продуктом отображается в KSC 13, видно все задачи и т.д. Секунд через дцать появляется статус "Защита выключена". Задача установки ключа ключ не устанавливает, он не отображается в консоли (хотя комадная строка показывает, что он активен). Из командной строки задача защиты тоже не запускается (ID 1).
Вопрос: что неправильно? Может статьи готовые есть по неработающей защите и вообще типичных проблемах с KESL?