I didn't checked the launcher source code thoroughly and I can assess its code only through my limited knowledge of a different programming languages, I have no experience in java whatsoever. I might be wrong, but I think it checks the admin privileges exclusively for the MXL.dll, just a precaution to make sure that you can run the game (patch the game) in the first place.
SteelWings wrote:And, yeah, I'm assuming this has to do with how eternal code basically is injected in base version on D2, but I'm not sure in all those permissions are "required" per se, that's something only a MXL developer can answer.
You don't need the dev to answer this question, I know what I'm talking about because I looked into the MXL.dll disassembly. Moreover, I know about this stuff because I'm using Whist's
D2Template for a few of my projects and since I modified it a bit, I know how it works and I'm assuring you that MXL.dll code is roughly based on the code of the aforementioned tool. So the initialization of MXL.dll fails either when it's calling
AdjustTokenPrivileges or
OpenProcess and it's not my wild guess.