hi, for this is need for windows on example another app with driver, that can completly hide app or driver from another app, i see on github apps like this to hide cheat from game that work in background, so it's possible to made this, but second problem is that you need to run windows in test mode to install app with unsigned driver.
How do I hide the fact to Windows that it runs in a VM?
- Thread starter speedbird
- Start date
I'm not saying you are cheating, but, thats exactly what anti-cheat software is looking for. This will always be a cat and mouse game and you will never get support neither from EAC nor the game devs.
Unfortunately, though pretty cool, to game with mutliple people on one rig, this will never be reliable with games that run some form of anti cheat. EAC is doing a pretty good job here, it seems.
My honest opinion: Just run games locally, if they require anti cheat.
( And also: Don't cheat!
)
Unfortunately, though pretty cool, to game with mutliple people on one rig, this will never be reliable with games that run some form of anti cheat. EAC is doing a pretty good job here, it seems.
My honest opinion: Just run games locally, if they require anti cheat.
( And also: Don't cheat!
)
I'm not focused on any particular purpose, I just don't want any software I am running to be able to know about the status of my VM.
My plan is to always run my desktop through hypervisor and I would like to have at least all of the basic VM detection methods defeated.
Preferably without any performance damaging impacts.
Things like Spoofing driver names and hiding places where qemu is identified, such as the motherboard information.
Patching the kernel timing method.
I don't want to try to beat the "cat and mouse" game at the cutting edge.
But I want to have all the counter measure to defeat techniques from 1-2 years ago and earlier.
Is there a guide somewhere in these forum that goes through each known detection method and how to counter it ?
Maybe a configuration recipe to create VM that aren't detectable by the most basic methods ?
My plan is to always run my desktop through hypervisor and I would like to have at least all of the basic VM detection methods defeated.
Preferably without any performance damaging impacts.
Things like Spoofing driver names and hiding places where qemu is identified, such as the motherboard information.
Patching the kernel timing method.
I don't want to try to beat the "cat and mouse" game at the cutting edge.
But I want to have all the counter measure to defeat techniques from 1-2 years ago and earlier.
Is there a guide somewhere in these forum that goes through each known detection method and how to counter it ?
Maybe a configuration recipe to create VM that aren't detectable by the most basic methods ?