Hmmm, it looks like a Windows only error message. Unfortunately I don't have a Windows machine to test this out, but it seems there are multiple things that could be causing this: wrong path specified in the command, corrupt jar file, wrong arguments specified in the command (also see https://stackoverflow.com/questions/11943948/what-causes-unable-to-access-jar-fi...). Since it's worked for others I'm going to assume it's not corrupt, and since I've tested this with Java 10 as well, I'm guessing that's not it either. Perhaps when running the command, the JAR file isn't located in the same folder as where you're in (in the terminal)? I'm afraid I can't really help much with this.