DRIVER KERNEL INTERFERE WITH ATTACH in x64dbg

[nexs324534]

hi i have been using pyark for now 2 weeks and its the best ark i have been using for now nice features it keep active very nice but the best things its the debug engine im using it with x64dbg and it work very very well but do you think u can fix these problem with protected process with kernel driver when im tryin to attach to the protected process? here a photo

[antiwar3]

I haven't seen this prompt before. Did x64dbg itself give this prompt? My tool only handles most anti-debugging related issues.

[nexs324534]

x64dbg itself give this prompt? yes when attaching ON a exe protected with a driver , its a callbacks detection i think idk if its possible to bypass it? obregistercallback i think

[nexs324534]

Could you also do something please? Can we change the driver name? I think it would be better because your driver is blacklisted in some games. I also want to use your debugger because honestly it's the best one I've found so far and I hope there will be more updates, especially for the debugging features. Also, could you add support for exception-based anti-debug protections like VEH/SEH? Sometimes when attaching to a process, an exception gets triggered immediately and makes debugging difficult. It would be really useful if the debugger could handle those cases better. I also have another issue with x64dbg on some protected games that use kernel drivers with ObRegisterCallbacks. A popup appears and it prevents attaching to the process. If possible, it would be nice if there could be a fix or better compatibility for those situations. I know I'm asking for a lot, but I'm asking respectfully. If you don't want to, it's completely okay.