walkies_a

Q: Bootcamp install not working after update

I have a 2015 MacbookPro 15inc with Windows 8.1 installed under bootcamp. I had an update mess up bootcamp earlier in the year, but was able to fix it using command prompt. However since updating 2 days ago bootcamp has stopped again and anything I do does not work.

 

When I boot with option key I see a mac and windows option, when I follow the windows I get an immediate blue screen with error 0xc00000e. I have tried various diskpart and bcd commands with no success, in-fact now I have two options for windows on boot, neither of which work.

 

I have looked at some of the other inputs in the forum and have posted the requested info from command below:

 

Last login: Wed Apr 15 10:32:44 on ttys000

pc-fourroux4:~ Walker$ diskutil list

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.3 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:          Apple_CoreStorage                         249.3 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.1 MB   disk0s3

   4:       Microsoft Basic Data                         249.8 GB   disk0s4

   5: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC               314.6 MB   disk0s5

/dev/disk1

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                  Apple_HFS Macintosh HD           *249.0 GB   disk1

                                 Logical Volume on disk0s2

                                 C49EDEF2-2D01-41F7-8C4B-D57E18FF9FFC

                                 Unlocked Encrypted

/dev/disk2

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:     FDisk_partition_scheme                        *4.0 GB     disk2

   1:                 DOS_FAT_32 NO NAME                 4.0 GB     disk2s1

pc-fourroux4:~ Walker$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group F65A76BB-CA47-4BA5-9D21-10FF87833E20

    =========================================================

    Name:         Macintosh HD

    Status:       Online

    Size:         249318658048 B (249.3 GB)

    Free Space:   53248 B (53.2 KB)

    |

    +-< Physical Volume 606BE5DA-7096-4361-9E50-B5F36899B8B1

    |   ----------------------------------------------------

    |   Index:    0

    |   Disk:     disk0s2

    |   Status:   Online

    |   Size:     249318658048 B (249.3 GB)

    |

    +-> Logical Volume Family 1981166F-9D27-434C-9368-A8A69A708910

        ----------------------------------------------------------

        Encryption Status:       Unlocked

        Encryption Type:         AES-XTS

        Conversion Status:       Complete

        Conversion Direction:    -none-

        Has Encrypted Extents:   Yes

        Fully Secure:            Yes

        Passphrase Required:     Yes

        |

        +-> Logical Volume C49EDEF2-2D01-41F7-8C4B-D57E18FF9FFC

            ---------------------------------------------------

            Disk:                  disk1

            Status:                Online

            Size (Total):          248980963328 B (249.0 GB)

            Conversion Progress:   -none-

            Revertible:            Yes (unlock and decryption required)

            LV Name:               Macintosh HD

            Volume Name:           Macintosh HD

            Content Hint:          Apple_HFS

pc-fourroux4:~ Walker$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

gpt show: /dev/disk0: Suspicious MBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 977105059

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         32         Pri GPT table

         34          6        

         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

     409640  486950504      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

  487360144    1269760      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

  488629904        368        

  488630272  487860224      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976490496     614400      5  GPT part - DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

  977104896        131        

  977105027         32         Sec GPT table

  977105059          1         Sec GPT header

pc-fourroux4:~ Walker$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Signature: 0xAA55

         Starting       Ending

#: id  cyl  hd sec -  cyl  hd sec [     start -       size]

------------------------------------------------------------------------

1: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

2: AC   25 127  15 - 1023 254  63 [    409640 -  486950504] <Unknown ID>

3: AB 1023 254  63 - 1023 254  63 [ 487360144 -    1269760] Darwin Boot

*4: 0C 1023 254  63 - 1023 254  63 [ 488630272 -  487860224] Win95 FAT32L

pc-fourroux4:~ Walker$



Any help appreciated!!!


Andrew

MacBook Pro with Retina display, Windows 8

Posted on Apr 15, 2015 8:54 AM

Close

Q: Bootcamp install not working after update

  • All replies
  • Helpful answers

first Previous Page 5 of 6 last Next
  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 7:41 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 7:41 AM in response to Loner T

    ok, i did that and when i booted from the USB EFI I got the same screen as before. When I hit the "continue, exit and continue to windows", it reboots and goes to the 3rd screen I had before that it cannot load winload.efi

  • by Loner T,

    Loner T Loner T Apr 17, 2015 8:02 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 8:02 AM in response to walkies_a

    What does sudo fdisk /dev/disk0 show?

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 8:04 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 8:04 AM in response to Loner T

    Andrews-MacBook-Pro:~ Walker$ sudo fdisk /dev/disk0

    Password:

    Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

    Signature: 0xAA55

             Starting       Ending

    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

    ------------------------------------------------------------------------

    1: EE 1023 254  63 - 1023 254  63 [         1 -  977105059] <Unknown ID>

    2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

    Andrews-MacBook-Pro:~ Walker$

     

     

     

     

  • by Loner T,

    Loner T Loner T Apr 17, 2015 8:37 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 8:37 AM in response to walkies_a

    1. Can you reset NVRAM and reboot - How to Reset NVRAM on your Mac - Apple Support?

    2. Run Disk Utility Repair.

    3. Try the USB installer.

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 8:32 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 8:32 AM in response to Loner T

    I got to step three and when I ran it i got this error, the output of code is below: I did not reboot yet due to error seen.

     

    Screen Shot 2015-04-17 at 10.30.00 AM.png

    Verifying and repairing partition map for “APPLE SSD SM0512F Media”Checking prerequisitesChecking the partition listAdjusting partition map to fit whole disk as requiredChecking for an EFI system partitionChecking the EFI system partition’s sizeChecking the EFI system partition’s file systemRepairing the EFI system partition’s file systemRepairing file system.** /dev/rdisk0s1

    ** Phase 1 - Preparing FAT

    ** Phase 2 - Checking Directories

    /EFI/Microsoft/Boot/BCD.LOG has too many clusters allocated (logical=24576, physical=28672)

    Drop superfluous clusters? yes

    ** Phase 3 - Checking for Orphan Clusters

    Free space in FSInfo block (267113) not correct (267121)

    Fix? yes

    323 files, 133560 KiB free (267121 clusters)

     

    ***** FILE SYSTEM WAS MODIFIED *****

    File system check exit code is 0.Updating boot support partitions for the volume as required.Checking the EFI system partition’s folder contentProblems were encountered during repair of the partition mapError: Couldn’t mount disk.

  • by Loner T,

    Loner T Loner T Apr 17, 2015 8:39 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 8:39 AM in response to walkies_a

    Can you boot into Internet Recovery (using a wired connection) and run Disk Utility and Repair it?

     

    OS X: About OS X Recovery - Apple Support

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 9:08 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 9:08 AM in response to Loner T

    I couldn't do via wired, but went into regular recovery and repair worked (see below output), i will reboot now and try efi again.

     

    Verifying and repairing partition map for “APPLE SSD SM0512F Media”Checking prerequisitesChecking the partition listAdjusting partition map to fit whole disk as requiredChecking for an EFI system partitionChecking the EFI system partition’s sizeChecking the EFI system partition’s file systemChecking the EFI system partition’s folder contentChecking all HFS data partition loader spacesChecking booter partitionsChecking booter partition disk0s3Repairing file system.Checking Journaled HFS Plus volume.Checking extents overflow file.Checking catalog file.Checking multi-linked files.Checking catalog hierarchy.Checking extended attributes file.Checking volume bitmap.Checking volume information.Trimming unused blocks.The volume Recovery HD appears to be OK.File system check exit code is 0.Updating boot support partitions for the volume as required.Reviewing boot support loadersChecking Core Storage Physical Volume partitionsVerifying storage systemChecking volumedisk0s2: Scan for Volume Headersdisk0s2: Scan for Disk LabelsLogical Volume Group F65A76BB-CA47-4BA5-9D21-10FF87833E20 on 1 devicedisk0s2: Scan for Metadata VolumeLogical Volume Group has a 17 MB Metadata Volume with double redundancyStart scanning metadata for a valid checkpointLoad and verify Segment HeadersLoad and verify Checkpoint PayloadLoad and verify Transaction SegmentLoad and verify Transaction SegmentIncorporate 1 newer non-checkpoint transactionLoad and verify Virtual Address TableLoad and verify Segment Usage TableLoad and verify Metadata SuperblockLoad and verify Logical Volumes B-TreesLogical Volume Group contains 1 Logical VolumeLoad and verify 1981166F-9D27-434C-9368-A8A69A708910Load and verify C49EDEF2-2D01-41F7-8C4B-D57E18FF9FFCLoad and verify Freespace SummaryLoad and verify Block AccountingLoad and verify Live Virtual AddressesNewest transaction commit checkpoint is validLoad and verify Segment CleaningThe volume F65A76BB-CA47-4BA5-9D21-10FF87833E20 appears to be OKStorage system check exit code is 0.Repairing storage systemThe volume disk0s2 cannot be repaired when it is in useChecking volumedisk0s2: Scan for Volume Headersdisk0s2: Scan for Disk LabelsLogical Volume Group F65A76BB-CA47-4BA5-9D21-10FF87833E20 on 1 devicedisk0s2: Scan for Metadata VolumeLogical Volume Group has a 17 MB Metadata Volume with double redundancyStart scanning metadata for a valid checkpointLoad and verify Segment HeadersLoad and verify Checkpoint PayloadLoad and verify Transaction SegmentIncorporate 0 newer non-checkpoint transactionsLoad and verify Virtual Address TableLoad and verify Segment Usage TableLoad and verify Metadata SuperblockLoad and verify Logical Volumes B-TreesLogical Volume Group contains 1 Logical VolumeLoad and verify 1981166F-9D27-434C-9368-A8A69A708910Load and verify C49EDEF2-2D01-41F7-8C4B-D57E18FF9FFCLoad and verify Freespace SummaryLoad and verify Block AccountingLoad and verify Live Virtual AddressesNewest transaction commit checkpoint is validLoad and verify Segment CleaningThe volume F65A76BB-CA47-4BA5-9D21-10FF87833E20 appears to be OKStorage system check exit code is 0.Updating Windows boot.ini files as requiredThe partition map appears to be OK

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 9:10 AM in response to walkies_a
    Level 1 (0 points)
    Apr 17, 2015 9:10 AM in response to walkies_a

    Still no luck on boot to efi, same options and same things happened.

  • by Loner T,

    Loner T Loner T Apr 17, 2015 10:04 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 10:04 AM in response to walkies_a

    Back up your OSX installation. Boot into Internet Recovery (not local recovery). The /Volumes/EFI may not exist. Choose a temporary directory/mount point on the internal disk.

     

    Mount your EFI volume as shown (to the directory you have created) and remove the Mcrosoft directory and all its contents.

     

    sudo mkdir /Volumes/EFI

    sudo mount -t msdos /dev/disk0s1 /Volumes/EFI

    df -h

    Filesystem      Size   Used  Avail Capacity   iused     ifree %iused  Mounted on

    /dev/disk0s2   691Gi  525Gi  165Gi    77% 137723786  43354293   76%   /

    devfs          336Ki  336Ki    0Bi   100%      1165         0  100%   /dev

    /dev/disk0s4   240Gi   58Gi  182Gi    25%    121547 190690105    0%   /Volumes/rMBPBCMP

    map -hosts       0Bi    0Bi    0Bi   100%         0         0  100%   /net

    map auto_home    0Bi    0Bi    0Bi   100%         0         0  100%   /home

    /dev/disk0s1   197Mi   25Mi  172Mi    13%         0         0  100%   /Volumes/EFI

    cd /Volumes/EFI

    ls -lt

    total 10

    -rwxrwxrwx  1 MyName  staff  4307 Sep 11  2014 BOOTLOG

    drwxrwxrwx  1 MyName  staff   512 Jan 10  2014 EFI

    cd EFI

    ls -lt

    total 1

    drwxrwxrwx  1 MyName  staff  512 Jul 24  2014 APPLE

    After you remove Microsoft, test.

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 10:34 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 10:34 AM in response to Loner T

    Before I do this, i am assuming it will take a little time. Do you have any instructions on chose temp mount point and then to remove microsoft, or does the code you listed do all that? Thanks!

  • by Loner T,

    Loner T Loner T Apr 17, 2015 10:50 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 10:50 AM in response to walkies_a

    The code does not remove any content. It is just to illustrate mounting the EFI partition. The worst-case I can see a TM backup of OSX and a restore after erasing the internal drive in Internet Recovery.

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 11:11 AM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 11:11 AM in response to Loner T

    OK, sorry, am a newbie on mac... Of the example, would you mind reposting with the codes in bold, versus the output. Thanks.

  • by Loner T,

    Loner T Loner T Apr 17, 2015 11:39 AM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 17, 2015 11:39 AM in response to walkies_a

    1. Boot into Internet Recovery.

    2. mkdir /Volumes/EFI

    3. mount -w -t msdos /dev/disk0s1 /Volumes/EFI

    4. cd /Volumes/EFI/EFI

    5. ls -l (Please ensure that you can see the Microsoft directory. If you cannot then there is a typo in the previous commands).

    6. rm -rf Microsoft

    7. umount /Volumes/EFI

    8. Reboot and try EFI boot.

  • by walkies_a,

    walkies_a walkies_a Apr 17, 2015 11:05 PM in response to Loner T
    Level 1 (0 points)
    Apr 17, 2015 11:05 PM in response to Loner T

    So, I followed through the last posts commands, I had to force the umount. I went to reboot and still no luck. I decided to recreate the usb windows in the bootcamp assistant. I then rebooted and selected EFI boot and it worked... I guess my usb must have got corrupted or something.The good thing about this is I will hopefully have a ufi installation Is there a set of commands to run to ensure that it installed correctly? It seems quicker to me already, but that is not particularly objective!

     

    Thanks!

  • by Loner T,

    Loner T Loner T Apr 18, 2015 3:39 PM in response to walkies_a
    Level 7 (24,115 points)
    Safari
    Apr 18, 2015 3:39 PM in response to walkies_a

    Please run msinfo32 in Windows -> Run and check the output. The following is for a legacy BIOS installation.

     

    13MBP-MSInfo-LegacyBIOS.PNG

first Previous Page 5 of 6 last Next