That's good to hear...
AFAIK, Windows installer primarily checks Windows registry in order to detect potential JDK/JRE installations that could be used for installer and GlassFish runtime and I think we have a known issue where 64 bit JDK installations are sometimes not properly detected. So, that would explain this behavior. I'll see if we can beef up JDK verification and check JAVA_HOME value for potential JDK location...