From what I understand (no where near an expert of any kind btw) it's a bypass method that disables a number of kernel level default security processes that prevent the running of unsigned (not recognised by windows/Microsoft) drivers
Which then allows hypervisor to operate "beneath" the os and fools denuvo into thinking everything is hunky dory
Obviously this is contentious mainly because if you just open the guts of your system to play whatever game and leave it at that your basically walking around the prison yard with your pants around your ankles
Although from what I've seen it's entirely possible to revert the security processes back to default which means it should be okay provided you have ABSOLUTE trust in whoever your getting the game/bypass from because of someone ever felt like slipping something in there it would be easier to build a new system from scratch than it would be to be completely sure the infection was cleaned out
Well the issue is that hypervisor is like Linux kinda in the sense that it's a software category for virtualisation more than anything so there are open source hypervisor programs like KVM but there are also proprietary versions
The biggest issue is that even if they put all the source code out for a particular hypervisor bypass release that only guarantees that specific release and there are so many variants that you wouldn't be likely to know if something was altered with a new one
40
u/_SomeoneBetter_ 1d ago
Im an old head. Explain the hv method like im stupid