VMware Tools then installed a ton of drivers and the graphics instantly looked better. Many people miss this step but completion of VMware Tools required going to Computer and actually finding the mounted CD-ROM of VMware tools before doing the next next next. Then I went through the rest of the Windows customization prompts such as choosing a keyboard layout and a username.Īfter it fired up I installed VMware Tools.
I continued with the Windows installation, choosing custom installation so I could opt out of the Big Brother program at the end of it. Doing this cuts Apple out as the middleman and lets VMware interact directly with the Windows 10 image. Based on that, I venture to say that native drivers for Windows 10 from Fusion are superior to the stuff that Apple gave it with Boot Camp. Right away, the VM's sound worked, which is more than I can say for my original Boot Camp VM. I let it use the default 60 GB virtual hard disk size. So instead, I deployed an empty Windows 10 64-bit VM, attached EVAL. The bottom line is that with a different combination of VMware Fusion, Windows 10, and MacOS, I was unable to reproduce my original success of even deploying Boot Camp. However, Boot Camp would not accept it as a legitimate "64-bit version of Windows past Windows 8".
I tried to do it myself and make a Boot Camp from the 90 day eval of Windows 10 Enterprise ( free here). It seems that this thread and others like it just winded down without resolution. Reasons ranged from the MacBook using PMBR instead of MBR, or the newer SSDs shipping with 4Kb sectors instead of the 512-byte sectors used in Fusion ( source thread for that point).
There are over a dozen forum threads out there (not just here) about people wondering why Fusion wasn't picking up on Boot Camp. You would just deploy the same ISO that you used to set up the alternate partition in Boot Camp. I believe that the correct approach is to change your strategy to deploy Windows directly from the ISO.
0 kommentar(er)
