Hit this bug, it seems, on vmware fusion 2.0.3 just now.
unmouting the install iso fixed the issue before applying any updates/patches
Hit this bug, it seems, on vmware fusion 2.0.3 just now.
unmouting the install iso fixed the issue before applying any updates/patches