Textractor has a powerful feature called "Auto Attach." If you have this enabled in your settings.json , Textractor will attempt to inject code the moment it detects a compatible process starting. If the auto-attach fails or is too slow, and you manually try to attach, you may trigger the conflict message.
Since a ghost DLL is likely stuck in memory, you need to purge everything. textractor already injected
This is the most common cause. When a game or Textractor crashes unexpectedly (or if you force-close the game via Task Manager), the injected code may not be cleaned up properly. When you restart the game and try to attach Textractor again, remnants of the previous session might still be lingering in the system's memory or the Textractor configuration files, triggering the "already injected" logic. Textractor has a powerful feature called "Auto Attach