Ah, I thought I wrote in the last reply, it didn't work. So I had a nap. Woke up, and thought: maybe rebooting will help? I guess I was too tired to notice Windows telling me to reboot after changing the SE path.
AND IT DID. So guys, I know it wasn't much, but it seemed to be the System Environment path messing up with it. I would still call that a bug, since it should work no matter what (Perhaps split by ; and check it contains part of the expected path, but I'm not a fully fledged developer)
Or at least one of the fixes was changing the SE path. The .NET enabling might have helped too, I can't be certain myself. But I know it didn't work before I reset my path to stock.
So thanks again for helping spot the issue, and for your timely and informative replies.