[Peter Johnson]

Originally Posted by SupremeSteak1

I get /Windows/amd64/

That should be correct (for a 64-bit JRE). The next debugging step requires looking inside of the .jar file GRIP is loading to make sure the file is actually there. In C:\Users\<name>\AppData\Local\GRIP\app there should be a "core-1.0.0-all.jar" file. If you rename this to end in .zip, you can look inside it with either WinZip or Windows Explorer (if you didn't know, .jar files are just .zip files under the hood). There should be a Windows\amd64\ntcore.dll file inside... if there isn't, that's the issue (with reinstalling GRIP as the probable solution), if there is, I'm not quite sure what the issue is.

Originally Posted by origamitaco

That's funny because when I run GRIP on my Windows 10 machine the Driver Station says linux/amd64. I can't even deploy GRIP to the RIO (errors that I can't solve) so it's running on the laptop for now.

Your robot code will print "platform: Linux/arm" to the Driver Station console because it's running on the roboRio (an ARM platform). GRIP, on the other hand, is running on your Windows machine and will print "Windows/amd64" or "Windows/x86" depending on the JRE. You really shouldn't be seeing "Linux/amd64" anywhere with a Windows / roboRio combination.