So probably not clear from title but I’d say this is a Linux problem. Basically I’m using sbctl to sign the cachyos kernel on fedora since it eeks out a little performance and also as I understand it it uses a slightly differently scheduler so my computer doesn’t lock up when hitting a steam download hard. I’ve only just started getting the error recently so I’m assuming it’s related to the MS secure boot key stuff that happened in June. I have confirmed that using the default provision from my mobo doesn’t trigger the vanguard error. Trying to figure out a solution, otherwise I guess I have half a mind to just nuke shitty windows forever again. I’ll take either an alternative solution to the cachyos kernel or a solution to the keys. What I don’t understand is doesn’t sbctl enroll the default keys from your mobos firmware anyway? Is this simply that ANY modification to my secure boot keys is somehow a problem with vanguard now? Thanks all!
Every time you do anything on that computer even on Linux that kernel level anticheat they use can see it all.
Is it worth playing that game?
Can you explain how that’s the case exactly?
Technically yes, practically no.
Windows doesn’t include the drivers to read Linux file systems (except through WSL) and Vanguard sure doesn’t either.
If you encrypt your disks, then it definitely can’t.