Most likely the protection (SC) was updated, here is dll - compiled, all of a sudden someone does not work.
But that's the question, it's reversing in Africa, reversing. After startup, dll creates a file (decrypted), but it is still protected, although - in fact, it should unload already clean (launched) files via l2.exe (bin).
Maybe someone, will advise what to add here so that it works?
ps.