Kaldaien
commented
5 years ago It is not possible to remove both Special K DLLs since SKIM64.exe has one of them loaded. It can be renamed while loaded, but that's really as much as you can do with a DLL that is locked because it's loaded.
I suspect the question is so old now that the injection strategy is not even the same. With SKIM 0.7.x (neo_injector), SKIM itself is responsible for all injection. Removing SKIM64.exe from Documents\My Mods\SpecialK\ is enough to stop any and all injection.
I do not clean out the Special K directory because it is used to store per-game config and various other things that are probably handy to keep around if you ever re-install. You can always scrub the directory yourself, but you should be aware that all of my recent per-game mods will re-create that directory and store anything shared between mods there (i.e. CEGUI, hardware performance monitoring drivers, SteamAPI DLLs, Plug-Ins, ReShade, etc.)
As for anti-cheat, to the best of my knowledge Special K is not recognized by VAC (it's a heuristic-based matching system, that matches patterns in known exploits) or Easy Anti-Cheat. VAC's not a big problem, but my software is not digitally signed so Easy Anti-Cheat will unload Special K 99 times out of 100.
Only one of the SpecialK dlls is being removed in the My Mods folder. Additionally the Special K folder persists.
Is there a list of everything that the Global Injector adds to the system (I'd really like to verify that the uninstall returns the system to a true pre-installation state)? Additionally, how does this injector impact Steam games like Counter-Strike:Global Offensive which has VAC as an anti-cheat?