Note that this is about DLL-Ejection
Today I tested a DLL with some Luastuff. I want this DLL to be injectable and ejectable "on the fly". Injection works fine. But I tested like 30min why 'Winject 1.7' refuseses to eject my DLL. First I thought there must be a mistake in my DLL ... like something is not cleaned up correctly ... but then I noticed something:
Winject always refuses to eject ANY DLL after the Login.
To be 100% sure I created a simple empty DLL like this ...
bool attached = false;
BOOL WINAPI DllMain(HINSTANCE hDLL,DWORD Reason,LPVOID Reserved)
attached = true;
attached = false;
...and it was the same thing ... Ejection wont work after the Login. This sucks!
I tested another DLL -In-/Ejector called 'RemoteDLL' by Nagareshwar Y Talekar and it worked. But I trust 'Winject' much more because its obviously made more professional.
So my Question is:
Any ideas why Winject refuses to eject any DLL after the login?
...srsly that pisses me off
... something seems to be wrong!
I have attached the two DLL Injectors and the empty DLL for testing purposes.
This stuff may trigger ur AV, so noobs stfu!