TitanHide

[abbas 4]

On 8/12/2017 at 7:56 PM, mrexodia said:

If it takes too much time it means you are not ready to use TitanHide:

 

allright

but i googled the issue for months tried everything then asked here.

[mrexodia 1,460]

1. Install Windows 10 x64 on VirtualBox/VMWare

2. https://github.com/hfiref0x/UPGDSED

3. Install TitanHide as explained in the readme

[daniel 0]

not working on win 8.1 x64

 

BSOD kmode_exception_not_handled when i load the driver

 

 

bsod.txt

[daniel 0]

i fix it with vmpprotect driver protector 

nvm still same bsod

Edited October 16, 2017 by daniel (see edit history)

[Radiola 0]

Hi! I'm beginner in using TitanHide, so i heed help. I understood how to compile and start the driver under Win7 SP1 and it seems that driver starts and works correctly. But I do not see any influence of the driver on my debugged software. I tryed to hide both main process of debugged software and x64dbg process but had no effect. I attach to program with x64dbg before control is transferred to entry point of DLL which is interested for me, and this DLL returns fail data if I set at least one breakpoint in it. I got the same result when I use ScillaHide, TitanHide and without of them. So I make conclusion that TitanHide does not hide the debugging process, particulary debugged DLL detects breakpoints or debug steps. What am I doing wrong? Shall I hide debugged process or x64dbg debugger with TitanHide? How can I test that my process is really hidden?