jdhiro

Q: Windows 8.1 install fails on new 2013 Retina MacBook

I doubt there are many people out there who can help with this yet.  I was able to pick up my 2013 Haswell Retina MacBook Pro from my local Apple store this morning (yay!), and so far everything has been stellar.  However, I'm unable to install Windows 8.1 via Bootcamp.  I have not tried Windows 8 or 7.

 

I've tried installing both via USB thumb drive, and via DVD on external SuperDrive, with the same results.  I know that 2013 MacBook Airs have to install via UEFI so I've tried that as well.  What I've tried:

 

Booting into UEFI:

- After creating the partition in Bootcamp, I boot holding OPTION

- At the boot selection screen I select "EFI BOOT"

- I go through all the motions, including formatting the BOOTCAMP partition

- After all the files have been copied, I get a message that "Windows cannot update the boot partition and that my progress won't be saved" (not the exact message).

 

Booting via BIOS:

- After creating the partition in Bootcamp, I boot holding OPTION

- At the boot selection screen I pick "WINDOWS"

- When I get to the partition selection/formatting screen it won't let me proceed, when I expand the error message it tells me that partition can't be used because it has a GPT partition table.

 

So, I'm stuck =(  Any ideas?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Oct 23, 2013 8:56 PM

Close

Q: Windows 8.1 install fails on new 2013 Retina MacBook

  • All replies
  • Helpful answers

first Previous Page 33 of 41 last Next
  • by CraigT33,

    CraigT33 CraigT33 Dec 29, 2013 6:50 PM in response to kyraxyg
    Level 1 (0 points)
    Dec 29, 2013 6:50 PM in response to kyraxyg

    I tried the same as iampastwitsend using diskpart (disk util is not recognized) at the windows partition screen but failed in just the same way.

     

    Can you explain at exactly which point you use cd B:

     

    i used:

     

    DISKPART> ASSIGN LETTER=B

    DISKPART> EXIT

     

    X:\services

    Then i just closed the command window (it already failed the first time so i had pressed format already) selected partition 4 and pressed next.

  • by Number88,

    Number88 Number88 Dec 29, 2013 7:00 PM in response to CraigT33
    Level 3 (750 points)
    Dec 29, 2013 7:00 PM in response to CraigT33

    You need to show volumes

     

    diskpart

    list disk  -  this will show your current disk as a number - let's say it's disk 0 (it may be 1)

    select disk 0

    list volume  -  this will show the volumes on the disk. Note the volume no of your EFI partition - let's say it's 2

    select volume 2

    assign letter=B

    exit

    close command prompt

  • by CraigT33,

    CraigT33 CraigT33 Dec 29, 2013 7:53 PM in response to Number88
    Level 1 (0 points)
    Dec 29, 2013 7:53 PM in response to Number88

    Sorry i only added the last few steps.  I did all those exactly as you listed except efi was disk 1.

  • by kyraxyg,

    kyraxyg kyraxyg Dec 30, 2013 12:44 AM in response to jdhiro
    Level 1 (0 points)
    Dec 30, 2013 12:44 AM in response to jdhiro

    What i did was ;

    as Number88 told

    diskpart

    list disk  -  this will show your current disk as a number - let's say it's disk 0 (it may be 1)

    select disk 0

    list volume  -  this will show the volumes on the disk. Note the volume no of your EFI partition - let's say it's 2

    select volume 2

    assign letter=B

    exit

         and at this moment

         X:\services   cd B:

         B:\ dir

         B:\cd APPLE or some directory

    after all these it did install without error about boot update, it may be my luck but i think it is related.

  • by Number88,

    Number88 Number88 Dec 30, 2013 7:21 AM in response to kyraxyg
    Level 3 (750 points)
    Dec 30, 2013 7:21 AM in response to kyraxyg

    I think this could be one answer to the "unable to update boot configuration data" error.

    I think that the Windows installer may have a difficulty mounting the EFI partition. Windows loves a "drive" letter and the native EFI partition doesn't have one.

     

    But I also think there are other problems once an install attempt has failed.

     

    My very first attempt to EFI install Windows 8 worked without a problem. Whereas my second and subsequent  attempts (after wiping it out and starting again - don't ask why) failed with this error.

    Secondly my first attempt at EFI installing Windows 8.1 worked without any error.

     

    Once Windows 8/8.1 is installed the EFI partition has the Apple folder and a Microsoft and a Boot folder. I suspect that if those 2 Microsoft-related folders already exist in the EFI partition then the installer won't edit them and fails.

     

    If an install fails (but you get the EFI Boot option for a hard drive (not a USB drive) in the boot manager) I suspect that you should remove the 2 Microsoft-related folders in the EFI partition before re-attempting an installation.

    This can be done by mounting the EFI partition in OSX and then in the Finder send the two items to trash. Don't touch the Apple folder though!!!

     

    Just my 2 cents 

  • by CraigT33,

    CraigT33 CraigT33 Dec 30, 2013 8:59 AM in response to Number88
    Level 1 (0 points)
    Dec 30, 2013 8:59 AM in response to Number88

    Thanks for the clarification.  Im going to try again when i get home from work.

     

    This thread is certainly a baptism of fire, good experience though.

  • by eternalhack,

    eternalhack eternalhack Dec 30, 2013 11:06 AM in response to Number88
    Level 1 (0 points)
    Dec 30, 2013 11:06 AM in response to Number88

    I successfully installed Windows 8 to boot via EFI using bootcamp assistant without any problems and was going to try and reinstall various ways to see if I could get it to fail but now I'm nervous. I'm going to use Winclone to save off my current windows installation so hopefully I can get back to my current working setup if I run into issues.

  • by kyraxyg,

    kyraxyg kyraxyg Dec 30, 2013 11:25 AM in response to jdhiro
    Level 1 (0 points)
    Dec 30, 2013 11:25 AM in response to jdhiro

    By the way i have a question for those who have managed to install windows in EFI mode.

    I have seen videos of new MBA booting windows in EFI mode but my rMBP doesn't boot so quickly.

    So how is your boot compaired to below video and does anyone have any idea about why mine boots slower than a MBA.

    http://www.youtube.com/watch?v=qZCl_E9NHKs

  • by Number88,

    Number88 Number88 Dec 30, 2013 11:39 AM in response to eternalhack
    Level 3 (750 points)
    Dec 30, 2013 11:39 AM in response to eternalhack

    eternalhack, I would be nervous too. What has happened before may not happen again, even on the same machine. This has been shown to be true by others.

     

    kyraxyg, when I had an EFI install of Windows 8 and 8.1 it boots very quickly if I am using the Microsoft Basic Display driver. However, if I enabled Nvidia (in Windows 8 - wouldn't work in Windows 8.1) the system booted much more slowly and there were 4 or 5 flashes of the screen from black to grey. Almost as if it was deciding which driver/screen to use (it showed 2 screens available on my rMBP! ).

    Does your rMBP have dual graphics?

  • by kyraxyg,

    kyraxyg kyraxyg Dec 30, 2013 12:39 PM in response to Number88
    Level 1 (0 points)
    Dec 30, 2013 12:39 PM in response to Number88

    I have updated the nvidia driver from the nvidia site beta drivers. I only see one graphics card and one screen no basic driver no intel card. While booting i am not having screen flashes but the openning sceen animation circles about 3-4 times.

     

    I even suspected  whether my install was BIOS but i have checked and it certainly is EFI.

     

    I am thinking about unistalling some of bootcamp installations.

  • by Number88,

    Number88 Number88 Dec 30, 2013 12:54 PM in response to kyraxyg
    Level 3 (750 points)
    Dec 30, 2013 12:54 PM in response to kyraxyg

    I'm assuming from what you wrote that the Intel chip does not appear in Windows' device manager.

    This is normally the case for Bootcamp installed Windows (even bios boot) as the Intel chip is switched off.

    That doesn't happen if you don't use Bootcamp - or it didn't here. Therefore the Intel chip is visible to Windows.

  • by kyraxyg,

    kyraxyg kyraxyg Dec 30, 2013 1:31 PM in response to Number88
    Level 1 (0 points)
    Dec 30, 2013 1:31 PM in response to Number88

    i only used bootcamp to create the usb. after that i merged the windowds partition to mac partition after that i recreated a new partition and deleted it to create unlocated space.

    i am pretty sure the install is EFI as i have checked the parttitions and panther folder for the setupact.

    So now there is different EFI installitions based on how we install or what.

  • by CraigT33,

    CraigT33 CraigT33 Dec 30, 2013 5:26 PM in response to kyraxyg
    Level 1 (0 points)
    Dec 30, 2013 5:26 PM in response to kyraxyg

    Still didnt work for me.  Sudo mounted the efi disk in Mac desktop and deleted folders leaving only the Apple one.  Then ran boot camp and followed your instructions prior to formatting.

     

    Please note that i could not change directory after leaving DISKPART.

     

         X:\services   cd B:

         B:\                         (this just shows for a second then it jumps to the next line)

         X:\services

  • by iampastwitsend,

    iampastwitsend iampastwitsend Dec 30, 2013 6:02 PM in response to CraigT33
    Level 1 (0 points)
    Dec 30, 2013 6:02 PM in response to CraigT33

    I'd like to encourage everyone having issues and who can to take up the issue with AppleCare.  I can't believe Apple doesn't already know there's a problem, but unless they get enough complaints through the support back channels, they won't devote the needed resources to get this issue fixed.

     

    When I started, I thought it would be a fun little project to get Windows up and running on my MacBook.  At this point, it's not fun anymore.

     

    AppleCare did offer me an interim solution that I'm satisfied with -- I can only imagine there's an issue that needs to be resolved that will only be resolved via an EFI update.  I don't understand why there's so much variability -- in that the installation works for some people out of the box, but not for others.  Suffice it to say though, it's a painful exercise to go through the myriad iterations just to find the latest solution doesn't work either.

     

    So, "Call Apple, call Apple, call Apple..."  Express your frustration... Let them know there are many of us in the community that are frustrated with the lack of support or resolution on this issue.

     

    AppleCare did ask me to call Microsoft for support.  The Microsoft tech that I first spoke with wanted me to launch Internet Explorer so he could remote into my machine.  I explained I was running a Mac.  His response was to forward me to the Office for Mac team.  Incidentally, the Office for Mac team doesn't help with Windows installations on Mac hardware.  Finally, the Office for Mac tech left me on hold for five or so minutes before coming back and telling me that Microsoft doesn't provide support for Windows installations on Mac hardware.  They said I should call Apple.  Well played Microsoft!

     

    FWIW, I think the MBR installation that you convert to an EFI installation on page 23 of this thread works, although you may need some tweaks.  I'm probably going to go back with that fix and then hold off on the Windows 8.1 upgrade until Apple comes out with an EFI update.

     

    Frankly though... I'm disappointed.  I never expected there would be such challenge.  The 15" retina Macbook Pro has been out for almost six months.  There's no way they should be having these issues now.

  • by mikereed36,

    mikereed36 mikereed36 Dec 30, 2013 6:31 PM in response to iampastwitsend
    Level 1 (0 points)
    Dec 30, 2013 6:31 PM in response to iampastwitsend

    I highly agree with iampastwitsend.

     

    If any of you want a Boot Camp that officially supports Windows 8.1 then you have to provide feedback here: http://www.apple.com/feedback/macosx.html

     

    You can call AppleCare but they'll tell you that the fastest way to have your voice heard is to report feedback here as well: http://www.apple.com/feedback/macosx.html

    (It's the same link)

     

    It'll take you maybe 1 minute or more depending on how thorough you wish to be.

first Previous Page 33 of 41 last Next