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 19 of 41 last Next
  • by Dourn,

    Dourn Dourn Nov 15, 2013 10:38 PM in response to Dourn
    Level 1 (0 points)
    Nov 15, 2013 10:38 PM in response to Dourn

    Also, I've just realized something:

    The reason that the Windows 8.1/Windows Server 2012 R2 installer has problems with updating the Boot configuration is that the EFI partition seems to be read-only from inside windows.

    It's possible it's only readonly to users, and not to the IS, but if I assign it a drive-letter via DISKPART or DiskManager, I get an access denied message when trying to browse it.

     

    But if I mount/assign it a letter from the WinPE environment (i.e. the repair console) then I can read/write to it with no problems.

     

    Also, I just managed to hose my OSX partition - I had some unallocated space on the drive, so from within Windows I located a new partition. Everything looked fine from Windows (i.e. the OSX HFS partition looked and was still an HFS partition with all the corretc files), but my rEFIt boot menu wouldn't appear - when I loaded OSX Recovery and looked in Disk Utility it said that the OSX partition was formatted as FAT.

    Weird - apparently windows does this sometimes, if you modify portions it can alter HFS partitions - the solution is to do all partition maintenance from within OSX.

     

    Oh well, reinstalling OSX now... :-)

  • by Dourn,

    Dourn Dourn Nov 15, 2013 11:03 PM in response to Dourn
    Level 1 (0 points)
    Nov 15, 2013 11:03 PM in response to Dourn

    OK, so re. the Windows Update problem, I suspect this is because Windows still thinks I'm in OOBE mode... goign to dig into this and see if I can fix it.. should just be a registry value change... but will have to wait till after I rebuild OSX... :-)

  • by benad84,

    benad84 benad84 Nov 16, 2013 11:25 AM in response to Dourn
    Level 1 (0 points)
    Nov 16, 2013 11:25 AM in response to Dourn

    I'm having the same problem as wohingenau. Manually running "msoobe" makes the laptop functional somewhat, but SYSPREP is left in a half-broken state which prevent all forms of Windows Software Update. I tried multiple forms of the sysprep command ("sysprep /oobe" for example), and in all cases it failed at some point. I even tried the workaround here: http://social.technet.microsoft.com/Forums/windows/en-US/bb62362c-7fbc-4d53-bb08 -aa35d39b49ca/sysprep-fails-on-msdtcprxdll?forum=w7itproinstall , and in the end SYSPREP completed but simply rebooted the machine back to the original issue of "windows setup cannot configure windows for this hardware".

     

    I'm not in a rush to install Windows 8.1, but if by the end of the year Apple doesn't have a fix to natively support EFI Windows in Boot Camp I'll have to move to BIOS / GPT by installing Windows 7 first then upgrading.

     

    It's really sad that Apple never tested Boot Camp on those laptops, not even once with Windows 8.0. The fact that the Boot Camp bundled with 10.9 is not versioned the same way ("BCA" and not Boot Camp version 6) gives me the impression the Haswell release was rushed.

  • by Dourn,

    Dourn Dourn Nov 16, 2013 11:54 AM in response to benad84
    Level 1 (0 points)
    Nov 16, 2013 11:54 AM in response to benad84

    Yup, that's quite right benad84 - after the failed call to Sysprep to get past the "cannot configure windows" problem, Windows is left in Sysprep Audit state, which is supposed to be used for adding drivers etc. before getting an image ready for deployment.

     

    Given the fact that Windows 8.1/Server 2012 R2 only runs in Audit mode, and gives the "cannot configure windows" error when not in audit mode, I suspect the issue lies with a core driver here. And I keep coming back to EFI - in theory Windows only support UEFI v2.0 (actually v2.3 I think), but Apple only implements v1.1.

     

    It's probably worth all of us raising a support ticket with Apple over this one - they're aware of the problem, but it will take more people to raise the issue to speed them along.

     

    But ultimately, we shouldn't have to install Win7 first just to install Win 8.1!!

     

    I'm going to keep trying to see if I can get out of Audit mode without running sysprep /oobe...

  • by david0evans,

    david0evans david0evans Nov 16, 2013 2:57 PM in response to jdhiro
    Level 1 (0 points)
    Nov 16, 2013 2:57 PM in response to jdhiro

    I'm having the same problems as the OP. 15" rMBP with nVidia, just bought it yesterday.

     

    Following the standard install process for Windows 8.1 with Bootcamp, I get the same error message at the end of "finishing up" in the 8.1 install.

     

    I've tried a bunch of the suggestions here and nothing has worked. I tried installing 7 but it hangs at 65% in the install process.

     

    I'm reinstalling Mavericks from recovery right now to see if it helps.

  • by Wasabi Dan,

    Wasabi Dan Wasabi Dan Nov 16, 2013 3:48 PM in response to david0evans
    Level 1 (0 points)
    Nov 16, 2013 3:48 PM in response to david0evans

    Windows 7 always stays at 65% for a majority of the install time -just wait it out, you should be fine.

  • by Shodan_Cat,

    Shodan_Cat Shodan_Cat Nov 16, 2013 4:01 PM in response to jdhiro
    Level 1 (4 points)
    Nov 16, 2013 4:01 PM in response to jdhiro

    I was able to install 8.1 Pro (the full version, not the upgrade) on my 15" RMBP with 750m. The solution is extremely simple.

     

    Use Boot Camp Assistant to set up a USB thumb drive with your 8.1 ISO file, along with the Windows Support files. Also let it partition your hard drive after you pick your size. When it asks you to restart, hold down Option to boot back to OS X, not your thumb drive. Open up Disk Manager and remove the BOOTCAMP partition, the create a new partition using the free space, name it BOOTCAMP and use ExFAT. After you click Apply and it recreates the partition, restart and hold Option to boot to the thumb drive.

     

    Once the 8.1 install starts and you get to the hard drive part, click Format on the BOOTCAMP partition and you should be good to go. After it runs through the install it'll ask you to reboot 2 or 3 times, each time it reboots be sure to hold down Option to boot off the Windows partition (NOT the thumb drive.) Eventually it'll prompt you through the Boot Camp installer for the Windows drivers and voila, you're done. 

     

    Short and sweet version: Do everything as normal with Boot Camp Assistant, but delete the partition it creates and then re-create it with ExFAT, then restart and boot off the thumb drive with Windows installation on it and the rest should go as expected.

  • by Colin Cornaby,

    Colin Cornaby Colin Cornaby Nov 16, 2013 4:08 PM in response to Shodan_Cat
    Level 1 (0 points)
    Nov 16, 2013 4:08 PM in response to Shodan_Cat

    I've tried this suggestion and it didn't work for me. I'm not sure why this works for some people and not others.

  • by Shodan_Cat,

    Shodan_Cat Shodan_Cat Nov 16, 2013 4:15 PM in response to Colin Cornaby
    Level 1 (4 points)
    Nov 16, 2013 4:15 PM in response to Colin Cornaby

    Can you explain where the process fails for you using that method?  I'll try to help you if I can.

  • by Colin Cornaby,

    Colin Cornaby Colin Cornaby Nov 16, 2013 4:15 PM in response to Shodan_Cat
    Level 1 (0 points)
    Nov 16, 2013 4:15 PM in response to Shodan_Cat

    I'm not sure where the failure is. I just get the exact same error I got before.

  • by david0evans,

    david0evans david0evans Nov 16, 2013 4:18 PM in response to Shodan_Cat
    Level 1 (0 points)
    Nov 16, 2013 4:18 PM in response to Shodan_Cat

    After deleteing/recreating the partition and booting in the USB drive, do you choose "WINDOWS" or "EFI BOOT"?

  • by Colin Cornaby,

    Colin Cornaby Colin Cornaby Nov 16, 2013 4:19 PM in response to david0evans
    Level 1 (0 points)
    Nov 16, 2013 4:19 PM in response to david0evans

    EFI Boot. I don't want to do the "WINDOWS" BIOS install.

     

    (Whoops, you were responding to Shodan. I'd hope his solution does the EFI boot part.)

  • by Shodan_Cat,

    Shodan_Cat Shodan_Cat Nov 16, 2013 4:24 PM in response to Colin Cornaby
    Level 1 (4 points)
    Nov 16, 2013 4:24 PM in response to Colin Cornaby

    After you re-create the partition with Disk Manager, reboot and hold Option to boot from the thumb drive with your Windows install.

     

    This method only uses the EFI boot options.

     

    Colin, can you explain to me step by step exactly what you did?  I doubt it's completely random from system to system so there's probably a minute detail where we differed on this process. By the way, I'm not a dude

  • by benad84,

    benad84 benad84 Nov 16, 2013 4:29 PM in response to Shodan_Cat
    Level 1 (0 points)
    Nov 16, 2013 4:29 PM in response to Shodan_Cat

    When I was booting with the option key, there were two USB boot drives: The "default" one, which is DOS, and one clearly marked "EFI". If the "reformat with ExFAT" trick only displays a single boot option for the USB drive, then likely it is the DOS boot.

     

    You can tell the difference easily between the DOS and EFI boot with the Windows logo. In DOS, the resolution is quite low, so the logo should almost fill the screen. In EFI, the logo will use the native 2880x1200 resolution of the Retina display, so the edges are perfectly sharp and not blurry as the DOS one.

  • by david0evans,

    david0evans david0evans Nov 16, 2013 5:30 PM in response to Shodan_Cat
    Level 1 (0 points)
    Nov 16, 2013 5:30 PM in response to Shodan_Cat

    Hm, I'm trying your method, but when I click format on the exFAT partition, it still says that windows cannot be installed on this partition, as if the format didn't work.

     

    EDIT (to clarify, this is from within the Windows 8.1 installer, after I deleted and recreated the bootcamp partition using disk utility).

     

    The full error is that the exFAT parition has an MBR record while Windows 8.1 can only be installed to a GPT disk. It sounds to me like you booted via BIOS to get your install.

first Previous Page 19 of 41 last Next