You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Upgraded to High Sierra, used Disk Utility, now Windows 10 won't boot

Macbook Air Mid-2011


Perfectly working state this morning:

Windows 10 x64 (upgraded in place from Windows 7 x64 which was created using standard Bootcamp steps in 2011, the upgrade was 3 years ago and was using standard windows process without having to mess with Bootcamp or do anything special).


Windows is the primary OS and machine has been running fine for years. Today I boot into OS X (I do this once a year for updates etc) and install High Sierra and to make some space, I use Disk utility (and do NOT touch the Windows partition), OS X only.


High Sierra successfully installs but when I try to boot back into windows, it just shows a white screen. Booting into OS X is working fine.


The Bootcamp partition still exists and is visible but the MBR is gone or GPT corrupted.


Contacted Apple Support online and they initially stuck with High Sierra isn't compatible with your device (wrong!), Hung up, called again and this time they redirected me to Nerdr article steps (http://nerdr.com/bootcamp-partition-lost-repairing-mac-partitions/) after the initial diagnostics that took an hour. I realise those steps were a mistake. Went to the Apple Store and they said they couldn't help with Boot Camp issues and that it looked like it was a High Sierra issue not Disk Utility (since High Sierra "moves stuff around"). We also tried to understand (but did not implement) couple of other threads where the issues were solved by Christopher Murphy and Loner T, but it was tough to figure out since some of the instructions seemed different:

Repairing Boot Camp after creating new partition

Windows 7 bootcamp partition not bootable after updating to 10.10.3

Repairing Bootcamp after resizing partition

Bootcamp not bootable after partitioning

Bootcamp Partition not bootable after resizing partition on HD

Repairing Boot Camp after creating new partition

Had too many doubts about those. Loner T made it clear not to follow Nerdr instructions but sometimes fdisk was used (built in?) whereas other times gdisk was.


System integrity is already disabled (followed Apple store person's instruction though they couldn't do it themselves coz not allowed). However sudo 'anything' always gives 'command not found' in the recovery terminal.


I'm tech literate and will follow instructions (unfortunately even when they are wrong) but am entirely unfamiliar with OS X and out of my depth here. Have used terminal in Linux and Cmd/Powershell in Win so willing to try anything at this point. I'd post the results of diskutil list but I have no idea how to copy it off of the Recovery and paste here.


OS X still boots fine and Bootcamp partition still exists. I really need to recover this (its not just Data but 400 tabs in browsers with Data I was working on that can't easily be copied).

MacBook Air, macOS High Sierra (10.13.6), null

Posted on Jul 16, 2018 4:57 AM

Reply
Question marked as Top-ranking reply

Posted on Jul 16, 2018 8:44 PM

VineetShrivastava wrote:


I'm typing this from Windows so I guess the Tests are moot! (For what its worth, all 3 tests would check out as Successful even before problem was solved, I could see the BootCamp Partition, access it and set it up as start up disk, it just wouldn't actually boot).

Excellent.

VineetShrivastava wrote:


I am atheist agnostic, but if you start a religion or cult, let me know 😝

Nah. No plans for such 'spiritual' adventures.


VineetShrivastava wrote:


Seriously though, Apple officially directed me towards Nerdr so for a more sustainable solution, I'll report it to Google to bury its ranking and contact the author to take it down as well if it does indeed cause more damage.

Yes, please do.


VineetShrivastava wrote:



I have few queries eating at me;

1) Did this happen due to High Sierra update (like Apple store Genius bar guys said) or Disk Utility (my guess)
2) I have 10 GB of space unused space on OS X side, I want to bring it over to Windows (seems impossible since Windows partition is at end of my disk, so I was thinking of a making the 10 GB a separate partition and dumping my Windows Page file on it. What would be the safest way of accomplishing this? My plan was to separate it from OS X using Disk Utility, then boot into windows and 'capture' it from there, keeping them from getting in each others way (not operating on the other OSes partition with another OS).
3) Now that I have a hybrid MBR, does this require extra precautions going forward? (Don't update etc? Was it always a Hybrid MBR)?
4) Do I have to do any housekeeping? (Re-enable SIP, remove something?)


1. Yes, due to HS update. It converts the partitions to APFS, but forgets to check if there is Windows, and to recreate the modified MBR after the upgrade.

2. I recommend against this. You will need to do some additional gymnastics with GParted and Windows Repair, if you want to pursue this further.

3. Yes, do not create additional partitions, otherwise the GPT and derived MBR will deviate again, rendering Windows not to boot (unless you recreate the updated MBR, again).

4. Yes, please re-enable SIP using the same link I posted earlier about SIP.

Similar questions

21 replies
Question marked as Top-ranking reply

Jul 16, 2018 8:44 PM in response to VineetShrivastava

VineetShrivastava wrote:


I'm typing this from Windows so I guess the Tests are moot! (For what its worth, all 3 tests would check out as Successful even before problem was solved, I could see the BootCamp Partition, access it and set it up as start up disk, it just wouldn't actually boot).

Excellent.

VineetShrivastava wrote:


I am atheist agnostic, but if you start a religion or cult, let me know 😝

Nah. No plans for such 'spiritual' adventures.


VineetShrivastava wrote:


Seriously though, Apple officially directed me towards Nerdr so for a more sustainable solution, I'll report it to Google to bury its ranking and contact the author to take it down as well if it does indeed cause more damage.

Yes, please do.


VineetShrivastava wrote:



I have few queries eating at me;

1) Did this happen due to High Sierra update (like Apple store Genius bar guys said) or Disk Utility (my guess)
2) I have 10 GB of space unused space on OS X side, I want to bring it over to Windows (seems impossible since Windows partition is at end of my disk, so I was thinking of a making the 10 GB a separate partition and dumping my Windows Page file on it. What would be the safest way of accomplishing this? My plan was to separate it from OS X using Disk Utility, then boot into windows and 'capture' it from there, keeping them from getting in each others way (not operating on the other OSes partition with another OS).
3) Now that I have a hybrid MBR, does this require extra precautions going forward? (Don't update etc? Was it always a Hybrid MBR)?
4) Do I have to do any housekeeping? (Re-enable SIP, remove something?)


1. Yes, due to HS update. It converts the partitions to APFS, but forgets to check if there is Windows, and to recreate the modified MBR after the upgrade.

2. I recommend against this. You will need to do some additional gymnastics with GParted and Windows Repair, if you want to pursue this further.

3. Yes, do not create additional partitions, otherwise the GPT and derived MBR will deviate again, rendering Windows not to boot (unless you recreate the updated MBR, again).

4. Yes, please re-enable SIP using the same link I posted earlier about SIP.

Jul 16, 2018 12:16 PM in response to VineetShrivastava

VineetShrivastava wrote:


I apologise for the stupidity in between....

No worries. 😉


VineetShrivastava wrote:


Disk: /dev/disk0 geometry: 14751/255/63 [236978176 sectors]

Signature: 0xAA55

Starting Ending

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

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

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

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

*3: 07 0
0
0 - 0
0
0 [ 0 - 0] HPFS/QNX/AUX

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

This is an invalid MBR. You will need to recreate the MBR using the Rebuild MBR section of Re: El Capitan has deleted my bootcamp windows partition. Do not modify the current GPT. The steps you have used only change the bootability of an already existing MBR entry, but does not create one.

Jul 16, 2018 12:51 PM in response to VineetShrivastava

Updated steps are...



Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see thesample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers. Please see the sample Q&A before you execute these steps.

  1. Sudo gdisk /dev/rdisk0
  2. P (Print list of parts)
  3. R (Recover)
  4. O (print current Hybrid MBR)
  5. H (chooses Hybrid)
  6. Partitions numbers to be hybridized: 2 3
  7. Y (Good for GRUB question)
  8. N (part 2 boot flag)
  9. Y (part 3 boot flag make NTFS bootable partition)
  10. O (print current Hybrid MBR)
  11. W (Write the new MBR)
  12. Y (Yes! write the new MBR)
  13. Reboot


Here is sample Q&A for this section. Please notice the Press Enter/Return.


Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y


Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF): Press Enter/Return

Set the bootable flag? (Y/N): N


Creating entry for GPT partition #3 (MBR partition #4)

Enter an MBR hex code (default 07): Press Enter/Return

Set the bootable flag? (Y/N): Y


Test 1 - Does Bootcamp Volume show up in Finder?

Test 2 - Can you see files in Bootcamp Volume?

Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?

Test 4 - If Test 3 is successful, select Bootcamp and Click Restart.

Jul 16, 2018 5:09 AM in response to VineetShrivastava

Please run Etrecheck and post the results here. https://etrecheck.com


1. Download, open Downloads folder, click it to open, then select 'open'

2. Click on the bouncing Etrecheck icon in the dock

3. Choose a problem from the popup menu, then start Etrecheck in the dialog box

4. Click 'share report' in the toolbar and copy to clipboard

5. Paste the clipboard here


Once we get a look at what's going on with your system, we might be better able to come up with something helpful.

Jul 16, 2018 5:24 AM in response to Stuart423

EtreCheck version: 4.3.5 (4D040)

Report generated: 2018-07-16 16:21:38

Download EtreCheck from https://etrecheck.com

Runtime: 3:46

Performance: Good


Problem: Other problem

Description:

Bootcamp not booting


Major Issues:

Anything that appears on this list needs immediate attention.


No Time Machine backup- Time Machine backup not found.

Battery failure- Your battery is reporting that it needs to be serviced.

Obsolete hardware- This machine may be considered obsolete.


Minor Issues:

These issues do not need immediate attention but they may indicate future problems.


Low disk space- This machine is running low on free hard drive space.

32-bit Apps- This machine has 32-bits apps that may have problems in the future.

Abnormal shutdown- Your machine shut down abnormally.


Hardware Information:

MacBook Air (13-inch, Mid 2011) - Obsolete!

MacBook Air Model: MacBookAir4,2

1 1.7 GHz Intel Core i5 (i5-2557M) CPU: 2-core

4 GB RAM - Not upgradeable

BANK 0/DIMM0 - 2 GB DDR3 1333 ok

BANK 1/DIMM0 - 2 GB DDR3 1333 ok

Battery: Health = Service Battery - Cycle count = 232


Video Information:

Intel HD Graphics 3000 - VRAM: 384 MB

Color LCD 1440 x 900


Drives:

disk0 - APPLE SSD SM128C 121.33 GB (Solid State - TRIM: Yes)

Internal SATA 3 Gigabit Serial ATA

disk0s1 - EFI (MS-DOS FAT32) [EFI] 210 MB

disk0s2 38.65 GB

disk1s1 - Macintosh HD (APFS) 38.65 GB (18.49 GB used)

disk1s2 - Preboot (APFS) [APFS Preboot] 38.65 GB (21 MB used)

disk1s3 - Recovery (APFS) [Recovery] 38.65 GB (516 MB used)

disk1s4 - VM (APFS) [APFS VM] 38.65 GB (1.07 GB used)

disk0s3 - B******P (NTFS) 82.47 GB


Mounted Volumes:

disk0s3 - B******P 82.47 GB (6.08 GB free)

NTFS

Mount point: /Volumes/B******P


disk1s1 - Macintosh HD 38.65 GB (18.46 GB free)

APFS

Mount point: /


disk1s4 - VM [APFS VM] 38.65 GB (18.46 GB free)

APFS

Mount point: /private/var/vm


Network:

Interface Bluetooth-Modem: Bluetooth DUN

Interface en0: Wi-Fi

802.11 a/b/g/n

One IPv4 address

2 IPv6 addresses

Interface en2: Bluetooth PAN

Interface bridge0: Thunderbolt Bridge


System Software:

macOS High Sierra 10.13.6 (17G65)

Time since boot: Less than an hour

System Load: 2.59 (1 min ago) 6.08 (5 min ago) 3.82 (15 min ago)


Security:

SystemStatus
GatekeeperMac App Store and identified developers
System Integrity ProtectionEnabled


32-bit Applications:

One 32-bit app


System Launch Agents:

[Not Loaded]8 Apple tasks
[Loaded]184 Apple tasks
[Running]100 Apple tasks
[Other]One Apple task


System Launch Daemons:

[Not Loaded]37 Apple tasks
[Loaded]192 Apple tasks
[Running]108 Apple tasks


Launch Agents:

[Loaded]com.google.keystone.agent.plist (Google, Inc. - installed 2018-02-04)


Launch Daemons:

[Loaded]com.apple.aelwriter.plist (Apple - installed 2011-12-24)
[Loaded]com.google.keystone.daemon.plist (Google, Inc. - installed 2018-07-16)


User Launch Agents:

[Other]com.facebook.videochat.***.plist (Apple - installed 2018-07-16)


User Login Items:

iTunesHelper Application (Apple - installed 2018-07-16)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)


Internet Plug-ins:

googletalkbrowserplugin: (installed 2015-12-11)

QuickTime Plugin: (installed 2018-07-04)

o1dbrowserplugin: (installed 2016-08-02)

JavaAppletPlugin: (installed 2012-01-28)


3rd Party Preference Panes:

BTTPrefs (installed 2011-11-23)

Perian (installed 2011-07-24)

Secrets (installed 2012-01-11)


Time Machine:

Time Machine Not Configured!


Top Processes by CPU:

Process (count)Source% of CPULocation
WindowServerApple21
sandboxdApple2
kernel_taskApple1
com.apple.WebKit.WebContent (2)Apple1
com.apple.WebKit.NetworkingApple1


Top Processes by Memory:

Process (count)SourceRAM usageLocation
kernel_taskApple508 MB
com.apple.WebKit.WebContent (2)Apple364 MB
mdworker (14)Apple198 MB
SafariApple121 MB
WindowServerApple62 MB


Top Processes by Network Use:

ProcessSourceInputOutputLocation
mDNSResponderApple12 KB11 KB
com.apple.WebKit.NetworkingApple10 KB13 KB
apsdApple4 KB2 KB
netbiosdApple758 B354 B
SystemUIServerApple0 B72 B


Top Processes by Energy Use:

Process (count)SourceEnergy (0-100)Location
WindowServerApple5
com.apple.WebKit.WebContent (2)Apple5
hiddApple1
syncdefaultsdApple0
com.apple.iCloudHelperApple0


Virtual Memory Information:

Available RAM1.26 GB
Free RAM29 MB
Used RAM2.74 GB
Cached files1.23 GB
Swap Used34 MB


Diagnostics Information (past 7 days):

2018-07-16 16:12:32 Last Shutdown Cause: 3 - Hard shutdown


2018-07-16 09:29:16 fseventsd Crash

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents .framework/Versions/A/Support/fseventsd



End of report

Jul 16, 2018 5:35 AM in response to VineetShrivastava

Last login: Mon Jul 16 16:12:55 on console

Vs-MacBook-Air:~ V$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 38.7 GB disk0s2

3: Microsoft Basic Data BOOTCAMP 82.5 GB disk0s3


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +38.7 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 18.5 GB disk1s1

2: APFS Volume Preboot 21.1 MB disk1s2

3: APFS Volume Recovery 516.1 MB disk1s3

4: APFS Volume VM 2.1 GB disk1s4


That's the output of diskutil list.


Also, we followed these intsructions twice:


"sudo fdisk -e /dev/disk0

p

setpid 4

07

flag 4

p

write

y"

Without the sudo and once with 4 and once with 3,whatever damaged that caused, I'm sorry (wasn't entirely in control of the troubleshooting at that point).

Jul 16, 2018 6:09 AM in response to VineetShrivastava

Post the output of


sudo dd if=/dev/rdisk0s3 count=1 2>/dev/null | hexdump -C (shows first block of NTFS header)

sudo fdisk /dev/disk0 (shows the MBR)


A 2011 Mac only support legacy BIOS and does not natively support W10. If W10 was an upgrade (as you indicate), it is a pain to work with due to BC driver issues. Let us see what we can do based on the output from these two.


VineetShrivastava wrote:


Contacted Apple Support online and they initially stuck with High Sierra isn't compatible with your device (wrong!), Hung up, called again and this time they redirected me to Nerdr article steps (http://nerdr.com/bootcamp-partition-lost-repairing-mac-partitions/) after the initial diagnostics that took an hour. I realise those steps were a mistake.

I personally would like to get rid of that specific page from the public Internet. It is an absolute travesty.

Jul 16, 2018 8:39 AM in response to Loner T

For the first block of NTFS header


00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|

00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 20 86 04 |........?.... ..|

00000020 00 00 00 00 80 00 80 00 ff d7 99 09 00 00 00 00 |................|

00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|

00000040 f6 00 00 00 01 00 00 00 a8 64 f6 4c 98 f6 4c e4 |.........d.L..L.|

00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|

00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|

00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|

00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|

00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|

000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|

000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|

000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|

000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|

000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|

000000f0 68 07 bb 16 68 52 11 16 68 09 00 66 53 66 53 66 |h...hR..h..fSfSf|

00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|

00000110 0a 13 b9 f6 0c fc f3 aa e9 fe 01 90 90 66 60 1e |.............f`.|

00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|

00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|

00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|

00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|

00000160 0e 16 00 75 bc 07 1f 66 61 c3 a1 f6 01 e8 09 00 |...u...fa.......|

00000170 a1 fa 01 e8 03 00 f4 eb fd 8b f0 ac 3c 00 74 09 |............<.t.|

00000180 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 64 69 |............A di|

00000190 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 6f 63 |sk read error oc|

000001a0 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d 47 52 |curred...BOOTMGR|

000001b0 20 69 73 20 63 6f 6d 70 72 65 73 73 65 64 00 0d | is compressed..|

000001c0 0a 50 72 65 73 73 20 43 74 72 6c 2b 41 6c 74 2b |.Press Ctrl+Alt+|

000001d0 44 65 6c 20 74 6f 20 72 65 73 74 61 72 74 0d 0a |Del to restart..|

000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

000001f0 00 00 00 00 00 00 8a 01 a7 01 bf 01 00 00 55 aa |..............U.|

00000200


For the MBR:


fdisk: /dev/disk0: Operation not permitted

Jul 16, 2018 12:04 PM in response to Loner T

Hi, since you had given the status command, I booted into recovery, checked (it had enabled itself). I disabled it using your command, but sudo fdisk did not work since sudo wasn't recognised in Recovery. So booted back into OS X and ran the command again and it gave the output you were looking for. I apologise for the stupidity in between....

Disk: /dev/disk0 geometry: 14751/255/63 [236978176 sectors]

Signature: 0xAA55

Starting Ending

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

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

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

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

*3: 07 0
0
0 - 0
0
0 [ 0 - 0] HPFS/QNX/AUX

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

Jul 16, 2018 12:23 PM in response to Loner T

I shall install GPT Fdisk now.


If its not too much trouble, may I have the instructions exactly as they should be entered since Step 10 and boot flags might need to be custom according to situation? Sorry, its just that I'm burnt from randomly entering commands found online when I was working with Apple support so I'm quite worried about messing it up by writing it on wrong sector/partition.

Jul 16, 2018 1:07 PM in response to Loner T

Last login: Tue Jul 17 00:01:25 on ttys000

Vineets-MacBook-Air:~ Vineet$ Sudo gdisk /dev/rdisk0

Password:

GPT fdisk (gdisk) version 1.0.4


Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:


MBR: hybrid


BSD: not present


APM: not present


GPT: present


Found valid GPT with hybrid MBR; using GPT.


Command (? for help): p

Disk /dev/rdisk0: 236978176 sectors, 113.0 GiB

Sector size (logical): 512 bytes

Disk identifier (GUID): 000033B4-45FD-0000-664D-000010580000

Partition table holds up to 128 entries

Main partition table begins at sector 2 and ends at sector 33

First usable sector is 34, last usable sector is 236978142

Partitions will be aligned on 8-sector boundaries

Total free space is 2021 sectors (1010.5 KiB)


Number
Start (sector) End (sector)
Size Code
Name

1 40 409639
200.0 MiB
EF00
EFI system partition

2 409640 75898879
36.0 GiB AF0A
Customer

3 75898880 236976127
76.8 GiB 0700
BOOTCAMP


Command (? for help): r


Recovery/transformation command (? for help): o


Disk size is 236978176 sectors (113.0 GiB)

MBR disk identifier: 0x00004B39

MBR partitions:


Number
Boot
Start Sector
End Sector
Status Code

1 1 236978175
primary 0xEE


Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 2 3

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y


Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF):

Set the bootable flag? (Y/N): n


Creating entry for GPT partition #3 (MBR partition #3)

Enter an MBR hex code (default 07):

Set the bootable flag? (Y/N): y


Unused partition space(s) found. Use one to protect more partitions? (Y/N): n


Recovery/transformation command (? for help): o


Disk size is 236978176 sectors (113.0 GiB)

MBR disk identifier: 0x00004B39

MBR partitions:


Number
Boot
Start Sector
End Sector
Status Code

1 1 409639
primary 0xEE

2 409640 75898879
primary 0xAF

3 * 75898880 236976127
primary 0x07


Recovery/transformation command (? for help): w


Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING

PARTITIONS!!


Do you want to proceed? (Y/N): y

OK; writing new GUID partition table (GPT) to /dev/rdisk0.

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Warning: The kernel may continue to use old or deleted partitions.

You should reboot or remove the drive.

The operation has completed successfully.

Vineets-MacBook-Air:~ Vineet$


One thing deviated from script, the bold/underline/italics line about unused partitions and using them to protect. I selected no.
Rebooting now to perform tests

Jul 16, 2018 1:18 PM in response to VineetShrivastava

I'm typing this from Windows so I guess the Tests are moot! (For what its worth, all 3 tests would check out as Successful even before problem was solved, I could see the BootCamp Partition, access it and set it up as start up disk, it just wouldn't actually boot).


I am atheist agnostic, but if you start a religion or cult, let me know 😝
Seriously though, Apple officially directed me towards Nerdr so for a more sustainable solution, I'll report it to Google to bury its ranking and contact the author to take it down as well if it does indeed cause more damage.


I have few queries eating at me;

1) Did this happen due to High Sierra update (like Apple store Genius bar guys said) or Disk Utility (my guess)
2) I have 10 GB of space unused space on OS X side, I want to bring it over to Windows (seems impossible since Windows partition is at end of my disk, so I was thinking of a making the 10 GB a separate partition and dumping my Windows Page file on it. What would be the safest way of accomplishing this? My plan was to separate it from OS X using Disk Utility, then boot into windows and 'capture' it from there, keeping them from getting in each others way (not operating on the other OSes partition with another OS).
3) Now that I have a hybrid MBR, does this require extra precautions going forward? (Don't update etc? Was it always a Hybrid MBR)?
4) Do I have to do any housekeeping? (Re-enable SIP, remove something?)


Thanks a ton

Jul 16, 2018 7:54 PM in response to Loner T

For 2 and 3.
What happens if I just partition off the space using Disk Utility and then format and use it as a page file (separate) parition in Windows (no expansion or merging).


Also what would be different or have happened if I selected yes for the "Unused partition space(s) found. Use one to protect more partitions? (Y/N): n" question.


Thanks a ton!

Jul 16, 2018 8:44 PM in response to VineetShrivastava

VineetShrivastava wrote:


For 2 and 3.
What happens if I just partition off the space using Disk Utility and then format and use it as a page file (separate) parition in Windows (no expansion or merging).

The moment you create a partition, you break the 1:1 GPT:MBR mapping, which breaks Windows. This implies that you will need to recreate it again. There is also the issue of Windows Startup Repair, because the BCD is also different.


VineetShrivastava wrote:


Also what would be different or have happened if I selected yes for the "Unused partition space(s) found. Use one to protect more partitions? (Y/N): n" question.

No, but it can create confusion, because you will end up with more entries in the MBR than in the GPT, which can cause future issues.

Upgraded to High Sierra, used Disk Utility, now Windows 10 won't boot

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.