there is no "known" issue with that on windows.
It could only happen if you use some kind of javaagent or have something really screwed with your environment.
Yep. A simple wrapper script that set the JAVA_HOME and JBOSS_HOME so I could have JBoss EAP 5.1 and 7.0 running concurrently was the culprit. The same script also read a couple of properties files that caused no problem in Wildfly 9 when I was porting some of our code over earlier this year in prep for the EAP GA release.