The injection process seems to be happening (for new game processes) even when deactivated, and when GeDoSaToTool.exe isn't running

[amasover]

I spent a few hours tonight troubleshooting a conflict between GeDoSaTo (v0.21.2136) and FFXIV dx11. I installed GeDoSaTo in order to fix some things with FFXIII, and I had been running GeDoSaTo only when I ran FFXIII. Tonight I tried running FFXIV for the first time in awhile and the game crashed (only when set to dx11 mode, but not in dx9 mode) on startup almost every time (access violation in dxgi.dll).

Initially I assumed that it was a driver issue because:

• GeDoSaTo was set to deactivated
• "start with windows" was unchecked (I even rebooted after unchecking that)
• I had exited out of GeDoSaToTool.exe, and confirmed that the process was no longer running.

However, I found that I could only reliably make the FFXIV crash go away by either:

• Renaming the GeDoSaTo folder (I have it in C:/GeDoSaTo if that matters)
• Removing FFXIV from the whitelist in GeDoSaTo.

This is on Windows 10, btw.

Is this a bug, or intended behavior? And could someone explain how GeDoSaTo is being injected when there is no running process to inject it? Thanks!

[XenHat]

Wow, this could be a problem if people use GeDoSato on GTA V and suddenly goes online. Rockstar is very ban-happy with dll hooks (I got banned for using an updated Direct X dll from the Windows SDK once)

[Ofunniku]

I can confirm that this is indeed happening, shim64.dll is being hooked EVERYWHERE, even on things not on the whitelist.

unlocking the dll and deleting it seems to fix the issue, but I need to know how to keep this from happening altogether.

[vertexgamer]

Confirmed, shin64.dll just hooks to everything causing crashes on some 3d accellerated softwares like trackmania 2020, rage 2, unigine superposition. @Ofunniku btw have you found a solution? Apart from deleting it every time