Here are SOME VERY IMPORTANT CAVEATS CONCERNING switching from VMWare to VirtualBox:
NOTE: You can download the conversion program (OVFTool.exe) by itself from VMWare here:
Because if you allow the Windows 10 update to DELETE VMWare install, it will delete this too!
UNFORTUNATELY, this whole thing is NOT a good solution for anyone (like me) who already has MANY TERABYTES of existing VMWare image files: You'll need to spend a huge amount of time CONVERTING those into .OVF files which can then be imported by VirtualBox, IF YOU EVEN HAVE THE ROOM TO DO SO, and then you'll find out that there are MANY ISSUES that must be resolved to use those converted files! Example: You'd think a Linux Ubuntu install wouldn't be as difficult to work with as some Windows OS, but it is... you'll have all kinds of DRIVER issues, my imported image still will NOT connect to the Internet! IOW, due to the differences in all the VIDEO and other peripheral devices between VMWare and VirtualBox, you might as well do a completely new INSTALL of any OS you were working with! That's fine if you have 1 or 2 VMs you worked with that were not very large, BUT NOT if you have dozens and dozens of them; each with 60 GB to over 500 GB in size like I do!~!
Totally separate question: If I spend hundreds $dollars on a new PC with a SLAT capable CPU, will my current Windows 10 OS work with it?? Highly doubtful... It was a free upgrade from a Win 7 install on this PC. If I had been using a LINUX OS instead of M$ (and started with VirtualBox instead of VMWare), this would NEVER have happened. Companies should focus on making something so good that their current users will WANT TO CHANGE... NOT go FORCING the users they already made money from to have to spend even more!