I've not configured 7MTT to work on Win10, but I've gotten it working in various incarnations on Windows Server 2012R2 and invariably the problem has something to do with Java. The Java version still 1.8u112 (which lights up our Nessus scanners) and so we have to play the java-shuffle when we run the tool (i.e. install u112 and then pull it off when we're done). To zero in on what might be causing the problem, check out the server-console.log in the "C:\Program Files\NetApp\7-Mode Transition Tool\logs" directory.
I can replicate your error below just by trying to run the tool with a newer version of Java. The errors that get spit out are along the lines of:
2017/04/11 11:52:48.130 | ADVICE | wrapper | --------------------------------------------------------------------
2017/04/11 11:52:48.130 | ADVICE | wrapper | Advice:
2017/04/11 11:52:48.130 | ADVICE | wrapper | Usually when the Wrapper fails to start the JVM process, it is
2017/04/11 11:52:48.130 | ADVICE | wrapper | because of a problem with the value of the configured Java command.
2017/04/11 11:52:48.130 | ADVICE | wrapper | Currently:
2017/04/11 11:52:48.130 | ADVICE | wrapper | wrapper.java.command=
2017/04/11 11:52:48.130 | ADVICE | wrapper | Please make sure that the PATH or any other referenced environment
2017/04/11 11:52:48.130 | ADVICE | wrapper | variables are correctly defined for the current environment.
2017/04/11 11:52:48.130 | ADVICE | wrapper | --------------------------------------------------------------------
2017/04/11 11:52:48.130 | ADVICE | wrapper |
2017/04/11 11:52:48.239 | FATAL | wrapper | Critical error: wait for JVM process failed
Hope that helps...
Chris