Apple Event: May 7th at 7 am PT

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

Boot Camp Partition not visible in High Sierra

Running an iMac 2017 (macOS 10.13.2) with bootcamped Windows 10 Pro (1709).


The problem is more or less a cosmetic hassle, but I would prefer to have it solved because it can disturb later repair operations. It is quite similar to this one , but my system is 10.13, has APFS, and I never installed any NTFS read/write solutions like Paragon NTFS, Tuxera etc. (which was the solution in the former thread)


On High Sierra I

- Cannot see Boot Camp from preferences when selecting startup disk.

- Cannot see Boot Camp mounted on desktop

- Cannot see Boot Camp in finder sidebar

- Can see Boot Camp in Disk Utility but it is grayed out and I cannot run first aid or mount


Systems are selectable via Restart and pressed Option Key, both are working without any trouble.


In startup disk of High Sierra selecting the only one option „OS X“ lets system restart only to „OS X“, whereas in Windows 10 Boot Camp startup panel the only one option „Windows“ restarts the system always in Windows. Thus the function of a working startup panel can become realized, but in a more complicated way.


I tried SMC Reset, NVRAM Reset, Reinstalled 10.13 via Recovery without Erase.


Here some outputs of the usually asked Terminal commands (after „csrutil disable“ in Recovery):


Obelix:~ deusrex$ diskutil list

/dev/disk0 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 500.3 GB disk0

1: EFI EFI 314.6 MB disk0s1

2: Apple_APFS Container disk1 73.0 GB disk0s2

3: Microsoft Basic Data Obelix W10 427.0 GB disk0s3


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +73.0 GB disk1

Physical Store disk0s2

1: APFS Volume Obelix HD 21.7 GB disk1s1

2: APFS Volume Preboot 23.1 MB disk1s2

3: APFS Volume Recovery 506.6 MB disk1s3

4: APFS Volume VM 2.1 GB disk1s4



Obelix:~ deusrex$ diskutil cs list

No CoreStorage logical volume groups found



Obelix:~ deusrex$ diskutil apfs list

APFS Container (1 found)

|

+-- Container disk1 1DD7DB4C-D623-49D3-848B-B2E4A9F07CFB

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

APFS Container Reference: disk1

Capacity Ceiling (Size): 73000787968 B (73.0 GB)

Capacity In Use By Volumes: 24507240448 B (24.5 GB) (33.6% used)

Capacity Available: 48493547520 B (48.5 GB) (66.4% free)

|

+-< Physical Store disk0s2 024E075C-F093-4B5D-9D03-2D8A1310F1FA

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

| APFS Physical Store Disk: disk0s2

| Size: 73000787968 B (73.0 GB)

|

+-> Volume disk1s1 E6633F2D-9F3F-4087-8F87-F4A7F1151D42

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

| APFS Volume Disk (Role): disk1s1 (No specific role)

| Name: Obelix HD (Case-insensitive)

| Mount Point: /

| Capacity Consumed: 21708156928 B (21.7 GB)

| FileVault: No

|

+-> Volume disk1s2 D6C537EC-13B1-4714-BB90-D46E067FC5A1

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

| APFS Volume Disk (Role): disk1s2 (Preboot)

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 23093248 B (23.1 MB)

| FileVault: No

|

+-> Volume disk1s3 F4D69D0E-F527-40A2-A416-CC36D8712E09

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

| APFS Volume Disk (Role): disk1s3 (Recovery)

| Name: Recovery (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 506568704 B (506.6 MB)

| FileVault: No

|

+-> Volume disk1s4 514382BE-612D-49D1-9016-F9717A241CB5

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

APFS Volume Disk (Role): disk1s4 (VM)

Name: VM (Case-insensitive)

Mount Point: /private/var/vm

Capacity Consumed: 2147504128 B (2.1 GB)

FileVault: No



Obelix:~ deusrex$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 7602/255/63 [122138132 sectors]

Sector size: 4096 bytes

Signature: 0xAA55

Starting Ending

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

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 122138131] <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



Obelix:~ deusrex$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500277788672; sectorsize=4096; blocks=122138132

gpt show: /dev/disk0: PMBR at sector 0

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

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

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 4 Pri GPT table

6 76800 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

76806 17822458 2 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC

17899264 104238848 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

122138112 15

122138127 4 Sec GPT table

122138131 1 Sec GPT header



Would like to see Bootcamp partition in Finder, on Desktop and in Startup Panel. Any idea what’s wrong?

iMac with Retina 5K display, macOS High Sierra (10.13.2), null

Posted on Dec 21, 2017 5:33 PM

Reply
45 replies

Dec 21, 2017 8:20 PM in response to ramses002

Do you have any Virtualization engines on your Mac? What third-party software have you installed on the macOS side?

ramses002 wrote:


I have an identical second iMac with an identical Windows installation here, where the Boot Camp partition is shown in all desired options.

Boot the non-working Mac in Target Disk Mode - How to use target disk mode to move files between two Mac computers - Apple Support - and connect to the working Mac. Do you see the Bootcamp partition from the 'non-working' show up on the 'working' Mac? If yes, you should consider re-installing High Sierra with the latest patches on the 'non-working' Mac. You may have KEXT corruption due to failed HS update.


References


Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1 - Apple Support

How to switch between Windows and macOS in macOS High Sierra - Apple Support

Dec 21, 2017 6:50 PM in response to munkymajik

It's present in Disk Utility, but grayed out and not mountable or repairable.

Your Windows argument is true, in particular because I have an identical second iMac with an identical Windows installation here, where the Boot Camp partition is shown in all desired options. Due to the discussions concerning this problem the Windows NTFS driver was my first suspect, because all changes of this driver (Paragon, Tuxera etc.) disable the visibility in High Sierra. Unfortunately disabling via GPO all Windows driver updates, followed by a reinstall of the original Boot Camp drivers didn't show any positive results.

Dec 21, 2017 10:00 PM in response to Loner T

Thanks for your reply. There are no virtualization engines on this Mac, there is also no software installed on the Mac side besides the system it came with. The Mac is not "non working", it works perfectly except the single feature of the missing visibility of the Boot Camp partition on the Mac side.


As in my first post mentioned I already reinstalled High Sierra from the Recovery partition (fresh "over"-Installation of newest High Sierra with user data kept, no erase of the partition, no updates available according to AppStore). IMHO such a reinstall of High Sierra from Recovery should renew the complete system, kexts included, or doesn't it? Would there be a difference between this kind of reinstall and prior erase of the macOS partition? Would the installed Boot Camp partition kept accessible and mountable after a macOS Erase?


But you brought me to another idea: a possible user account corruption, which is not covered during a fresh install. Immediately tested with a new admin account, but unfortunately also without success.


The idea with Target Mode is interesting, but I don't own a Thunderbold 3 cable in the necessary USB-C variation, and these are here difficult to get and too expensive just for a short test.

Dec 22, 2017 8:14 PM in response to Loner T

Obelix:~ deusrex$ diskutil info disk0

Device Identifier: disk0

Device Node: /dev/disk0

Whole: Yes

Part of Whole: disk0

Device / Media Name: APPLE SSD SM0512L


Volume Name: Not applicable (no file system)

Mounted: Not applicable (no file system)

File System: None


Content (IOContent): GUID_partition_scheme

OS Can Be Installed: No

Media Type: Generic

Protocol: PCI-Express

SMART Status: Not Supported


Disk Size: 500.3 GB (500277788672 Bytes) (exactly 977105056 512-Byte-Units)

Device Block Size: 4096 Bytes


Read-Only Media: No

Read-Only Volume: Not applicable (no file system)


Device Location: Internal

Removable Media: Fixed


Solid State: Yes

OS 9 Drivers: No

Low Level Format: Not supported



Obelix:~ deusrex$ diskutil mount disk0s3

Volume on disk0s3 failed to mount

If the volume is damaged, try the "readOnly" option

Dec 23, 2017 7:47 AM in response to Loner T

chkdsk didn't show any errors. I also started later the deeper going "chkdsk c: /f /r" from admin console, also without any errors. Back in High Sierra nothing has changed.


Microsoft Windows [Version 10.0.16299.125]

(c) 2017 Microsoft Corporation. Alle Rechte vorbehalten.


C:\Windows\system32>chkdsk

Der Typ des Dateisystems ist NTFS.

Die Volumebezeichnung lautet Obelix W10.


WARNUNG! Der Parameter /F wurde nicht angegeben.

CHKDSK wird im schreibgeschützten Modus ausgeführt.


Phase 1: Die Basisdatei-Systemstruktur wird untersucht...

254208 Datensätze verarbeitet.

Dateiüberprüfung beendet.

3882 große Datensätze verarbeitet.

0 ungültige Datensätze verarbeitet.


Phase 2: Die Dateinamenverknüpfung wird untersucht...

260 Analysedatensätze verarbeitet.

318632 Indexeinträge verarbeitet.

Indexüberprüfung beendet.

0 nicht indizierte Dateien überprüft.

0 nicht indizierte Dateien wiederhergestellt.

260 Analysedatensätze verarbeitet.


Phase 3: Sicherheitsbeschreibungen werden untersucht...

Überprüfung der Sicherheitsbeschreibungen beendet.

32213 Datendateien verarbeitet.

CHKDSK überprüft USN-Journal...

36065480 USN-Bytes verarbeitet.

Die Überprüfung von USN-Journal ist abgeschlossen.


Dateisystem wurde überprüft, keine Probleme festgestellt.

Keine weiteren Aktionen erforderlich.


416955388 KB Speicherplatz auf dem Datenträger insgesamt

47111760 KB in 120213 Dateien

94580 KB in 32214 Indizes

0 KB in fehlerhaften Sektoren

371124 KB vom System benutzt

65536 KB von der Protokolldatei belegt

369377924 KB auf dem Datenträger verfügbar


4096 Bytes in jeder Zuordnungseinheit

104238847 Zuordnungseinheiten auf dem Datenträger insgesamt

92344481 Zuordnungseinheiten auf dem Datenträger verfügbar


C:\Windows\system32>

Dec 23, 2017 8:08 AM in response to ramses002

From the macOS side, post the output of the highlighted commands


cd /Volumes

ls -lga

total 24

drwxrwxrwt@ 6 admin 204 Dec 23 11:04 .

drwxrwxr-t 32 admin 1156 Dec 20 09:39 ..

-rw-r--r--@ 1 admin 6148 Aug 27 22:36 .DS_Store

drwxr-xr-x+ 2 admin 68 Dec 23 11:04 BOOTCAMP

drwxr-xr-x 1 staff 8192 Nov 25 20:45 BOOTCAMP 1

lrwxr-xr-x 1 admin 1 Dec 21 19:50 OSY-MBP13 -> /

Dec 23, 2017 10:01 PM in response to Loner T

With disabled BootCamp on the "working" iMac:

Asterix:/ deusrex$ cd /Volumes

Asterix:Volumes deusrex$ ls -lga

total 0

drwxr-xr-x+ 5 wheel 160 24 Dez 06:16 .

drwxr-xr-x 30 wheel 960 21 Dez 00:42 ..

lrwxr-xr-x 1 wheel 1 23 Dez 19:41 Asterix HD -> /

drwxr-xr-x+ 3 wheel 96 8 Dez 13:28 Preboot

drwxr-xr-x@ 4 wheel 128 22 Nov 14:38 Preboot 1


The 2 helping partitions (?) "Preboot" and "Preboot 1" seems to be missing on the "non working" iMac. They contain Caches and Crypto related plists. I forgot to mention, that at the "working" iMac the High Sierra partition was sealed with FileVault after everthing worked ok.

Dec 24, 2017 9:17 AM in response to Loner T

Both, the "working" and the "not working" iMac came with High Sierra and APFS preinstalled. Both have pure Flash drives, so there is no other choice, and any convertion was not necessary. The two Preboot Volumes on the "working" iMac seems to be related to FileVault, both are linking to the UUIDs of the High Sierra side:

Asterix:/ deusrex$ cd /Volumes

Asterix:Volumes deusrex$ ls -al Pre*

Preboot:

total 0

drwxr-xr-x+ 3 root wheel 96 8 Dez 13:28 .

drwxr-xr-x+ 6 root wheel 192 24 Dez 07:01 ..

drwxr-xr-x+ 4 root wheel 128 8 Dez 13:28 4D9AAE28-0DF3-4F29-920D-3F23CD6B40FC


Preboot 1:

total 0

drwxr-xr-x@ 4 root wheel 128 22 Nov 14:38 .

drwxr-xr-x+ 6 root wheel 192 24 Dez 07:01 ..

d-wx-wx-wt 3 root wheel 96 20 Nov 22:18 .Trashes

drwxr-xr-x 7 root wheel 224 8 Dez 19:07 4D9AAE28-0DF3-4F29-920D-3F23CD6B40FC

Boot Camp Partition not visible in High Sierra

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