2023/7/27
As per the recent announcement, our driver is similar to ProcessHacker's and Windows automatically blocks ProcessHacker's driver upon launch.
For this reason, we've temporarily disabled Echo's kernel functionality until further notice.
What this means for Custom Strings?
This means our Custom String's capability won't be able to scan protected processes such as lsass.exe, Msmpeng.exe, csrss.exe or Sgrmbroker.exe.
All other non-protected processes should scan perfectly fine.
Keep them in your string builder! They'll be ignored for now, but very soon it'll be back to normal functionality.
What this means for Echo's OP detections?
Not much, contrary to popular belief, only a small minority of detections require kernel-level access. This will not affect any major cheat detections, and we have prepared backup methods
How long will this last?
Not long at all (expected within the next 2 weeks), our new driver is almost complete, we've just got a few final checks to run through. The new driver has increased validation and a powerful authentication system to ensure that only we can use the driver file. This will begin effect at 12pm London Time.
New update regarding the above, good news and bad news.
Good news
We've expedited a massive part of the process in getting the new driver ready, could arrive in the next few days (awaiting Microsoft verification).
Bad news
Some antiviruses appear to be instantly killing Echo midway through the scan, this is because it's no-longer protected by the kernel driver. I believe it's due to one of our scanners, we're currently investigating the exact cause. For now, up until the new driver, you may need to exclude from some antiviruses.
