You could try running it from a shorter path name, although I don't think you're hitting the limit there but it's hard to tell.
Could be a live protection from your antivirus blocking the execution of the virtual stuff, you could try disabling it completely(or looking for a live feature to add an exception/temporarily disable) to see if that fixes it.
I'm assuming you're using windows 10 from the look of that error box style and I'm not sure if someone else tested it on it so could be the issue. It was released 4-5 months before I made the fix so it should support it but maybe not.
Edit: Read back a bit and someone did make it work on win 10 so unless an update screwed it up, that shouldn't be the issue.
Could be a live protection from your antivirus blocking the execution of the virtual stuff, you could try disabling it completely(or looking for a live feature to add an exception/temporarily disable) to see if that fixes it.
I'm assuming you're using windows 10 from the look of that error box style and I'm not sure if someone else tested it on it so could be the issue. It was released 4-5 months before I made the fix so it should support it but maybe not.
Edit: Read back a bit and someone did make it work on win 10 so unless an update screwed it up, that shouldn't be the issue.
Last edited: