3/27/2023 0 Comments Codemeter webadmin![]() ![]() As long as this driver is available on the system, the CodeMeter service cannot be started and therefore the protected software cannot be used. So there is a driver on the system that is used to either attack protected software or to use cracked software. Specifically, the driver component is C: \ Windows \ SysNative \ drivers \ multikey.sys, which we have classified as very suspicious. ![]() These struck here now and prevented the start of CodeMeter. Since we protect our customers' software and our own against such attacks, there are various protection mechanisms, among others. After analyzing the log file by development, the cause could be found, which is why the CodeMeter service could not be started.Ī core driver was identified on the system that can be used for reverse engineering CodeMeter. Thanks for the quick response and the LicenseLocks data. Then we can analyze which process is causing the problem here. Since there are so many of the log files here, can be assumed that by default such a process is running, which will probably also bring code meters to a regular end.Ĭould you send me 1-2 of these LicenseLocks (C: \ ProgramData \ CodeMeter \ Logs) via following ShareFile Link: ), please? certain processes are running (kernel debugger, USB emulators, debugger) or because an attempt is being made to debug the application. LicenseLocks are written when CodeMeter or the protected application terminates itself because e.g. I get the answer from development, What immediately stands out here is the extreme amount of LicenseLock files: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |