

If I had been using a LINUX OS instead of M$ (and started with VirtualBox instead of VMWare), this would NEVER have happened. It was a free upgrade from a Win 7 install on this PC.

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. 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!~!

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. 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. NOTE: You can download the conversion program (OVFTool.exe) by itself from VMWare here:īecause if you allow the Windows 10 update to DELETE VMWare install, it will delete this too! Here are SOME VERY IMPORTANT CAVEATS CONCERNING switching from VMWare to VirtualBox: Sedory windows-10-security windows-10-application-compatibility But it's your software telling me I can no longer use an application that runs just fine under Win 10 1809. though I certainly find them at fault in this as well. You are effectively telling me I must get new hardware or never be able to update Windows 10! (And don't blame VMWare. and of course a new CPU and then new Memory which is currently DDR2 not DDR3.)ĭOES MICROSOFT HAVE AN UPDATE THAT WILL ALLOW ME TO CONTINUE USING VMWare 12.5 ? it can't work with any CPU beyond what I already have!. because I cannot afford to purchase a whole new PC! (I would need a completely new motherboard. both have same issue:), it said it could not function with my INTEL Q6600 CPU !!! I had to go back to Win 10 version 1809. But when I tried to install the new VMWare version (it was a 14 or 15.

Upon upgrading to Windows 10 version 1903 (or later I would assume!), the update told me I could no longer use VMWare 12.5 (but that VMWare would supply a later version I could use. My platform has an Intel Q6600 (Dual Core Quad) CPU.
