![]() In order to install Windows 8.1 through Boot Camp, the internal drive (HDD or SSD, depending on your configuration) must have only a single user-available partition, otherwise the application will throw an error asking the user to rectify the problem to continue. That was both a wise and a bad decision at the same time. ![]() So if I ever wanted to reinstall the OS I would not lose all my data through formatting. Prior to using Boot Camp for the first time, I created a second partition on which to store stuff that is not OS X-related (application setup files, movies and so on). That was my premise, coming from someone who has never owned a Mac nor had any previous experience with Boot Camp. You can either rename the Boot Camp VM back to "Boot Camp", or simply drag it into the Fusion VM Library under the name you gave it.Shortly after my new MacBook Air arrived, I proceeded to install Windows 8.1 thinking that the OS would work just fine on Apple's ultrabook as it does on my five year-old HP laptop. Rename the Boot Camp VM bundle, which will prevent Fusion from deleting it as a failure, then acknowledge the alert panel. If you'd like to do the renaming via Finder, open a Terminal window and enter the command "open ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp" and Finder will open the ordinarily hidden folder for you. Note that the ~/Library folder is hidden by default under OS X Lion and Mountain Lion, so the simplest way to get to this folder might be from Terminal, not Finder. You'll find the Boot Camp VM in your home folder, under ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp. We'll do it by renaming the VM.ħ) While the error alert panel is showing, use Terminal or Finder to rename the VM. What we do need to do is prevent Fusion from deleting the VM when you acknowledge the failure. We'll want this file from Windows.ģ) Restart your Mac under native Boot Camp.Ĥ) From Windows, find the file bootcamp.reg where you saved it, and double-click to add those settings to the Registry.ĥ) Restart your Mac under OS X, start Fusion, and recreate the Boot Camp virtual machine.Ħ) It's likely that it will fail again at the "preparing your virtual machine" stage, but that's no longer critical since the necessary settings have been added to the registry already. They don't interfere with using Boot Camp natively.ġ) Find the file /Applications/VMware Fusion.app/Contents/Resources/naos-1.0.vmwarevm/reconfig.iso and open it under OS X, which will mount the ISO.Ģ) Copy the file "bootcamp.reg" on the ISO and copy it to some folder on your Mac, or to a USB drive. As a workaround, you can add those keys and driver enablings (!) manually, under Boot Camp itself. Fusion is attempting to insert registry keys and enable drivers for the boot device, and in certain situations it's unable to do so. The problem occurs after the Boot Camp VM has been set up, but before it's powered on for the first time as a virtual machine. ![]() While I don't have a fix for that right now (we have a bug filed, and are working on it), I do have a workaround. The problem I think you saw, a failure at the point of "VMware Fusion is preparing to run as a virtual machine" can be caused by the state of the Windows registry. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |