Windows10 10586 enterprise 64bit
x64dbg v25 compiled on: Dec 1 2016, 22:29:29
Reproduce the problem:
Same situation, loading a x32 executable with ScyllaHide (updated Nt*.ini) simply throws me a loop of ACCESS_DENIED into the log and if you try to close it just crashes.
Simply, seems there're some problems with Win 10.
If you rename the plugins folder (therefore disabling plugins) you'll be able to debug without any problem.
There's a plugin who's giving problems, not sure but MAY be Scylla.
DBG: limit the maximum amount of exception to be skippable (resolves #…
should no longer hang now.
It still hang. How could i reopen this issue?@mrexodia
Reproduced on Win 8.1 Pro x64 with build 2017-02-05 using the ScyllaHide Themida x86 profile and only adding Exception 0xC0000096 to the Exception-list (otherwise the unpackme won't run properly --> anti-debugging); after closing the unpackme, the unpackme window disappears, but the main thread of the unpackme seems still active and unresponsive; x64dbg times out with 'Debuggee unresponsive after 10s). In the x64Dbg statusbar is says 'Running | Cleaning up wait objects...'. The x64Dbg GUI thread is still responsive, but you can't for example restart or stop the debuggee, nor close the Debugger itself normally.
It happens in Olly too (with the same ScyllaHide plugin + settings); so I guess it's anti-debug... but Olly asks if you want to terminate the unresponsive process, and clicking yes will kill the hanging thread and leave Olly operational. Perhaps that would be a nice enhancement for x64Dbg too in this case ?
PS: If it is anti-debug, it might be interesting to bugreport it to ScyllaHide as well (as a potential improvement), as to investigate the cause and potentially have a 'workaround/fix' implemented.
@hulucc I tried your unpackme with the VMProtect profile and it ran fine.
Although, it couldn't be dumped with Scylla.
OEP seems to be at RVA 0x1253