Games running with elevated privileges are typically the case for those using BattlEye, Easy Anti-Cheat, and a few other in-house anti-cheat solutions. Special K won’t be able to inject itself into any games running with elevated privileges unless the user does unexpected stuff such as running SKIF/SKIM/the global injection as an elevated process. The reason behind this design was to allow the use of Special K on Steam without the user appearing as “In game: Special K” for their friends on Steam. In case of SKIF, I believe both 32-bit and 64-bit injection is taken care of by background rundll32.exe processes that retains the global injection service even if SKIF is closed down without stopping global injection. This was partially not the case with SKIM, where SKIM64.exe took care of 64-bit injection while a background process rundll32.exe took care of the 32-bit injection.
You can start the global injection and then exit SKIF – the global injection will still remain active in the background. The global injection service in SKIF is not actually a part tied to the Special K Injection Frontend (SKIF) itself.
We don’t really have any ability to say what so ever either way, so at best its just guesswork.
0 kommentar(er)
