mdkm

I can confirm that uninstalling Windhawk resolved the issue. Installed it again (with no plugins active) and the issue was there. Definitely the culprit was Widhawk. Than you very much. I will mark response above as correct solution.

Here are log logs collected with ESET Log Collector. Hope it will help. Nothing was logged in HIPS log. When I add adb.exe to HIPS exclusions it works. When I remove it from exception list it does not work. eav_logs.zip

Just adding final screenshot for future reference. HIPS On Deep Behavior Inspection ON adb.exe added to exclusion list

Yes, enabling HIPS Deep Behavior Inspection ON and adding adb.exe to exclusion list fixed the issue. I am adding 2 screenshots that shows that disabling HIPS helped. The best option is to add app it to exclusion list. Just would like to point out that showing notification when HIPS prevent an app from running would be VERY helpful.

HIPS was in automatic mode with no custom rules created. Restoring HIPS and disabling only Deep Behavior Inspection fix the problem.

No Crowdstrike installed

Hi all, just opened account here to share my experience and many hours wasted trying to figure out why command prompt programs (like adb.exe) would simply not work through command prompt, terminal, powershell (elevated or not) on Windows 11. For example typing adb.exe (in command promt opened in folder where Google platform tools where extracted) would give no output at all. Checking Application logs gave me "generic" error: Faulting application name: adb.exe, version: 0.0.0.0, time stamp: 0xbd7c0bf9 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x75591412 Faulting process id: 0x0x1270 Faulting application start time: 0x0x1DA76B7F8BE4DA2 Faulting application path: E:\adbV35\adb.exe Faulting module path: unknown Report Id: 77bc79dc-ab8a-4666-be66-d9edf2e37570 Faulting package full name: Faulting package-relative application ID: Tried everything online. Nothing helped. The system was ok but it seemed like something was preventing program from running. Today I revisited the problem for the nth time. Disabled NOD32 (again) nothing happened. Disabled Host Intrusion Prevention System (HIPS), restarted computer, tried adb and voila - it worked. Checking HIPS log in Nod32 showed no trace of Nod blocking adb.exe form running but disabling HIPS definitely helped. It would be awesome if Nod would notify user when prevented app from running and I hope they will. Now, I am not comfortable leaving HIPS disabled hence opening this thread hoping to find consensus on best setting to prevent silent stopping of program execution prevention and also have programs work when you start them. Also this is for all the people trying to find out why all of the sudden programs stopped working. Please note this was not a problem with adb.exe only but with many command line tools as well. I will continue to explore this and edit OP with findings. Important note: this is not a suggestion to disable HIPS. I do not think HIPS should be disabled. It is a useful tool but it should be more informative when preventing an action.