If JCP is invoked using JRE short path e.g. C:/progra~1/java/jre6/bin/javacpl, then one can notice 2 enteries against the 6u10 inside the Java Runtime parameters dialog. It is a automation blocker in the sense that runtime params set against C:/progra~1 JRE entry will be ignored and APIs under our STL library will consider C:/progra~1...... entry as default JRE since most of the times it ends showing up at index 0 i.e. first JRE enrty inside the JRE table

Steps to reproduce:
-----------------
1) Invoke JCP as C:\progra~1\java\jre6\bin\javacpl
2)GO to Advanced > Java > View
If you can notice 2 enteries aganist 6u10 JRE then bug is reproduced