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.

1. Install Windows 10 x64 on VirtualBox/VMWare

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

3. Install TitanHide as explained in the readme

not working on win 8.1 x64

 

BSOD kmode_exception_not_handled when i load the driver

 

 

bsod.txt

i fix it with vmpprotect driver protector 

nvm still same bsod

Edited October 16, 20177 yr by daniel

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?

Same, i just curious how to make sure that TitanHide really hide x64dbg / process.

Why debugged stop, when the target open?

Now its works! But sometimes, i got BSOD but nevermind, i love it.
I am not hide PID but it's run smoothly

Edited May 29, 20214 yr by sitikomariah

Can someone help me I am unavailable to solve issues 

Please guide me 

 

10 hours ago, POOP COME said:

Can someone help me I am unavailable to solve issues 

Please guide me 

 

do you have installed https://learn.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads what source do you use

 

I used official @mrexodia provide souce project. Old issue was fixed by install SDK and wdk now I face new error. @Coco420Thanks for reminding me about wdk.

try this compiler option in your proj settings:

TitanHide has been updated to support the latest VMProtect v3.9.4 changes.

The service name is now used as the device name, as well, so the check for \\.\TitanHide will fail if you name the service the differently.

Latest version (v0019) download link

 

Edited June 1Jun 1 by Stuttered

thanks a lot for this !!

Well thats work 

does not work on 396

It also does not work against the latest version of Themida/WinLicense