Jump to content

Updating to Windows 10 on a Clover Multi-Boot System


mnfesq
 Share

3 posts in this topic

Recommended Posts

Most of the time, I use Windows for work and run it as a VM in OS X using Parallels.  However, none of my work files are in the VM.  I save them to a folder in a Windows installation that I rarely use that boots natively with Clover.  Even though I don't use that Windows installation very often, I decided to upgrade it from Windows 8.1 to 10.  (I had already created a new VM for Windows 10 and am using that exclusively in Parallels - Goodbye Aero Glass!)

 

Because it was so easy to create a new VM of Windows 10 in Parallels, I mistakenly believed I would have even less trouble installing it on a hard drive in my laptop.  Wrong.

 

I had the installer as a mountable image file.  That worked great with Parallels and it mounted just fine using Windows Explorer.  However, I ran the installation program about 4-5 times and each time it said it had a problem and could not check to see if Windows 10 could be installed on my laptop.  I rebooted and did the usual stuff and nothing seemed to make a difference.

 

Here's the deal:  Windows 10 can only be installed on an active partition.  If you use Clover and have it installed in the EFI partition of your disk running OS X, OS X will be your active partition.  In my case, I have OS X and its EFI partition on an mSATA drive.  Windows is installed on a separate hard drive.  In my BIOS, I can only select whether to boot from an internal hard drive or a USB drive.  When the mSATA slot is in use, that will be the internal hard drive. Therefore, I had to remove the mSATA drive that has OS X (and Clover) on it.

 

When I tried to boot from my Windows hard drive, I got a Boot0:error.  That was because I did not set that drive to active before I removed the mSATA drive.  I could have done that by using fdisk in OS X.  Having forgotten to do so, I chose to use a USB installer I have with Windows 7 on it.  I booted to the USB drive and selected the repair option and that gave me access to a cmd window.  I used the diskpart command, listed the drives, selected the hard drive (not the USB drive), listed the partitions, selected the Windows partition, and set it to active.  I shut down the laptop, removed the USB drive and restarted and Windows booted up and Windows 10 installation could proceed.  After installation, I reconnected the mSATA drive and Clover booted my installations of Windows 10, Yosemite and El Capitan just fine.

 

The Windows drive is 1TB of which the Windows partition is about 500GB.  It took about 1 hour to install Win 10 and it took another hour to upgrade my Win 8.1 to Win 10.  DO leave adequate time to install Win 10 when you decide to do so.  A bunch of apps needed updating and a few didn't have upgrades and wouldn't work.  MacDrive version 9.x will NOT work on Windows 10. 

 

All-in-all, I like the new Windows.  I am having difficulty deciding whether to use all of the features and forego my privacy or sacrifice some of the new features to so that I can continue to enjoy Donkey porn without receiving targeted ads relating to that (just kidding but you get the idea.)  

  • Like 1
Link to comment
Share on other sites

...hi, i have just taken the plunge as well...went from W7 to W10....and just for fun...i removed the HDD from a working lenovo box with mavs installed...put it in another box with a P5KC mother board...and surprise...with a graphics tweek to change from amd to nvidia(clover) osx booted right into mavs....W10 installed a few drivers and it works fine as well...2 portable systems...at least once...only changed to take advantage of the asus board's overclock functions...next I'll take the quad-core from the lenovo and install it as well(short on thermal paste)  :smoke:"sometimes, sh*t just happens"

Link to comment
Share on other sites

  • 2 weeks later...

Hey Guys,

 

I hope to get some support here from you on my issues trying to update to windows 10.

 

I admit, I may have a complex disk setup with a fusion drive (made of a SSD "disk 0" plus HDD "disk 1"), a time machine backup disk "disk 2" and - last but not least - a windows disk "disk 3" on which I installed 8.1 in UEFI mode 64-bit.

I managed to set up clover EFI properly for multi boot, by means that I have both (OS X and windows) EFI folders on my first EFI partition. This is located on the SSD "disk 0" of the fusion drive. All other disks (HDD from fusion drive "disk 1" and time machine disk "disk 2") do have empty EFI partitions.

Besides, there's also the recovery volume (just to not forget to mention).

 

As for the windows disk "disk 3", for whatever reason, there's only the windows partition "partition 2" and a small 128MB disk1s1 ("partition 1", windows reserved) left. No "EFI" as such, so my guess is that I somehow messed the layout of that disk up at some point earlier.

 

My problem is that I can't update to Windows 10 now. Setup breaks after the first reboot, makes a rollback and gives me an error re "safe_os" phase. My guess is that windows 10 setup tries to access the EFI and cannot find it where it should be?

 

Selecting disk 3 during boot does not work, finds no "bootable OS", which makes sense with no EFI being on that disk, right?

 

I have read bit about possible ways to "repair" windows EFI, but I honestly feel a bit insecure and wanted to double check with you to hopefully find the most suitable way to get this solved.

Some info says there should be 3 partitions on the windows disk, namely a small ca. 100MB system reserved, a 300MB (?) EFI and finally the windows "data" partition. To me this makes not much sense, as I do not think I have deleted a complete partition at any time.

 

Any ideas?

 

update: solved (or not solved). I made a clean new installation incl. completely new partitioning of the windows drive.

Link to comment
Share on other sites

 Share

×
×
  • Create New...