Very interesting! I don't have a workaround for you on this one. To be honest, this is the first time I've *ever* used this command on Windows - so I've never noticed this. I'll log it as a defect.

Thanks