This seems to be an unresolvable issue... Are you going to step in here VMWare to correct the issue r give us a work around?
