labynko 3 Posted January 27 Share Posted January 27 Hello. In ESET PROTECT 10.0.14.0, when performing similar tasks, in one case the result is successful, and in the other case it is not. If you run these commands, the task will end with the Finished status: Quote taskkill /im HDhsfjkdfoiuqerhsd.exe taskkill /im IjnvejfdvhHfwfsdf.exe taskkill /im JHuwenNCsfwefwefs.exe taskkill /im UwerNnfsdfwefsdf.exe taskkill /im Wfwmekrdfwseew.exe If you run these commands, the task will end with the Failed status: Quote taskkill /im HDhs.exe taskkill /im Ijnv.exe taskkill /im JHuw.exe taskkill /im Uwer.exe taskkill /im Wfwm.exe The processes specified in the commands do not exist and can be absolutely anything. Computers running ESET Management Agent 10.0.1126.0. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,609 Posted January 27 Administrators Share Posted January 27 I assume that setting debug verbosity via agent's policy would enable logging more details in trace.log on the client which may be helpful for troubleshooting the issue. Quote Link to comment Share on other sites More sharing options...
labynko 3 Posted January 27 Author Share Posted January 27 I didn't know, but the tasks have a history, and there is detailed information there. The "trace message" column for the problematic task contains the following information: Quote Invalid utf8 leading byte Also, information about this error appears in the trace.log: Quote 2023-01-27 09:00:19 Error: CSystemConnectorModule [Thread 824]: Invalid utf8 leading byte Quote Link to comment Share on other sites More sharing options...
labynko 3 Posted January 27 Author Share Posted January 27 I didn't know, but the tasks have a history, and there is detailed information there. The "trace message" column for the problematic task contains the following information: Quote Invalid utf8 leading byte Also, information about this error appears in the trace.log: Quote 2023-01-27 09:00:19 Error: CSystemConnectorModule [Thread 824]: Invalid utf8 leading byte P.S. In ESET Management Agent 9.0.1141.0 the error does not appear. In ESET Management Agent 10.0.1126.0 the error appears. I have attached the agent log collected in trace mode with traceAll. trace.log Quote Link to comment Share on other sites More sharing options...
labynko 3 Posted March 4 Author Share Posted March 4 Performing even such a task as starting a service Quote sc start RemoteRegistry results in an error Quote Invalid utf8 leading byte Is there anything known about this issue? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.