Actually this is a vision2 issue on Windows. It will be fixed in release 6.0.6.7256+