Return to Question

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger along with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

Debuggers that I use:

• Visual Studio 2019 (works but everything else freeze)
• x64dbg (works but everything else freeze)
• Windbg (freezes along with everything)
• IDA Pro (freezes along with everything).

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger along with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

Debuggers that I use:

• Visual Studio 2019 (works but everything else freeze)
• x64dbg (works but everything else freeze)
• Windbg (freezes along with the rest)
• IDA Pro (freezes along with the rest).

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger along with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

Debuggers that I use: Visual Studio 2019, x64dbg, IDA Pro.

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger along with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

Debuggers that I use:

• Visual Studio 2019 (works but everything else freeze)
• x64dbg (works but everything else freeze)
• Windbg (freezes along with everything)
• IDA Pro (freezes along with everything).

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

I'm trying to "trace" (just setting breakpoint, step in, step over to know how certain things work) an application. But if the application enters suspended state by using breakpoint, every things on the screen are unresponsive, I can't click anything on the taskbar to switch to another application, I can't even press Alt+Tab to switch app. The only thing still working is the debugger.

Windbg is the worst case that it isn't even react to my mouse click when a breakpoint is hit, I have to use Task Manager to terminate the debugger along with the target app.

So, it's maybe some kind of anti-debugging technique? Does anyone know about this?

Debuggers that I use: Visual Studio 2019, x64dbg, IDA Pro.