News for hackers. Stuff that matters.
Re:Cracking Windows Open: Porting RADV to Win32 by not_a9 on Wednesday July 29, 2026 @05:41AM (#49095234)
If anti-cheats actively whitelisted drivers playing competitive video games would be impossible for people using any rarer HW/utilities. Vulnerable drivers are generally blacklisted when found.

Getting your driver signed seems like a pain these days, yeah

Re:Cracking Windows Open: Porting RADV to Win32 by inigyou on Wednesday July 29, 2026 @07:53AM (#49096284)
Yes this is how they work. You use a mainstream GPU or no game for you!
Re:Cracking Windows Open: Porting RADV to Win32 by not_a9 on Wednesday July 29, 2026 @08:34AM (#49096670)
Throw a lawn dart at the contents of https://vx-underground.org/Archive/Driver%20Collection/Bulk%... all drivers download, load the resulting driver and try to get into Fortnite or something. It'll probably get in fine assuming driver isn't Unknowncheats superstar already
Re:Cracking Windows Open: Porting RADV to Win32 by nananana9 on Wednesday July 29, 2026 @05:44AM (#49095252)
I'm inclined to believe this is exactly what happens, given that both Bluetooth and my printer stopped working the last time I tried playing a Riot game.

Also got a BSOD in vgk.sys, and it left a bunch of junk in my EFI partition after I uninstalled it. Fun times.

Re:Cracking Windows Open: Porting RADV to Win32 by LoganDark on Wednesday July 29, 2026 @06:01AM (#49095375)
Maybe drivers are treated differently, but I remember having to update Windows 11 to play ARC Raiders because my specific version was old enough that system files did not pass their whitelist check. It told me which system file failed the check - I don't remember which it was exactly, but it definitely wasn't one that'd ever been modified, just one that wasn't recent enough it seems, at least going off of how updating fixed it.