VMware needs fix that to make life easier for their customers. Oddly, even though what each documents wanted me to do was largely the same, a couple of things that the VMware discussion page contradicted what the VMware knowledgebase document said. But thanks to my friend Google I found this discussion page from VMware which worked. To try and fix that, I tried this VMware knowledgebase document with no success. My Windows 10 and 7 virtual machines had no sound after they came up in VMware Fusion 10.The only problems that I came across were: It’s pretty straightforward for the most part. The process to migrate is detailed in this VMware document. Migrating from Parallels Desktop 13 to VMware Fusion 10 was mostly easy. I did note that in the process of reviewing VMware Fusion 10, it came out as simply the better product as it supports features such as NVMe devices, UEFI Secure Boot, UEFI boot, and TPM chips which means that I can accurately replicate customer environments so that I can understand why they are having an issue, and come up with a fix for it.That’s a total #EpicFail in my mind because if you pay for a product, you should not ever expect to see ads. The secondary reason for me to make the switch was the fact that Parallels Desktop 13 displays ads when you start the program.Parallels Desktop 13 doesn’t appear to provide that mitigation which was a concern to me and was the main driver for me to make the switch. That’s important to me as I take security seriously. VMware Fusion 10 provides mitigations from the Spectre CPU vulnerability.Now before I get to the part where I tell you how I did it, let me tell you why I made the move to VMware Fusion 10. But I knew that I had to get it done as I use these virtual machines frequently in my job. Plus I was expecting to have some problems along the way. It was something that I was dreading because of the time involved to do this. Last night I got around to migrating my virtual machines from Parallels Desktop 13 to VMware Fusion 10.

Parallels vs vmware 2018