The workaround works after reboot. thank you.
Your original terminal command worked. I was then able to delete old fusion from the windows drop down and install v. 6.0. Thanks for the help.
Hi Darius - I get the message, "The file specified is not a virtual disk"
This is from my Windows 7 VM - the one I use most :-(
I have got XP going OK and Ubuntu by launching directly from Finder ... then they're OK from the VMware library panel
I'm afraid I don't have any more detail than that. I still cannot start Windows 7
For some of us, that is not the correct answer!
I have this same problem and have tried everything I can find about the problem including what's in the VMware Fusion 6 fails to start (2058900) link. I've compeletely deleted manually (it's pretty sad that there is no Uninstall for VMware Fusion!), tried the rm command recommended other places, I've done this multiple times now with restarts. I've wasted an entire afternoon trying to install Fusion 6, to no avail. Nothing works, I see the License Screen for a second or two and the it crashes
I've looked in the crash logs and there is no reference to license anything. Makes sense because I've deleted those files several times now. I've included a crash file. I did go back to 5.0.3 at one point and it works fine!!
Any help would be greatly appreciated.
Your problem there is quite different: One of your USB peripherals is misbehaving and reporting an empty serial number. You should be able to find out which device it is by looking in your host's System Information tool, under Hardware > USB... just look for one with no Serial Number.
Remove whichever device is causing the problem, and you should be able to use Fusion 6. We have an update in the works that will allow Fusion to work with these devices.
So far, we've seen it with the Apogee Duet USB audio interface, a Zebra Thermal printer, and a handful of other devices. We'd be interested to hear which device is causing the problem for you.
That was the problem and I'm amazed at the quick response.
I just have one nagging question. What the sour pickles were ya'll thinking. I can't believe 5 worked just fine with this device and now 6 crashes because of a missing serial number. And I've wasted most of a day trying to get 6 installed. I've never heard of any software crashing because of an USB device missing a serial number and I've been playing with computers for over 40 years. I am totally unamazed that this managed to get out in the real world and waste so much of your customers time, since I'm apparently not the only person that the license fix didn't help.
BTW, the device is a CablesToGo USB to ATA, SATA adapter, part number 30504. SN 1109JM02610.
Bought and downloaded VMware Fusion 6 this morning and ran into exactly the same problem: Installation instantly crashed after startup (update from Fusion 5.x, Macbook Pro, OS X 10.8.5).
So I am really glad I found this thread, because deleting the file /Library/Preferences/VMware\ Fusion/license.fusion.site.6.0.200*** finally solved the problem.
But why is a bug that has been identified and solved (very fast) two weeks ago still present in the recent downloads? I only lost about 1h with this issue, but I guess that many Fusion users run into this problem too!
Just a quick note that I have also been affected by this issue but things are now working after deleting the offending preferences...
My issue appears to be similar and yet not so similar.
a. deleted the old license files: crash
b. deleted ALL preference files: crash
c. did a manual uninstall as show in the vmware link:
You guessed it: crash.
c. pulled all the USB devices: crash
Just bought Fusion Pro 6 today and now dead in the water. As far as I can tell, there isn't much for Fusion to be unhappy about.
vmware-crash.txt 53.6 K
I have tried to apply all suggested fixed, but now joy. I do not have any USB's attached. Same problem for MBA per this report and iMAC. iMAC initially worked fine but then started crashing today. I have only upgraded from v4.1.
For anybody interested. This was resolved, with the help of the nice support people from vmware, by doing a complete uninstall including removing all traces of vmfusion in preferences etc and then reinstalling