If you write the property with java and then read it you will have no problem. This variable is written by advanced installer during windows installation and then read with java and that leads to problems here, because advanced installer writes it in this "bad way". Java itself does proper escaping of course.
Ouch - am guessing a bug report to the "not so advanced" installer might be in order.
