8f6a993769
Issue was caused by the launcher not dealing with slashes in the way windows expects them to be handled -- last slash of the path considered an escape character for the following qoute. This is definitely to be ported to the 2.72 release.